You sent the cold email. They replied. And now the real work starts.
The five responses below cover roughly 90% of what you'll hear back when you pitch a web design redesign. Each one looks like a rejection, but most of them aren't. The prospect is telling you exactly what objection they have — and competent salespeople treat that as a gift. The rejection is only the surface.
This post is the third in our cold outreach series, after 7 templates for the first touch and the follow-up sequence that doubles replies. If the prospect isn't replying at all, the problem is usually follow-up cadence, not objection handling — check that one first.
Objection 1: "We don't need a new site, ours works fine"
What they're actually saying: They haven't connected their site to revenue, so they don't feel the pain of it being outdated.
Don't respond with: "But your site is outdated!" (They know. They don't care. Yet.)
Response that works:
Totally fair — a site that does its job is hard to argue with. Quick question: how many new clients did the site bring in last month? The reason I ask is that a site "working" usually means one of two things — either it's actively generating leads, or it's just not embarrassing you. Both are fine outcomes, but they have very different design implications.
This reframes the conversation from aesthetics to revenue. A site that's not embarrassing is a business card. A site that generates leads is a salesperson. Most prospects in this bucket are in the first category but haven't named it.
Roughly 20% of the time, the prospect replies with a number ("maybe 2 or 3?") or an honest admission ("I have no idea, probably not many"). That's the opening. Now you're talking about lead generation, not typography.
If they reply "we get plenty of business from word of mouth," thank them and close. They're not the buyer. Their site is genuinely not the bottleneck and your pitch is wrong for their business. Don't fight it.
Objection 2: "Too expensive"
What they're actually saying: Either (a) they can't see the ROI, (b) they genuinely can't afford it, or (c) they haven't been told the price and are preemptively dismissing. Your response depends on which.
Don't respond with: an immediate discount. Dropping your price the moment someone questions it teaches them the original number was negotiable, which kills trust in your pricing across the whole conversation.
Response that works:
What number were you expecting? I can usually work with most budgets if we scope the right way. Most of my clients end up somewhere between $4-8k for a full rebuild, but there are lighter options that come in well under that — depends on whether you need a full redesign or targeted improvements.
Three things happen here:
- Anchoring. You name the real range. If they were hoping for $500, you find that out now instead of chasing for a week.
- Optionality. "Full rebuild" vs "targeted improvements" gives them a cheaper choice without you dropping the price on the original scope.
- Honesty. You're not pretending every client pays the same amount. The range ("$4-8k") gives the prospect permission to be budget-conscious without feeling embarrassed.
Then you move the conversation to value: "If we could reliably bring in one new client per month, what would that be worth to you?" For most service businesses, one new client at $2-5k/month recurring crushes any price concern on a $5k one-time project.
Objection 3: "We already work with someone"
What they're actually saying: "Convince me switching is worth the friction." They're usually not committed — they're asking you to prove you'd be a clear upgrade.
Don't respond with: "Well, we can do better than them!" (Unproven, confrontational, easy to dismiss.)
Response that works:
That's great — hopefully they're doing right by you. I won't try to poach — but can I ask what made you pick them, and if there's anything the current arrangement isn't covering? Sometimes existing agencies handle the build great but drop the ball on SEO, or vice versa. Happy to either handle the gap or leave it alone entirely.
What this does:
- Respects the existing relationship. You're not the creepy competitor trying to steal their vendor. You're a professional asking where the gaps are.
- Probes for unmet needs. Every agency has gaps. Build-only agencies rarely handle SEO well. Maintenance-focused agencies rarely ship bold redesigns. If you can find the gap, you have a foothold.
- Creates low-stakes entry. "Handle the gap or leave it alone entirely" offers them a way to work with you without firing their current vendor. That lowers the decision cost.
Sometimes the prospect will say "actually, we haven't been thrilled with them." That's your opening. But let them volunteer it — don't fish.
Objection 4: "Send me more info / can you send over a deck?"
What they're actually saying: "I want to feel like I'm making progress without actually committing." In 80% of cases, "send me more info" is a polite dead-end.
Don't respond with: a 12-page PDF deck. It will not be read.
Response that works:
Happy to — but what specifically would be most useful? I've got:
- A 2-minute loom walking through the redesign I mocked up
- Case studies from 3 {{niche}} businesses I worked with recently
- A full proposal with scope, timeline, and pricing
Any of those help? Or we could just do a 15-min call and I'll walk you through whichever you care about.
Three things:
- You make them commit to a direction. A prospect who picks "the case studies" is a different buyer than one who picks "the full proposal." Now you're qualifying.
- The 15-min call is the real ask. You offered it as one of four options — the least committal one. But you've framed a call as an easier path than reading materials, which is often true for busy people.
- You're not dumping information. Every piece of content is a specific response to a stated need. That's sales discipline — don't over-inform, over-serve.
If they still don't pick anything or ghost after you offered, they were never serious. Move on.
Objection 5: "Not now — bad timing"
What they're actually saying: Could be genuinely bad timing (they just finished a big project, they're understaffed, they're mid-season). Could also be polite dismissal.
Don't respond with: pressure to reconsider now.
Response that works:
Totally understand — bad timing is real. When would be better? I'll pencil you in and reach out then. In the meantime, the redesign preview is yours — use whatever's useful, no obligation either way.
What this does:
- Takes the concern at face value. Pushing against "bad timing" reads as tone-deaf. Accept it.
- Commits them to a specific future date. "When would be better?" forces a concrete answer. "Next quarter" or "after January" or "our slow season starts in Feb." Those are commitments you can log.
- Keeps the mockup in play. Even if they never buy, the preview is out there. You've given them value. That goodwill matters if you run into their network later.
Then — and this is the critical part — actually follow up on the date they named. If they said "check back in March," your job is to make sure you do, to the day. Most agencies never follow through on deferred timing, which is why the ones that do close at 3-4× the industry rate. A clean CRM entry + calendar reminder is enough to separate you from 95% of competitors.
What never to do after an objection
Three failure patterns worth naming:
- Arguing. If the prospect says your price is too high, your job isn't to prove them wrong. It's to surface the real concern underneath. Arguing makes you right and unemployed.
- Over-qualifying. If they reply with a soft objection and you respond with a three-paragraph email asking about their goals, team size, current traffic, and tech stack, you've turned a warm conversation into a job application. Lead with a short question; save the deep discovery for the call.
- Vanishing. The most common failure isn't a bad response — it's no response. If a prospect raises an objection and you don't have a good answer ready, you'll often just... not reply. Don't do this. Even a short, honest "Let me think about the best way to address that and circle back" is better than silence.
The real skill
Objection handling isn't about having a clever comeback for every concern. It's about staying curious when most salespeople go defensive. Every objection is the prospect offering you information about what's actually in their way. Your job is to ask the next question, not win the current one.
Nail this and your pipeline stops being about how many emails you send, and starts being about how many conversations you handle well.
If you want to automate the front half of the pipeline — scraping, qualifying, sending that first email, and running follow-ups for you — that's what Scoutmap handles. The objection-handling part is still yours to own.
Related reading
- Handling "it's too expensive" specifically — deep dive on the #1 objection in this post
- How to qualify a web design lead in 60 seconds — fewer bad objections happen when leads are properly qualified upstream
- Red flags that mean you should walk away from a web design lead — some objections are signals to disengage, not work through
- How to price a web design project — the pricing framework that pre-empts most budget pushback