Objection Handling — Deep Dive
Cold-call rebuttals are the difference between 0.5% close rate and 3% close rate. Memorize these. Don't read them; internalize them. Modify the language to sound like you, but keep the structure.
The framework: ACAR
Every objection follows the same 4 beats:
- Acknowledge — never argue. "I get it" / "Totally fair" / "I was afraid you'd say that"
- Clarify — ask one question to find the real objection (the first one is rarely it)
- Address — the real objection, not the surface one
- Re-ask — for the small next step (not the close)
Pattern: [A] [C] [A] [R]
Objection 1 — "Not interested."
The real objection: They're busy and saying the magic word that makes you go away. Not actual disinterest.
Response:
"I was afraid you were going to say that. Totally get it — I called out of the blue. Quick question: is it 'not interested in a website,' or 'not interested in this conversation right now'? Because those are very different problems."
If "not interested in a website" → see Objection 7.
If "not interested in this conversation" →
"Got it, I'll stop talking. Mind if I just text you the link to the demo I built and you look at it whenever? If it's a no, throw it away."
Why this works: The "is it X or Y" reframe forces them out of the autopilot rejection. Most people, when forced to think, soften.
Objection 2 — "How much does it cost?"
The trap: Spitting out three prices on a cold call. They have no context, the prices feel high, they hang up.
Response:
"Sure — three plans, $97, $197, or $397 a month, no setup fee. Most local spots like yours are on the $197 plan. Honestly, the price is the easy part — the question is whether what we'd build is actually worth it for your business. That's what the 15-minute call is for. Free, no pitch, I just walk you through what we'd do. Are you free [day, time] or [day, time]?"
The move: Drop the prices fast (don't dodge), then immediately reframe to "is it worth it" and pivot to the meeting.
Objection 3 — "Send me an email."
The translation: "I want to get off this call."
Response:
"Will do, sending it right now while we're on. What's the best email — is it [the one on your Google profile]?"
[Send it. Live. So they can hear you tap.]
"Cool, you should have it. One quick thing while I have you — easiest way to figure out if this is even a fit is a 15-min call where I show you the demo. Are you free [day/time] or [day/time]?"
If still no:
"All good. I'll follow up [Thursday]. If the email helps, awesome. If not, no harm done."
Why this works: Sending live shows you're real. The "one quick thing" pivots back to the close before they hang up. The follow-up commitment ensures another touch.
Objection 4 — "I need to think about it."
The translation: Either an actual concern they didn't share, or a polite "no" they don't want to deliver.
Response:
"Totally — what's the part you want to think about? Is it whether you need a site at all, or whether we're the right ones to build it? Different things to think about."
Listen to what they say. That's the real objection. Address it.
If "do I need a site at all":
"Fair question. Honest answer: if word of mouth is working and you're full, you might not. But if you've ever had someone say 'I tried to find your website and couldn't,' that's the signal."
If "are you the right ones":
"Got it. What would help you decide — talking to a current client, seeing more examples, knowing more about how we work?"
End every "think about it" with:
"Cool. Let's pencil next [day] at [time] for a follow-up. If you decide before then, awesome. If not, we regroup. Sound fair?"
Never let them go without a next step booked.
Objection 5 — "I'm too busy right now."
The translation: Sometimes literal, sometimes "go away."
Response:
"Totally hear you. Two quick questions:
One — do you want me to call back at a better time, like end of day or weekend? Or
Two — do you want me to just text you the link so you can look on your own time, no call needed?"
If they pick one, run with it. If they pick "neither, just stop," respect it:
"Got it — I'll get out of your hair. Mind if I check back in 6 months in case anything's changed?"
(That last question gets a yes ~80% of the time, which is permission to re-prospect later.)
Objection 6 — "I'll talk to my partner / spouse / business partner."
The translation: Either real, or a stall.
Response:
"Smart. Can I help with that? I'm happy to get on a call with both of you so I can answer their questions directly — usually saves a game of telephone. Are they around this week?"
If real → book the call with both.
If stall → "Got it. When are you guys usually able to chat? I can pencil in 15 min so you don't have to remember to circle back to me."
Why this works: It's surprisingly hard to say "no, I don't want to schedule a call with my partner about this" if it's a real consideration. If it's a stall, they admit it.
Objection 7 — "We have a website."
The clarifying play:
"Right on, I figured. Two quick questions: when was it last redone, and is it bringing you actual leads, or is it more of a digital business card?"
Branch on the answer:
"It's old / nephew built it / etc."
"Most local sites are. Mind if I look at it real quick — what's the URL? ... Yeah, I see what you mean. Want me to mock up what we'd build instead? No charge, takes me a couple days. If you like it we talk; if not, you've got a free comparison."
"It works fine."
"That's actually great to hear, honestly. Most of the time when someone says 'it works' I'm skeptical, but you might genuinely be set. Mind if I take 60 seconds to look at it and tell you if I think you're leaving money on the table? Worst case I say 'looks great, carry on.'"
[Look at it. Find one specific thing — slow load, no mobile, no GBP integration, no contact capture, etc.]
"Cool, here's what I noticed: [specific thing]. That's costing you somewhere between [conservative estimate] and [optimistic estimate] a month in lost leads. Worth a 15-minute conversation about whether to fix it?"
"It's brand new, just rebuilt it."
"Great — congrats. Last question: who built it, and how easy is it to update? Most folks I talk to whose sites were just rebuilt say making changes is the part that broke their old setup. We're a subscription model, so updates are unlimited and 48-hour turnaround. Worth knowing in your back pocket for when you next need something changed. I'll text you my number — feel free to use it."
(Plant the seed. They'll call in 6 months when their developer ghosts them.)
Objection 8 — "Just send me your portfolio / pricing PDF / brochure."
The translation: Wants more info before committing to a call.
Response:
"Will do. Quick clarification — are you wanting to see examples of sites we've built or more about how the pricing/process works? I want to send the right thing, not dump a brochure on you."
If portfolio:
"Cool. I'll send you the [demo I built for you] and one or two other examples. Honestly the demo is way more useful because it's literally what your site would look like."
If pricing:
"Sure — I'll send you the one-pager. Two things to know: $97 Starter, $197 Growth (most folks land here), $397 Pro. No setup fee is the part most people don't expect. Anything else you want me to include in the email?"
End with:
"I'll follow up Thursday after you've had a look. Best time?"
Objection 9 — "How long does this take?"
The trap: Quoting a vague timeline that sounds slow.
Response:
"Faster than you think. First preview in 48 hours, live on your domain in 7 days. The catch is your responsiveness — if you can give me 30 minutes for a quick intake form and 30 minutes to look at the preview, we hit the timeline. If you ghost me for a week, it slips. Most clients land on day 7."
Why this works: Specificity beats vagueness. Putting some of the timeline on them (responsiveness) primes them to actually be responsive when you do start.
Objection 10 — "Can you just build it for a one-time fee?"
The reason this comes up: They've been burned by subscriptions OR they're trying to cut a deal.
Response:
"I get the question — totally fair. Honest answer is no, and here's why: a website isn't a one-time thing. Hours change, menus change, you get a new staff member, your hosting bill comes due, security patches come out. The subscription means you don't get a $5,000 surprise invoice in 18 months when something breaks — and we stay invested in your site actually working long-term.
The math: subscription is $197/month. A one-time custom site is usually $5,000–$8,000, plus hosting at $20–$50/month, plus you call someone every time you need a change at $100/hour. After 24 months, the subscription is cheaper and you've never had a bill you didn't expect."
If they push: "Look, totally understand if it's not the model for you. Lots of agencies do one-time builds. Want me to recommend a freelancer who's good?"
(Walk away willingly. Subscription is the model. Don't dilute it for one client.)
Objection 11 — "How do I know you're not going to disappear?"
The translation: They've been burned.
Response:
"Best question. Three things:
One — you own your domain and your content from day one, in your accounts, not mine. If we vanish tomorrow, you take your domain and find someone else.
Two — if you cancel, we send you a static export of your site. You can host it for $5/month forever if you want.
Three — month-to-month, no contract. The day we stop earning your subscription, you stop paying. We've designed this so we have to keep delivering or you leave."
Why this works: Direct, specific, addresses the actual fear. Bonus: subtly reframes you as the careful, considerate operator vs. the agency that burned them.
Objection 12 — "Why are you so cheap? Other agencies want $5k+"
The translation: Skepticism, sometimes anchored in past quotes.
Response:
"Two reasons we're cheaper. One — subscription model, so we make our money over time, not up front. Cheaper to start, but we earn more over the lifetime of the relationship. Two — we use modern tech (static sites, CDN hosting) that costs us almost nothing to run, vs. agencies still selling WordPress installs they have to babysit.
So no, you're not getting less. You're getting the same or better, just on a different business model."
If they push: "Want to see a comparison? I can put together a 'one-time agency vs. us over 24 months' chart."
(Then actually do it. Spreadsheet. Send it.)
Objection 13 — "Send me references."
Response:
"Sure thing. Couple options:
One — I can give you the number of [current client] who's been with us [N] months. You can call them and ask anything you want. I won't even prep them.
Two — I can send you the live site for [current client] so you can see the work for yourself.
What's more useful?"
Important: Always ask the client first. Don't give a phone number without permission. Most clients are fine to be a reference if you ask.
If you don't have any clients yet (you're brand new), say so:
"Honest answer — you'd be one of our first clients, so I don't have references yet. What I can do is offer you our 'first client' deal: same pricing, but I'll guarantee in writing that if you're not 100% happy in 90 days, I refund every penny and you keep the static export of your site to do whatever you want with."
(Risk reversal closes nervous prospects.)
Objection 14 — "I'm going to look at a few options first."
Response:
"Smart. Two thoughts:
One — if you're comparing us to other subscription web designers, here's what to ask them: 'Do I own my domain? What's your turnaround on edits? What happens if I cancel? Is there a setup fee?' Those four questions will sort the real ones from the sketchy ones.
Two — I'd love to be on your shortlist. Want me to send you a one-pager you can compare against the others?"
End with:
"When you've talked to a few, can we set up a follow-up to compare notes? I'd say [Friday]?"
Why this works: You're being a helpful guide, not pushing. Most prospects don't actually shop seriously — they call you, get warm, and forget to call others. By asking the comparison questions, you give them tools (which they'll actually use against your competitors) and stay top of mind.
The "spiral" close (use sparingly, on warm prospects)
When someone is in the "thinking about it" zone but not committing, try this once per call:
"Can I be straight with you for a second? You've got a real business that's clearly working. The site is going to happen eventually — either you build it now and it works for the next 3 years, or you build it in 6 months after losing some unknown number of customers in the meantime. I'm not trying to push, just being honest about what I see.
Is there anything I could say that would make you a 'yes' today, or are we just at 'not yet'?"
If "not yet" → respect it. Book the follow-up.
If "well, if you could..." → they're telling you exactly what to do. Do it.
Don't run this on every call. It's a tool, not a hammer. Misused it sounds desperate.
What every objection has in common
Almost every objection is one of three things:
- Information gap — they don't have the info they need to say yes (price, timeline, examples). Give it.
- Trust gap — they've been burned or don't know you yet. Reduce risk (references, guarantees, owning your own domain, cancel-anytime).
- Priority gap — they have other fires. Either show why this is the priority, or schedule for later (don't push for now).
When you hear an objection, ask yourself which gap it is. The right response depends on the gap, not the words.
Practice plan
The only way these become muscle memory is repetition. Out loud. To yourself, to a friend, to a wall.
Week 1: Read this doc once a day. Practice each objection out loud with the script in front of you.
Week 2: Practice without the script. Record yourself. Listen back.
Week 3: Have a friend roleplay objections. Try not to peek.
Week 4: Real calls. Track which objections came up, which responses worked, which fell flat. Refine.
After 4 weeks, you'll never freeze on a cold call again.