The dollar amounts in this lesson are made-up round numbers. They show how the conversation and the math work, not market prices and not what you'll earn.
The gist
Closing isn't about pushing something on a client that they don't need. Closing is helping a person make a decision they've almost made on their own. If you've done your work right, they'll thank you for closing the deal. Not for "talking them into it," but for getting them out of analysis paralysis.
In this lesson we'll cover how to handle the usual objections ("it's too expensive," "I need to think about it," "I'll talk it over with my team"), 5 closing techniques, the structure of a 45-minute sales call, and how to follow up properly after a demo.
The main problem we're solving: prospects (potential clients) in your pipeline (your list of deals in progress) say "sounds interesting" and then go quiet. That isn't their problem. It's a sign that your process has no moment where they make a decision. Closing is creating that moment.
🎯 The closing mindset
Before any techniques, you need the right mindset. Without it, every technique turns into manipulation, and the client can feel it.
Four beliefs that change everything:
You sell solutions to problems the client already has. You don't create a want out of thin air or "educate the market." If the person doesn't have the problem, don't sell to them. Find someone else.
If your product is the right fit and the price works, closing the deal is a helpful thing to do. You're not "squeezing money out of them"; you're shortening their time-to-value (how long it takes them to see results). Every month without your solution is a month of benefit they miss out on.
If it's the wrong fit, don't sell. The refund request comes in 30 days, the bad review in 90, and the damage to your reputation lasts for years. Better to pass on a bad deal than to close it and then spend your time putting out fires.
Patience. Sometimes the right time is "not now." That's normal. Not now doesn't mean never. A good follow-up in 3 to 6 months converts better than pressure today.
Key concepts
- Objection: the client's reason for not signing right now. It can be stated openly ("it's too expensive") or hidden ("I'm not sure this will work for me")
- Hidden meaning: what the client really means behind the objection they voice. "Too expensive" often means "I don't see the value"
- Closing technique: a structured way to ask for a decision at the right moment
- Sales call structure: the order of stages in a conversation, from rapport (a friendly, human connection) to signing
- Follow-up cadence: the schedule of contacts after a demo: when to write, what to write, when to stop
- Discounting strategy: when and how to give a discount without cheapening your product
- Quid pro quo: "something for something." You only give a discount in exchange for something from the client (paying for a year up front, buying more than one product, a longer contract)
- Decision maker: the person who actually has the authority to sign. Often it isn't the person you're talking to
- Graceful rejection: closing out a deal that didn't happen in a way that keeps the door open
Theory
8 common objections and how to handle them
An objection isn't a refusal. An objection means "I want to buy, but X is in the way." Your job is to find out what X is and remove it.
The main rule: don't argue, dig deeper. Every objection has a hidden meaning. Often the real reason is different from the one the person says out loud.
Objection 1: "It's too expensive"
The most common objection, and the most misunderstood.
❌ Wrong response: "How about a discount?"
Why it's bad: you confirm that the product is overpriced, you lower your own value in their eyes, and you open the door to more haggling. Most important, you haven't solved the real problem.
✅ Right response:
"I hear you. Help me understand: what are you comparing it to? And let's look at the value you'd get. If it returns several times what it costs in the first year, is it still too expensive?"
Hidden meaning: more often than not, "too expensive" means "I don't see the value." The person doesn't understand what they'll get for the money. Your job isn't to drop the price but to raise the perceived value.
Sample dialogue:
Client: $5,000 a month is expensive.
You: I understand. What are you comparing it to? Doing it
yourselves, hiring someone, a different tool?
Client: Hiring a junior developer.
You: Okay. Say a junior is $4,500 a month in salary, plus
about $1,500 in payroll taxes and benefits. That's
$6,000 a month, plus around 3 months to get up to speed.
We start right away, on the work we scoped together.
Over one quarter, that's $15,000 with us vs. $18,000 for
a new hire who spends most of that quarter still
learning. Does that way of looking at it make sense?Objection 2: "We don't have the budget right now"
❌ Wrong response: "Okay, can you wait?" (passive: you lose momentum)
✅ Right response:
"Understood. When's your next budget review? We could lock in the terms now, and I'll get you rolled out quickly as soon as the budget frees up."
Or an alternative:
"We could start with a smaller starter tier at $X. It's a small test investment, and you'll see whether it works for you. If it does, you can expand once the budget is there."
Hidden meaning: sometimes it's true (there really is no money), sometimes it's a polite brush-off. One way to tell: offer a concrete plan to work around it. If they're willing to talk about a timeline, it's a real budget issue. If they turn vague, it's a hidden "no."
Objection 3: "I need to think about it"
The most dangerous objection: it sounds soft, but often it's a polite "no."
❌ Wrong response: "Okay, take your time" (you lose the deal for good)
✅ Right response:
"Of course. What specifically do you want to think over? Knowing that will help me support your decision better."
After this question, the real objections often come up, the ones the person hadn't said out loud: "I'm not sure this will work for us," "I'm worried about explaining it to my team," "I'm afraid of making a mistake."
Sample dialogue:
Client: I need to think about it.
You: Of course. What specifically: the price, the features,
the timing of getting it set up?
Client: The timing, mostly. We're rolling out another system
right now, and I can't take on both at once.
You: Got it. When do you expect to wrap up that rollout?
Client: In about 6 weeks.
You: Okay. What if we sign now and set the start date for
6 weeks out? You'll be ready by then, and the terms
are locked in. Would that work for you?Objection 4: "I'll talk it over with my team"
❌ Wrong response: "Call me when you decide" (you lose control of the process)
✅ Right response:
"Makes sense. Who else is involved in the decision? I'd be glad to join that meeting and answer their questions directly. Otherwise all the questions land on you, you won't have every detail on hand, and the decision drags on."
The main rule: get the decision maker on the call. If you're talking to someone who isn't the decision maker, your job isn't to "convince them to convince the others." It's to get access to the people who actually decide.
Whoever retells a pitch secondhand loses much of the nuance. You gave a great presentation, and your champion (the person inside the company who's on your side) passes it along in one line: "looks expensive."
Objection 5: "We already use [competitor]"
❌ Wrong response: "Well, we're better" (defensive: you sound like a salesperson who knows nothing about the client)
✅ Right response:
"Tell me, what's working well for you in [competitor]? What do you wish worked better? I'll show you how we handle exactly those gaps."
Position yourself as a complement, not a replacement. Not "throw that out and buy ours," but "you've already invested in X; we add Y where X is weak."
Sample dialogue:
Client: We use Notion for our documentation.
You: Good choice. What's working well in Notion?
Client: The knowledge base, the templates, working on it as a team.
You: And what do you wish worked better?
Client: Search is slow, the AI is weak, exporting is clunky.
You: Got it. Those are exactly the three things we handle.
Notion stays your knowledge base, and we add search by
meaning on top of it. Not a replacement, an add-on.Objection 6: "I'll try the free version first"
❌ Wrong response: "Sure, here's a 14-day trial" (for a high-ticket product, that's a loss)
✅ Right response (for high-ticket products):
"A trial is one way to go. Another is a 30-day money-back guarantee, which gives you full access with no limits. Which fits you better?"
Why a money-back guarantee beats a trial:
- A trial = limited features, so the client doesn't see the real value
- A trial = no commitment, so it's easy to "forget" and drop off
- Money-back = the full experience + skin in the game + a strong psychological commitment
When a trial makes sense: low-ticket software ($20 to $100/month), self-serve onboarding, a mass market. For $1,000+/month, a money-back guarantee is almost always the better choice. Only offer a guarantee you can actually honor, and put its terms in writing.
Objection 7: "I'm not sure this is for me"
❌ Wrong response: "It's for everyone!" (a red flag: generic, and it pushes people away)
✅ Right response:
"I understand. Tell me, what's making you hesitate? If it isn't a good fit, it's better for both of us to find out now than 3 months after you sign."
The key point: show that you're willing to say "don't buy this" if it really isn't a fit. That builds trust fast. The client sees that you aren't desperate for their money.
Objection 8: "AI doesn't work for us"
A common objection from people who've already tried AI and were disappointed: the chatbot made up facts (that's called a hallucination: AI confidently making things up), or the automation broke within a week.
❌ Wrong response: "Our AI is excellent" (not convincing)
✅ Right response:
"What exactly went wrong last time? Often the problem is in the setup or the integration, not in the technology itself. I'll show you what we do differently."
Hidden meaning: the client got burned on an earlier attempt. Your job is to separate your product from that bad experience. Concretely: "Where exactly did it break? Walk me through what happened."
5 closing techniques
You've handled the objections; now it's time to close. Five main techniques, each for its own situation.
Technique 1: The assumption close
You assume the decision has already been made and offer a choice only about logistics.
"When would you like to get started: this Tuesday or Thursday?" "Onboarding this month or next?" "A one-year contract, or should we start with a quarter?"
When it works: the client has already shown clear interest. They've seen the demo, nodded along, asked questions about implementation. It doesn't work on a cold prospect; there it comes across as pressure.
Technique 2: The summary close
You sum up everything you've discussed and end with a gentle ask.
"So, to sum up: you need [pain point], we do [solution], the price is [$X], and you get [outcome] within [timeframe]. Ready to get started?"
When it works: at the end of a long demo or several meetings. It reaffirms the value before you ask. It helps the client hear once more why they've almost said yes.
Structure of the summary:
- Their problem (the way you heard it)
- Your solution (specific, not generic)
- The price (no apologies)
- The expected result
- The ask: "Ready to get started?"
Technique 3: The alternative close
Not "yes or no" but "A or B."
"Would you like the Starter tier or the Growth tier?" "Should we start with one team, or the whole company right away?"
When it works: the client is torn between being ready and being cautious. The alternative close takes away the yes-or-no stress ("buy or don't buy") and turns it into an easier choice ("which one").
⚠️ Careful: it doesn't work if the client isn't convinced about the product in the first place. Sell the "why" first, then use the alternative close for the "how."
Technique 4: The urgency close (use with care)
You point to a real deadline.
"We have 3 onboarding spots this month. Would you like one of them?" "Our prices change on the 1st of next month. Would you like to lock in the current one?"
When it works: only if the urgency is real. If you invent a limit that doesn't exist, the client feels manipulated.
❌ Manipulative urgency damages trust in the long run. "Today only!" works once; then the client feels deceived, and your reputation takes a hit.
✅ Honest urgency works: "We have capacity for 3 implementations this quarter, and two are already booked."
Technique 5: The question close
A direct question about whatever objections are left.
"What would you need to see to get started today?" "Is there anything holding you back from signing right now?"
When it works: at the end of a meeting, when you sense the client is ready but something is holding them back. You bring the remaining objections to the surface so you can address them.
The pattern: the client often names something concrete ("I need to see a case study from my industry," "I need to understand how it connects to our CRM"). That's your chance to clear the last obstacle.
Sales call structure (45 minutes)
Every successful sales call has a structure. Without one, you spend 30 minutes pitching features and lose the client.
0-3 min: Rapport ("last time we talked about...", "how did that launch go?")
3-10 min: Recap their situation (let them retell it: they sell themselves)
10-25 min: Demo / proposal walkthrough
25-35 min: Q&A + handling objections
35-42 min: Pricing + close attempt
42-45 min: Next steps (signing the contract / follow-up)Why this structure works:
- Rapport first: it eases the tension, and the person opens up. Without rapport, it's a formal interview, not a conversation.
- Recap their situation: the most underrated step. You don't retell it; the client retells it themselves. When people describe their pain out loud, they sell themselves. Your job is to ask follow-up questions.
- Demo in the middle third: the client has already told you where it hurts, so you show exactly that remedy. Not a generic tour, a targeted one.
- Pricing only after value: never before. A price without context is a shock. A price after the value is clear is a logical investment.
- A close attempt, always: not "hopefully they'll sign," but a clear ask.
- Next steps in writing: you send them right after the call.
Don't:
- ❌ Pitch features for the first 30 minutes (you lose the prospect)
- ❌ Be too soft (no clear ask = no close)
- ❌ Push hard after a "no" (leave the door open)
- ❌ Give the price at the start (it lands with no context)
Handling rejection (gracefully)
Not every deal closes. That's normal. Here's how to close it out without burning bridges:
"Thanks for being straight with me. If things change, the door's open. And may I ask: is there anyone you know who might find this useful?"
Three key elements:
- Acknowledge it without taking offense. Not "too bad it didn't work out," but "thanks for the straight answer."
- Leave the door open. Be specific: "I'll check in with you in 3 months, okay?"
- Ask for a referral. If they aren't a fit themselves, who in their circle might be? Some of your best clients may come through referrals from people who didn't buy.
Stay in touch: a quarterly check-in, not a push but something of value:
- "I saw an article about your industry and thought it might be useful"
- "We launched feature X, and I remembered you'd asked about it"
- "It's been a quarter. Has anything changed on your end?"
Follow-up cadence after a demo
Five touchpoints over the first month, then a check-in at day 90 and quarterly after that.
Day 0 (after the demo): thank-you email + recap + a clear next step Day 3: a gentle follow-up: "any questions?" Day 7: add value (a relevant article / case study) Day 14: a final "closing the loop" message Day 30: a re-engagement attempt Day 90: "checking in": the quarterly cadence begins
What goes into each touchpoint:
Day 0: within 4 hours of the call. Not the next morning. Structure:
Thanks for your time. To recap:
- Your situation: [recap]
- What we'll do: [recap]
- Price: [recap]
- Next step: [specifics]
I'm available [date/time] to answer your team's questions.
Day 3: short and personal. Not automated. Not "just checking in."
Hi [name], I've been thinking about our conversation. If anything about X is unclear, call me directly.
Day 7: add value. Not a sales push.
I came across this article about [their topic] and thought it was relevant to what we discussed: [link].
Day 14: a direct "closing the loop."
[Name], this is my last follow-up. If this isn't the right time, just let me know; I'll close the file and stay in touch for when things change. If you have questions, give me a call.
Day 30: re-engagement around a trigger event (some news at the client's company).
I saw that you [company news]. That often leads to [our use case]. Would it make sense to pick our conversation back up?
Day 90+: quarterly value, not sales.
Don't:
- ❌ More than 5 touchpoints in the first 30 days: that starts to feel like stalking
- ❌ A generic "checking in" with no content: annoying
- ❌ Automating personal follow-ups: the client can tell
Pricing presentation (how to show the price)
Presenting the price is a skill of its own. Do it wrong and you lose deals that could have closed.
Rules:
- DON'T start with the price. The client doesn't understand the value yet. A price without context is a shock.
- Show pricing after the demo, once the value is quantified. When the client sees the solution and understands the result, the price becomes an investment, not a cost.
- Frame it as "An investment of $X gets you [outcomes]," not "The cost is $X."
- Don't apologize for the price. No "I know it's a lot, but..." Say the number calmly and confidently.
- Don't offer a discount nobody asked for. It signals "this product is overpriced."
A pattern for presenting the price:
"Okay, let's talk about the investment.
[Tier 1]: $X/month, for [type of customer], gets you [outcomes].
[Tier 2]: $Y/month, for [type of customer], gets you [outcomes + extras].
[Tier 3]: $Z/month, for [type of customer], gets you [outcomes + extras + more extras].
Based on what you've told me, [Tier 2] is the right fit for you.
$Y/month = $Y x 12 a year, and it pays for itself in [N months] through [savings/revenue].
Ready to start with that tier?"Discounting strategy (when and how)
A discount is a tool, not a way to defend yourself. Use it strategically.
When a discount is justified (always tied to a concession):
| Type of discount | Size | What you get in return |
|---|---|---|
| Annual prepay | 15-20% | They pay for a year up front (cash flow for you) |
| Multi-product bundle | 10-15% | They buy several products (expansion) |
| End of quarter/year | 10-20% | They close before a deadline (cash flow + your numbers) |
| Competitive switch | 20-30% for the first year | They switch over from a competitor (a new customer won) |
| Multi-year contract | 10-15% a year | A commitment for 2-3 years |
The sizes in the table are the course's rough guides, not a market norm. Work out your own with the pricing lessons.
Never:
- ❌ A discount "because the client asked" with no quid pro quo
- ❌ A discount over 30%: it cheapens the product for good
- ❌ Discounts for regular customers with no clear reason: you train them to haggle
The rule: always tie it to a concession. "I'll give you 15% if you prepay for the year" is fine. "I'll give you 15% because you're a nice person" is a disaster for your brand.
Contract and legal essentials
The minimum set of terms your contract should have:
- Auto-renewal: yes by default, with easy cancellation (30 days' notice)
- Term: monthly by default, with an annual option (at a discount)
- Cancellation policy: 30 days' notice is typical
- Refund policy: clear, and posted on your landing page
- Data ownership: the client owns their data; you process it
- SLA (Service Level Agreement): uptime (99.9%) and response time (24 hours is typical), for higher tiers
- DPA (Data Processing Agreement): needed when you handle personal data on behalf of a client in the EU (GDPR calls for a written contract), and often expected in regulated industries such as healthcare and finance
Sample terms for small AI projects:
- Monthly contracts by default (low commitment, easier to close)
- An annual option at 15-20% off (for those it suits)
- A 30-day refund window (for first-time customers)
- Auto-renewal with an email reminder 14 days ahead (no surprise charges)
⚠️ This is a starting checklist, not legal advice. Rules on auto-renewal, cancellation and client data vary by state and by industry, so have a lawyer review your contract template before you use it.
Common pitfalls
The most frequent mistakes that kill your close rate:
❌ Talking more than you listen. The rule: listen at least 60% of the time, talk 40%. If you talked for 80% of the call, the client will walk.
❌ Discounting without a quid pro quo. Give one discount with no conditions and you've taught the client to haggle. Every renewal after that turns into a negotiation.
❌ Not asking for the sale. "Hoping they'll sign" is passive. Every sales call should end with a clear ask.
❌ Too many follow-ups. More than 5 touchpoints in the first 30 days starts to feel like stalking. Respect the client's "not now."
❌ Pressure tactics. Manipulative urgency and fake deadlines work once; then your reputation suffers for years.
❌ Bad-mouthing competitors. "X is bad" sounds unprofessional. Better: "X is good for Y; we focus on Z."
❌ Promising features you don't have. A deal closed on features that don't exist = a refund + a bad review within 30 days + a hit to your reputation.
Practice
Step 1: Write your objection response script
Create a document with your responses. A Google Doc or the notes app on your phone works; if you keep a project folder on your computer, name the file sales/objections-script.md:
# Objection Response Script ## "It's too expensive" **My response:** "I understand. What are you comparing it to? And let's look at the value you'd get: if it returns [N] times what it costs, is it still too expensive?" **Diagnostic questions:** - What are you comparing it to (doing it yourselves / hiring / another tool)? - What budget did you plan for this problem? - Would a 6-12 month payback work for you? ## "We don't have the budget right now" **My response:** "When's your next budget review? We can lock in the terms now and roll out once the budget frees up." ## "I need to think about it" **My response:** "What specifically? The price, the features, the timing?" ## "I'll talk it over with my team" **My response:** "Who else is involved in the decision? I'm happy to join that meeting." ## "We already use [X]" **My response:** "What's working in X? What do you wish worked better?" ## "I'll try the free version first" **My response:** "A trial or a money-back guarantee: which fits you better?" ## "I'm not sure this is for me" **My response:** "What's making you hesitate? Better to find out now." ## "AI doesn't work for us" **My response:** "What exactly went wrong last time?"
Learn it by heart. Don't read from the page during a call; people can tell. It should come out naturally, in your own words.
Step 2: Structure of a 45-minute sales call (template)
Create a second document (or the file sales/call-template.md):
# Sales Call Template (45 min)
## 0-3 min: Rapport
- "How did [what we talked about last time] go?"
- Not straight to business: a human connection first
## 3-10 min: Recap their situation
- "Could you remind me briefly: what's the situation, what's the pain,
what have you already tried?"
- Listen 80% of the time. Ask follow-up questions.
## 10-25 min: Demo / proposal walkthrough
- Targeted at their pain (not a generic tour)
- Show the solution to their specific problem
- Quantify the outcome ("this will save you X hours a week")
## 25-35 min: Q&A + objections
- "What's unclear? Any concerns?"
- Use your objection script
- Don't get defensive: dig deeper
## 35-42 min: Pricing + close attempt
- Show 2-3 tiers
- Recommend a specific one
- Closing technique (assumption / summary / alternative)
## 42-45 min: Next steps
- What we're signing, and when
- Who to send the contract to
- Follow-up: the Day 0 email (within 4 hours of the call)Step 3: Follow-up cadence template
A third document (or the file sales/followup-cadence.md):
# Follow-up Cadence (5 touchpoints in 30 days, then quarterly) ## Day 0 (within 4 hours after the call) Subject: [Company]: recap + next steps Hi [name], Thanks for your time today. To recap: - Your situation: [recap] - What we'll do: [recap] - Price: [recap] - Next step: [specifics] The contract is attached. I'm available to answer your team's questions [day/time]. [Your name] ## Day 3 Subject: [Company]: a quick question [Name], I've been thinking about our conversation. If you have questions about [specifics of their case], call me directly: [phone]. ## Day 7 Subject: An article you might find relevant [Name], I came across this article about [their industry]. It's relevant to what we discussed: [link]. By the way, how did the conversation with your team go? ## Day 14 Subject: Closing the loop [Name], this is my last follow-up about the contract. If this isn't the right time, just let me know; I'll close the file and stay in touch for when things change. If you have questions or your team would like another demo, give me a call. ## Day 30 Subject: Saw [trigger event] [Name], I saw that [company news]. That often leads to [our use case]. Would it make sense to pick our conversation back up? ## Day 90+ Quarterly value-add, not sales.
Step 4: Role-play objections with Claude
Use Claude as a sparring partner. Open a regular chat at claude.ai (or Claude Code, if you already use it) and paste the prompt below. In this example, you're pitching to a CTO (chief technology officer):
Role-play: you're the CTO of a 50-person startup evaluating our platform for AI workflows. The price is $5,000 a month. Your budget is tight this quarter. I'll start the sales call. After each of my turns, give me a realistic CTO objection, not an easy one.
Practice twice a week, 15 minutes each time. Write down the answers that didn't work and improve your script.
Variations to practice:
- "A CTO who has already invested in a competitor"
- "A founder who's skeptical about AI"
- "A VP of Engineering who has to discuss it with the team first"
- "A procurement officer who wants a 30% discount"
Step 5: Close-rate metrics
Track:
# sales/metrics.md ## Pipeline metrics (weekly review) | Stage | Count | Conversion rate | |---|---|---| | Discovery calls | N | - | | Demos delivered | N | X% (target 80%+) | | Proposals sent | N | X% (target 60%+) | | Closed won | N | X% (target 25%+) | | Closed lost | N | - | ## Diagnostics - Loss reasons (categorize): - Price: N% - Timing: N% - Wrong fit: N% - No decision: N% - Competitor: N% - Average sales cycle: N days - Average deal size: $N
What to do with the metrics (the thresholds below are the course's working guides, not market statistics; adjust them once you have 10-20 deals of your own):
- Demo → proposal under 60% → improve your demo (you're showing the wrong thing)
- Proposal → close under 25% → improve your closing (you're losing people who were ready)
- Sales cycle over 60 days → shorten it (or it's complex B2B, where that's normal)
- Loss reason "no decision" over 30% → you didn't reach the decision maker
Skill levels
Beginner
- ✅ 2-3 closing techniques mastered (assumption, summary)
- ✅ Responses to all 8 objections memorized
- ✅ Day 0 follow-up email template ready
- ✅ Able to run a 45-minute call using the structure
Intermediate
- ✅ Sales call structure adapted to your own product
- ✅ Full follow-up cadence (5 touchpoints) scheduled in your calendar or CRM
- ✅ All 8 objections handled without reading from the script
- ✅ Close rate above 25% from demo
Pro
- ✅ Custom proposals for large (enterprise) clients
- ✅ Multi-stakeholder selling (3+ decision makers)
- ✅ Negotiation skills (discounts only with a quid pro quo)
- ✅ Close rate above 40% from qualified prospects
- ✅ Average deal size growing quarter over quarter
Readiness checklist
Tools and resources
- "Never Split the Difference" by Chris Voss, a former FBI hostage negotiator. Tactical empathy, mirroring, calibrated questions. A negotiation classic.
- "SPIN Selling" by Neil Rackham. Situation / Problem / Implication / Need-payoff. A classic B2B sales method.
- The Sandler Selling System: a sales method that starts with the buyer's pain and only then gets to the product. Good for consultative selling.
- Y Combinator: startup sales: a collection of materials on first sales for startups.
- "The Mom Test" by Rob Fitzpatrick. How to ask questions that get you honest answers instead of polite lies.
- Apollo.io: a contact database with email sequences and calls: finding clients and first emails in one place
- Gong.io: records and analyzes your conversations with clients so you can review yourself (if your budget allows). Always tell people you're recording and get their OK; in some states, everyone on the call has to consent.
Key takeaways
Closing isn't about pushing something on a client. It's helping them make a decision they've almost made. If your product is the right fit and the price works, closing the deal is a helpful act, not an aggressive sale. If it's the wrong fit, better not to sell. The refund request comes in 30 days, the bad review in 90.
Every objection has a hidden meaning. More often than not, "too expensive" means "I don't see the value." Often, "I'll think about it" is a polite "no" with an unstated reason. Don't argue with the objection they voice; dig deeper and handle the real one.
The structure of a 45-minute call matters more than any technique. Listen 60%, talk 40%. The demo goes in the middle third (not the first!). The price comes after the value (never before). Every call ends with a clear ask, not "hopefully they'll sign." And follow up within 4 hours of the call, not the next day.
Related lessons
- Your first clients: already covered: how to find your first clients among people you know
- Pricing strategy for AI products: already covered: how to set a price so that closing is realistic
- Cold outreach with Claude: already covered: how to reach the prospects you'll later close
- Lead generation: an optional library lesson on building a contact list automatically
Next lesson
→ Delivery and retention: what to do after the signature so the client doesn't leave a month later
The mark stays in this browser only and is never sent anywhere. My progress