Yar Malik
HomeFree CourseResourcesStartupsPortfolioPartnershipsAbout
Join the community
Build a 1-Person AI Business with Claude/Sales with Claude

Course 10 · Lesson 9 of 14

Handling Objections

An objection is not a rejection — here is exactly what each one means and how to respond

An objection is not a rejection.

A rejection is "no, we are not interested, please do not contact us again." An objection is "I am interested, but there is something I need to resolve before I can say yes." That distinction changes everything about how you respond.

This lesson covers the five most common objections freelancers and service providers hear, what each one usually really means, and the Claude prompts to prepare your responses.

Why Most Objection Handling Goes Wrong

Most people respond to objections by either defending immediately, which means launching into a justification of their price, their experience, or their timeline, and this reads as defensive and raises the prospect's guard, or caving immediately, which means dropping the price, changing the scope, and offering more for less, which signals that you had no real conviction in your original offer.

Both of these are wrong. The right move is to understand the objection before responding to it. Ask a question first. Then respond to what you learned.

The Five Objections and What They Mean

Objection 1: "It's too expensive."

What they usually mean: they cannot currently afford it which is a real budget constraint, they do not yet believe the outcome justifies the cost which is a value problem, they can get something similar for less elsewhere which is a comparison problem, or they are using price as a soft no to avoid a harder conversation.

How to respond: do not apologise or drop the price immediately. Ask one question first.

"Can you help me understand — is it that the total is outside your current budget, or more that you are not sure whether it is worth it yet?"

This separates the real budget constraint from the value problem. Then respond to what they actually said.

For a real budget constraint: "The Starter package is $[X] and covers [SCOPE]. That might be a better fit for where things are right now."
For value doubt: "That's fair — let me be more specific about what I've seen this produce. [SPECIFIC EVIDENCE OR RESULT]. Does that shift the picture at all, or is it still not quite there?"

For comparison: "Who else are you looking at? I'm happy to tell you honestly how we compare and where the differences actually lie."

Objection 2: "I need to think about it."

What they usually mean: there is an unanswered question they have not asked, they need to consult someone else, they are not ready to commit yet and this is a polite delay, or they are genuinely evaluating other options.

How to respond: do not say "of course, take your time." That ends the conversation without information.

"That makes sense — what's the main thing you want to think through? I'd rather address it now if it's something I can help with."

If they say they need to check with someone: "Of course — would it be useful if I sent a shorter summary document for [PARTNER OR COLLEAGUE] to look at? I can put something together that captures the key points without the full proposal length."

If they want to compare options: "That's completely reasonable. Is there anything specific you're comparing, or gaps in what I've proposed that you want to see addressed elsewhere?"

Objection 3: "We don't have the budget right now."

What it usually means: exactly what it says, or they are saying no without wanting to say no directly.

Ask one question first: "When you say right now — is this genuinely a timing thing, or is it that this particular thing is not a priority this quarter?"

If it is genuinely timing: "That's fine — when would be the right time to pick this back up? I'll follow up then." Then add them to your follow-up list which the next lesson covers.

If it is a priority question: if solving this is not a priority then no price will close the deal. It is not an objection worth pursuing. Disqualify gracefully and move on.

Objection 4: "Can you do it cheaper if I..."

What they mean: they want more for less or they are not clear on what they actually need.

How to respond: "What would you take out?" or "What would need to come out of the scope to get to [LOWER PRICE]?"

Make it their decision about what to remove. Do not volunteer scope cuts. If they propose cuts that make the project worse for them, say so: "We can take that out, but I'd want you to know that without [X] you're likely to find [Y problem]."

Objection 5: "We've had bad experiences with freelancers before."

What they mean: they were burned and they are scared of being burned again. This is entirely reasonable.

How to respond: do not dismiss this or rush to reassure. Take it seriously.

"That's worth taking seriously. What happened? I'd like to understand what went wrong — it helps me know what I'd need to demonstrate to earn the confidence back."

Then listen. What they describe tells you exactly what evidence to bring in the proposal and what to promise specifically and measurably.

Often the solution is a paid pilot project: a smaller first project that proves you before they commit to the bigger one.

Using Claude to Prepare Your Responses

Using @MARKETING.MD and @SALES.MD — help me write personalised responses to

the five most common objections I hear.

For each objection write:

  1. The question I should ask before responding to understand the real objection
  2. A response for the most common version of this objection in my voice
  3. A response for the less common version
  4. What I should NOT say — tempting responses that backfire

The five objections:

  1. "It's too expensive"
  2. "I need to think about it"
  3. "We don't have the budget right now"
  4. "Can you do it cheaper if..."
  5. "We've had bad experiences with freelancers before"

My specific context: [ANY DETAILS ABOUT YOUR CLIENTS OR PRICING — e.g. "I charge

$800 to $2,500 for websites, typical clients are local service businesses"]

Voice: see @MARKETING.MD. Direct, honest, no corporate scripts.

Adding to SALES.md

## Common Objections and Responses
### "Too expensive"
First question: [YOUR QUESTION]
If budget: [YOUR RESPONSE]
If value doubt: [YOUR RESPONSE]
### "Need to think about it"
First question: [YOUR QUESTION]
If unanswered question: [YOUR RESPONSE]
If needs approval: [YOUR RESPONSE]
### "No budget right now"
First question: [YOUR QUESTION]

If timing: [YOUR RESPONSE — add to follow-up sequence]

If not a priority: [DISQUALIFY GRACEFULLY]
### "Scope trading"
My response: [YOUR RESPONSE]
### "Bad past experience"

My response: [YOUR RESPONSE — listen first, pilot second]

Your Action Right Now

Run the objection preparation prompt above with your real context. Read the responses out loud. Do they sound like you? Edit anything that sounds too polished or defensive. Save the final versions to SALES.md.

Then: next time you hear any of these five objections you know exactly what to ask first.

PreviousPricing Your WorkNext lessonFollow-Up Sequences

Do it with other builders

Post your homework. Get unstuck.

Every course ends with homework. Post yours in Claude Codex Mastery, the community this course comes from, and get feedback from Yar and 400+ people building the same way.

Join the community · $29/mo
Sales with Claude
  1. 1.Sales with Claude: Start Here
  2. 2.Sales Is a Conversation, Not a Pitch
  3. 3.Qualify Leads Before Every Sales Call
  4. 4.Cold Outreach That Gets Replies
  5. 5.The Discovery Call
  6. 6.Positioning Your Offer
  7. 7.Writing Proposals with Claude
  8. 8.Pricing Your Work
  9. 9.Handling Objections
  10. 10.Follow-Up Sequences
  11. 11.Closing: Asking for the Yes
  12. 12.Client Onboarding: Starting the Project Right
  13. 13.Course Summary: Sales with Claude
  14. 14.Homework: Create Your Sales System, Run It Once

Yar Malik

AI operator, educator, and founder building businesses around automation, media, and monetizable skills.

HomeAboutFree CourseBlogsPartnershipsCommunity

© 2026 Yar Malik. All rights reserved.