How to Sell Website Redesigns: Pitch, Scope, and Price

By Cameron Kirdzik — Founder @WebHunt.ai

August 25, 2026 · 8 min read

The AI-era reality: You don’t win on craft—you win on proof and speed

Owners don’t say “no” to redesigns; they say “my site is fine.” That’s status-quo bias. You break it with side-by-side evidence that shows what’s leaking: mobile UX, speed, and lead capture—not opinions about color palettes.

AI site builders compressed delivery from weeks to hours. Your edge isn’t vague promises; it’s proof on the spot. Show a live, mobile-first concept during the call. Offer a no-risk path to approval and a switch only when they’re happy.

Reframe the value: you’re not selling a prettier site—you’re selling more booked jobs and fewer leaks in the funnel. Set promises you can keep: same-week delivery for a refresh, 3–5 business days for a light rebuild, and a first preview within 60 minutes of discovery with Replit, Lovable, or v0.

If you need a steady stream of qualified redesign targets, WebHunt.ai surfaces local businesses with weak, slow, or outdated sites and scores each one for buy-likelihood—so you start with owners most likely to feel the pain.

Key takeaway: Don’t debate taste. Show evidence, then show a working alternative before the call ends.

The 5-piece evidence stack that beats 'my site is fine'

Assemble this in advance so the “reveal” takes 5–8 minutes, not a lecture.

1. Visual clarity

• Side-by-side desktop and mobile screenshots of their current site versus a clean reference (or your draft concept).
• Call out above-the-fold clarity: headline, one-sentence value prop, primary CTA, and trust signals (review count, badges, warranties). If these aren’t visible without scrolling, that’s money left on the table.

1. Mobile usability

• Show where the layout breaks, font sizes are small, tap targets are cramped, and there’s no sticky call button.
• Mobile accounts for roughly 60%+ of web traffic today—weak mobile means fewer bookings.¹

1. Speed and Core Web Vitals

• Pull PageSpeed Insights for their homepage and a key service page. Highlight LCP/INP/CLS in plain English: “Your homepage takes 5.8s to become usable; slower pages shed leads, and Core Web Vitals are part of search visibility.”²
• Translate to revenue: “If 100 people visit and half bounce before the page loads, that’s lost calls.”

1. Competitor comparison

• Two or three local competitors with faster speeds, clearer service pages, and stronger mobile UX. Show their SERP presence and how their Google Business Profile and site work together (reviews above the fold, click-to-call).³

1. Lead-capture friction

• Count clicks from landing to call/form. Compare their 7-field form vs. a 3-field quick-quote. Note missing click-to-call on mobile, no after-hours capture, or no sticky CTA.⁴

How to assemble fast

• Pre-pull screenshots and PageSpeed URLs into a single deck.
• If you’d rather skip manual prep, WebHunt.ai provides AI “Deep Analysis” briefs per lead with desktop and mobile screenshots, what’s broken, and a suggested pitch angle—use it as your evidence backbone.

By the numbers: Speed, mobile, and friction are the silent killers. Owners stop arguing when they see their site lose to a neighbor’s on a phone in 30 seconds.

Run the discovery like a close: deploy evidence, then live-demo a better version

Structure the call to earn permission for a live concept demo.

Call flow (10–20 minutes)

1. Baseline goals (2–3 minutes): “How many bookings a week? From where: search, referrals, ads?”
2. Evidence deck (6–8 minutes): Show the five proof points. Keep it tight.
3. Permission pivot (30 seconds): “Want to see those fixes live?”
4. Live demo (6–10 minutes): Build or reveal a draft.

When to deploy the live demo

• Use it when the owner sees issues but hesitates on risk, downtime, or sunk cost. “Show-before-you-commit” removes fear.

Prep what you need for a <60-minute draft

• Logo (right-click from current site), brand colors (eyedropper), 3–5 hero photos, services list, 3 top reviews, primary CTA (phone/email). That’s it.

Build stack

• Paste a prepared prompt into Replit, Lovable, or v0 to generate a 1–3 page draft (Home + top service + Contact) with a sticky mobile CTA.
• To accelerate, use the one-click website prompt from WebHunt.ai on the lead— it pre-fills a builder prompt with real business details and photos for Replit, Lovable, Base44, v0, Bolt, Framer AI, Cursor, Windsurf, Codex Sites, Claude Design, or Claude Code. You’ll have a live draft in minutes.

Close the loop

• Show the draft on your phone, run an instant speed test, and compare that score versus their live site side-by-side in-screen. Ask them to tap the sticky call button on their own phone.

Script the low-friction next step

• “If I finish this by tomorrow, I’ll put it at a hidden URL. You approve it first—no switch until you’re happy. Fair?”

The 8-question decision tree: refresh or rebuild?

Use these eight questions to scope the lightest path to outcomes.

1. Is the current CMS/theme maintainable and mobile-responsive without breaking design? If no or brittle, lean rebuild.

2. Is LCP > 3.0s or INP poor on core pages after basic optimizations (image compression, lazy-loading, minify)? If it still fails, rebuild on a lighter stack.

3. Does the information architecture match how buyers search today (services, locations, FAQs)? If key services are buried/missing, rebuild or a major IA refresh.

4. Are there brand assets to keep (logo, colors, typography) that the owner values? If yes and layout is the main issue, a refresh can suffice.

5. Any platform lock-in or plugin conflicts blocking updates (legacy WP theme, dead page builder)? If yes, rebuild.

6. Does content need more than a 30% rewrite (offers, service areas, FAQs, reviews)? >30% = rebuild or hybrid; <30% = refresh viable.

7. Compliance/security gaps (no HTTPS, ADA basics, cookie notices, outdated PHP)? Multiple gaps together favor rebuild.

8. Net-new features needed (multi-location, online booking, quote flows)? If yes, rebuild or modular expansion.

Decision rule of thumb

• 0–2 rebuild flags = refresh.
• 3–4 = hybrid (template + IA cleanup + speed).
• 5+ = full rebuild.

Document each answer in the proposal so the owner sees change tied to specific evidence, not guesswork.

If you need to reach the real decision-maker to run this process, WebHunt.ai can enrich leads with owner names, direct phones, and emails (with confidence scoring), so your discovery invite hits the right person.

Pricing in the AI era: three-option proposal that lets them choose risk

Anchor on outcomes, not hours. Delivery is compressed; your fee buys fewer leaks and more calls.

• Option A — Refresh ($300–$800)

  • Keep platform, fix mobile sections, compress images, simplify hero, add sticky CTA, shorten form, basic speed tuning, light on-page SEO.
  • Delivery: 24–72 hours.
  • Risk reversal: pay-on-approval.

• Option B — Rebuild Lite ($800–$2,500)

  • Move to a lightweight stack/theme. 3–7 pages (Home, 2–4 services, About, Contact), copy refresh, reviews showcase, analytics, basic schema.
  • Delivery: 3–7 days.
  • Terms: 50/50 or milestone-based.

• Option C — Rebuild + Growth ($2,500–$6,000 + $300–$1,000/mo)

  • All of B plus 3–6 extra pages, location/service-area buildout, blog templates, lead magnets, quarterly CRO tests, reporting.
  • Delivery: 1–2 weeks.

Price rationale you can say

• “Build time is cheap now. You’re buying outcomes—more calls and quotes—plus a 30-day tune-and-tweak window post-launch.”

Protect your margin

• Out-of-scope: custom integrations, advanced booking systems, heavy copywriting/photoshoots, complex multi-location SEO.
• Add a $99–$199/mo Care plan (backups, uptime, updates) so “doing nothing” isn’t perceived as cheaper long-term.

Make the 'cost of doing nothing' unmistakable

Start with their numbers

• Baseline: monthly visitors, form submissions, calls, close rate, average job value.
• Example: 1,500 visits/mo × 2.0% lead rate = 30 leads × 50% close × $600 avg job = $9,000/mo. Lift mobile UX and speed to hit 3.0% and you add ~15 leads × 50% × $600 = +$4,500/mo. Option B pays back in under a month.

Use simple, sourced facts to justify the lift

• About half of mobile visitors abandon pages that take more than 3 seconds to load—slow hurts.⁵
• Faster pages improve user engagement and conversions; Core Web Vitals also influence search visibility.
• Mobile represents the majority of browsing—small mobile UX wins compound across most visitors.¹

Tie it back

• “If we do nothing, that 1% gap is ~$4,500/mo lost—over $50k/year. Option B fixes the leaks this week.”

Objection handling that respects the owner's risk calculus

• “It looks fine to me.”

  • Show side-by-sides on mobile and your speed delta. Hand them your phone and ask them to tap the current site’s tiny buttons vs. your sticky CTA.

• “We just redid it 2 years ago.”

  • Acknowledge sunk cost. Then show how competitors evolved and speed benchmarks changed. Offer Option A (refresh) first so they can get value without reliving a full build.

• “I don’t want downtime.”

  • Promise a hidden URL, off-hours DNS cutover, and an instant rollback plan. Show the staging link live.

• “I’m not sure it’ll pay off.”

  • Walk through the cost-of-inaction math with their numbers. Offer a 30-day pilot (Option A) with upgrade credit toward B/C.

• “I don’t have content.”

  • Draft from the current site, reviews, and Google Business Profile using AI; the owner edits. Cap their time at 15–30 minutes.

Close move you can use anytime

• “Before we end, let me show you your new mobile hero live.” Build a 1-section hero in under 10 minutes. Tangible beats theoretical.

If you’re juggling many prospects, WebHunt.ai can even run an AI Voice Agent SDR to book qualified discovery calls onto your calendar, so you spend your time on demos and closes.

Proposal and next steps checklist (so approval is the easy answer)

• Attach an evidence appendix: screenshots, speed scores, competitor notes, and the live demo link.
• Scope table: map each of the 8 decision-tree answers to included tasks.
• Timeline: draft-by-tomorrow for Option A, 3–5 business days for Option B. Include the exact cutover window and rollback.
• Deliverables: page list, copy sources, analytics setup, call tracking, schema basics, handoff docs, 30-day tweak window.
• Payment terms and risk reversal: one line each. Include the Care plan and optional growth retainer.
• Follow-up cadence: same-day recap, a 48-hour nudge with a 2–3 minute Loom walkthrough, and a 5-day “last call” with a small expiring incentive (e.g., first month of Care free).

To keep everything moving, save the lead and track deal stages in WebHunt.ai—its pipeline and workflow tools make follow-ups, exports, and automation straightforward when you’re running multiple proposals.