How to Sell Website Redesigns to Businesses With an Existing Site

By Cameron Kirdzik — Founder @WebHunt.ai

October 14, 2026 · 8 min read

Why Existing-Site Owners Say "It’s Fine"—and How AI Changes the Pitch

Most owners already believe in websites. Their objection isn’t existence; it’s perceived adequacy. “It’s fine” means “I don’t feel the pain.” Your job is to surface the leaks—lost calls, slow load, weak mobile flow—then show a no-friction path to a visibly better, faster site.

In the AI era, you can build a live draft in hours using Replit, Lovable, Base44, v0, Bolt, Framer AI, Cursor, Windsurf, Codex Sites, Claude Design, or Claude Code. That lets you promise a 24–72 hour redesign pilot, not a 6-week project. The talk track shifts from features to loss: quantify the missed leads from speed, mobile UX, and weaker-than-competitor pages. Then demo a working upgrade, not a Figma.

Set the closing arc up-front: a short discovery call to extract the owner’s impact language; your 5-piece evidence stack; a 48-hour live draft; and a performance-focused proposal with a reversible commitment.

Key takeaway: Evidence first, draft fast, and make the commitment reversible. That’s the AI-native close.

Discovery Call: Questions That Make the Owner Voice the Problem

Lead with curiosity, not critique. Use these in order, and write exact phrases they say—they’ll anchor your proposal.

• Lead-in framing: “You already have a site. I want to understand how it’s performing for you so I can show you where money might be leaking.”
• Traffic and intent: “What percentage of your new customers first find you online or Google you before calling? How do they usually contact you?”
• Conversion reality check: “In the last 30 days, how many web form submissions or click-to-calls did you get from the site? What’s a good month vs. a slow one?”
• Speed and mobile pain: “Have customers ever mentioned the site being slow or hard to use on phones? Do you know your mobile vs. desktop traffic split?”
• Competitive context: “When people compare you to [Top Competitor], what do you think they see online? If a neighbor is searching right now, which site looks more trustworthy side-by-side?”
• Offer and proof: “What’s your highest-margin service and average ticket size? If we added 3–5 more bookings a month from the site, what’s that worth?”
• Guardrails and timing: “If I can show you a side-by-side with your site’s gaps and a live draft that fixes them in 48 hours, would you be open to a short pilot and then a decision?”

Build the 5-Piece Evidence Stack (Visual, Mobile, Speed, Competitor, Lead-Capture)

You’re not persuading with opinions; you’re prosecuting a case. Package these five artifacts in a single share link.

1. Visual (credibility scan)

• Desktop and mobile screenshots annotated with trust gaps: missing social proof near the hero, weak above-the-fold offer, dated design cues (tiny fonts, cramped layout), inconsistent branding. Red boxes with plain-English notes beat long audits.

1. Mobile (thumb test)

• Record a 30-second mobile walkthrough: tap targets too small, non-sticky call button, header covering the hero CTA, forms with too many fields, broken viewport scaling. The majority of visits are now on mobile, so mobile conversion rules the funnel ¹.

1. Speed (load-to-first-action)

• Run Lighthouse/PageSpeed/WebPageTest. Highlight LCP, CLS, TTI; flag if mobile LCP > 2.5s (outside Core Web Vitals “good”). Show the waterfall that reveals blocking assets and oversized images. Even small delays correlate with meaningful conversion losses—make the delta visible in your report ².

1. Competitor (A/B credibility)

• Side-by-side screenshots and a simple feature table vs. the strongest local competitor: clarity of offer, trust badges, reviews placement, service area clarity, financing/guarantees, before/after gallery, booking UX. Circle exactly where the competitor builds more trust in the first 5 seconds.

1. Lead-capture (path to booking)

• Map the click path from landing to booking/call: steps, friction (CAPTCHA, multi-page forms), CTA clarity on every page, sticky call/text presence, chat availability, and tracking (no call-tracking, no form confirmations). Your deliverable: a one-page flow diagram with red friction markers and a green “ideal path.”

If you’d rather not assemble this from scratch, WebHunt.ai generates AI opportunity briefs per lead—desktop and mobile screenshots, a summary of what’s broken/missing, and a suggested pitch angle you can copy into your deck.

By the numbers: Anchor fixes to Core Web Vitals and mobile outcomes. Owners sign off faster when the “why” is quantified.

Produce a 48-Hour Live Draft: From Evidence to Tangible Fix

Translate each evidence gap into visible fixes the owner can tap on their phone.

• Above-the-fold rewrite: One clear offer (“Same-day leak repair”), immediate social proof (star rating + review count), one CTA (“Call now”)—no carousel, no fluff.
• Mobile-first UX: Sticky call/text bar, large tap targets, simplified form (name, phone, service, preferred time), trimmed nav, and legible type.
• Speed: Compressed assets, deferred non-critical JS, system/variable fonts, optimized hero media, and lazy-loaded galleries.
• Trust strip: Reviews, badges, “since 2009,” financing/guarantee if relevant.

Execution stack

• Use Framer AI to draft a clean, conversion-first layout fast, or Replit/Bolt/v0 for custom stacks. Swap in real brand copy/photos. Wire tel: links, schema, and analytics in the draft so it’s demo-ready.

Demo script

• “Here’s your site on a phone in 3 taps vs. ours. Count the steps to call.”
• “Here’s your speed report vs. the draft—LCP and TTI side-by-side.”
• “Here’s your hero copy vs. the revised one with proof and a single CTA.”

Pilot approach

• Point a subdomain or /try URL to the draft for 7–14 days. Add unique call-tracking and simple form thank-you events. If results don’t justify, revert—no lock-in.

To accelerate the build, the one-click website prompt in WebHunt.ai generates a ready-to-paste prompt for Replit, Lovable, Base44, v0, Bolt, Framer AI, Cursor, Windsurf, Codex Sites, Claude Design, or Claude Code using the business’s real details and photos. It’s the fastest path to a credible first draft.

Quantify ROI and Price to Win in the AI Era

Back-of-napkin ROI

• Avg job value × margin × expected extra bookings/month.
• Example: $900 average job × 40% margin × +4 bookings = $1,440/month lift; break-even on a $1,000–$2,000 setup in under 2 weeks.

AI-compressed costs → outcome pricing

• Position a flat setup ($0–$2,000 depending on scope/complexity) plus a performance-minded monthly ($150–$600) that covers hosting, updates, speed monitoring, call tracking, and CRO iterations.

Risk-reversal options

• Cancel-anytime monthly, a short pilot with a target metric (+30% calls/forms), or “pay on publish” after the demo hits agreed scores (e.g., Lighthouse mobile score and competitor parity on key features).

Benchmarks that de-risk the buy

• Use Core Web Vitals “good” thresholds—LCP ≤ 2.5s and CLS ≤ 0.1—as acceptance criteria for publish ³. Owners appreciate objective lines in the sand.

Handle "It’s Fine" and Other Objections with Evidence and Time-Boxed Trials

“It’s fine for now.”

• Reply with the side-by-side mobile scroll video and speed delta. Ask, “Which one would you trust with your card on your phone?” Propose a 14-day draft trial with call tracking, then decide on data.

“We just redesigned.”

• Audit the redesign against Core Web Vitals, mobile CTA stickiness, and competitor landing pages. Highlight monetized misses (e.g., no financing badge on a high-ticket service) and offer a micro-upgrade sprint.

“We don’t get leads from the website anyway.”

• Bring local search behavior stats and show competitor map-pack presence versus the site’s broken conversion path to call/booking. Even if discovery happens elsewhere, mobile UX determines who gets the call ⁴.

“Price is high.”

• Re-anchor to ROI math and near-zero switching cost. Offer to ship the top-3 fixes first (sticky call, speed, hero with proof) under a pilot fee credited to the full engagement.

Prospecting: Find Existing Sites that Are Losing Money (and Will Buy)

Go where one extra job proves ROI fast: roofing, HVAC, plumbing, pest control, med spa. Phone-first, high LTV trades convert quickly when you fix the leak points.

Qualify by weakness signals at scale

• Look for missing HTTPS, slow mobile speed, thin content/old blog, weak review momentum, and confusing booking flow. Sort by categories with current demand spikes in your city.

Prioritize owners you can reach this week

• Enrich for owner name, direct phone, and email with validation. No gatekeepers, no info@ loops.

Outreach angle

• “I recorded a 2-minute mobile and speed teardown of your site vs. [Competitor]. If I can show you a live draft in 48 hours that fixes it, would you review it?” Include one screenshot in the first email and the 30-second scroll video in the bump.

If you’d rather not build the list by hand, WebHunt.ai scores local businesses for buy-likelihood using site-quality signals (HTTPS, mobile, speed, freshness) and review momentum. Save the best leads, and when you’re ready to call, use owner contact enrichment in WebHunt.ai to pull the owner’s name, direct phone/email, with confidence scores and mobile vs. landline checks so you start with the right person. If you want meetings booked for you, the AI Voice Agent SDR and the human cold-calling marketplace in WebHunt.ai can pitch your offer and place qualified appointments on your calendar.

Proposal, Close, and Handoff: Evidence-Linked Scope and First 30 Days

Proposal structure

• Page 1: Evidence collage (5-piece highlights). Visual, mobile, speed, competitor, lead-capture gaps.
• Page 2: ROI math and acceptance metrics.
• Page 3: Scope—what ships in 7 days.
• Page 4: First 30 days of CRO iterations.

Acceptance criteria tied to evidence

• Publish when: sticky mobile CTA on all key pages; LCP ≤ 2.5s on mobile; hero above-the-fold shows offer + proof + one CTA; competitor feature parity on the top service page ⁵.

Implementation timeline

• Day 0–2: Demo build.
• Day 3: Review and capture edits.
• Day 4–5: Implement edits, speed passes, tracking.
• Day 6–7: Publish.
• Day 8–30: Track calls/forms vs. baseline, compress images, fix friction, add 2 new social-proof blocks.

Measurement stack

• Unique call-tracking number, form thank-you events, and a weekly snapshot email of calls/forms vs. baseline. Keep the summary to one screen.

For pipeline hygiene, track stages and notes. The deal pipeline and workflow in WebHunt.ai makes it simple to save leads, move them across stages, and export to your CRM or Zapier while your outreach runs.

Optional: A Simple Competitor Parity Table You Can Reuse

Use real screenshots and numbers. The point is to make “loss” unmistakable in 10 seconds.