Respond to the 'now isn't the right time' objection
intermediateClaude SonnetSalesAeobjection-handlingtimingaedeal-management
Use case
Use this prompt when a prospect says 'now isn't the right time,' 'we need to wait until next quarter,' or 'we're too busy right now.' Timing objections are often disguised priority or value objections — this prompt helps you diagnose and respond correctly.
The prompt
You are a senior sales coach helping an account executive respond to a timing objection without being pushy or losing the deal. Situation: - Prospect name:{{prospect_name}}- Company:{{company_name}}- Deal stage:{{deal_stage}}- What they said:{{objection_quote}}- What you know about their situation:{{situation_context}}- The urgency or business impact of the problem:{{business_impact}}- Any upcoming events or deadlines relevant to them:{{upcoming_events}}Generate: ## 1. Timing Objection Diagnosis Classify this objection into one of these types and explain why: - Type A: Real timing constraint (genuine external blocker — budget cycle, org change, project freeze) - Type B: Priority objection in disguise (they're not convinced it's important enough to act now) - Type C: Relationship/trust gap (they like the idea but aren't confident enough in you/your solution yet) - Type D: Polite no (they've decided not to buy but don't want conflict) ## 2. Immediate Response (what to say in the moment) A 2–4 sentence response that: - Acknowledges the timing concern without dismissing it - Asks one clarifying question to diagnose which type of objection this is - Doesn't pressure or create false urgency ## 3. Response by Objection Type Write a tailored follow-up approach for the two most likely objection types from your diagnosis. ## 4. The Cost of Waiting 2–3 talking points that make the cost of delay concrete — using the business impact and upcoming events — without being manipulative. ## 5. How to Keep the Deal Alive Without Forcing It Specific language and a proposed next step that maintains momentum without pressuring them to decide before they're ready.
Variables
{{{{prospect_name}}}}Replace with your {{prospect name}}{{{{company_name}}}}Replace with your {{company name}}{{{{deal_stage}}}}Replace with your {{deal stage}}{{{{objection_quote}}}}Replace with your {{objection quote}}{{{{situation_context}}}}Replace with your {{situation context}}{{{{business_impact}}}}Replace with your {{business impact}}{{{{upcoming_events}}}}Replace with your {{upcoming events}}
Example
Input
prospect_name: Greg prospect_title: Head of Sales Operations company_name: Pinnacle Distribution deal_stage: post-demo, proposal sent 1 week ago objection_quote: "Everything looks good, but Q3 is our busiest season and we can't take on a major implementation right now. Let's revisit after Labor Day." situation_context: Greg has been engaged throughout the process, asked detailed questions about implementation timeline, and looped in his IT lead business_impact: their current manual order routing costs approximately 12 hours per week in ops team time; they're also scaling into 3 new distribution centers this summer upcoming_events: they're opening two new distribution centers in July; they have a new ERP go-live planned for September
Output
## 1. Timing Objection Diagnosis This is most likely **Type A (real timing constraint) with elements of Type B**. Greg's engagement level (looping in IT, asking implementation questions) signals genuine interest — this isn't a polite no. The Q3 busy season concern is real for a distribution company. However, the September ERP go-live is actually a counter-argument to waiting: implementing after a major ERP change is harder, not easier. The real question is whether he's thought through the dependency. ## 2. Immediate Response "Greg, that's fair — I'd rather implement when you have bandwidth than rush something in. Help me understand the timing better: is the concern about your team's capacity to manage an implementation, or is it more about the Q3 volume making any distraction risky? Those point to different solutions." [Wait for his answer before moving to any reframe.] ## 3. Response by Objection Type **If Type A (real capacity constraint):** "Here's what I'd propose: we start the contract now but schedule implementation to begin in early October, after the season peaks. You lock in current pricing, we do the configuration work on our end, and your team doesn't touch anything until you're ready. Does that change the calculus?" **If Type B (priority disguised as timing):** "Let me ask it differently — if we were having this conversation in October, what would need to be true for you to move forward then? I want to make sure we're not pushing a timeline back just to face the same conversation in a few months." ## 4. Cost of Waiting - "You're opening two new distribution centers this summer. Every week the order routing is still manual, you're adding that overhead to a larger volume. The problem scales with your growth." - "The September ERP go-live is actually a reason to move before it, not after. Adding a process change on top of an ERP migration is twice as hard — we've seen that at other clients." - "The 12 hours a week your ops team is losing to manual routing: that's roughly 150 hours between now and Labor Day. At your team's loaded cost, that's real money sitting on the table." ## 5. Keeping the Deal Alive Don't push for a close date. Instead, propose a concrete "pre-implementation" next step: "What if we schedule a 30-minute call with your IT lead in the next two weeks — not to talk implementation, just to make sure there are no technical dependencies we'd need to plan around for an October start? That way we're not scrambling in September and you're not deciding under pressure." This keeps the deal warm, involves the right stakeholder, and gives you a natural check-in date without forcing a decision.
Tips for best results
- 1The single most important thing with timing objections is diagnosing correctly. Responding to a 'polite no' as if it's a genuine timing constraint wastes months of follow-up effort.
- 2Never manufacture urgency. Fake scarcity ('our pricing changes next week') destroys trust and rarely works with sophisticated buyers.
- 3The 'start now, implement later' structure is one of the most effective responses to genuine capacity constraints — it lets them commit in principle without feeling overwhelmed.
- 4After running this prompt, ask Claude: 'What are 3 follow-up questions I can ask over the next 4 weeks to keep this deal warm without being annoying?' for a nurture plan.
- 5If the deal keeps getting pushed, that's diagnostic information. Ask Claude to help you evaluate whether this is a real opportunity worth pursuing.
Related prompts
Respond to the 'your price is too high' objection
intermediateGenerate a confident, non-defensive response to price objections that reframes value and advances the deal.
Salesobjection-handlingpricenegotiation
Write a deal-close email before quarter end
intermediateGenerate a professional, non-desperate close email that creates genuine urgency and makes signing easy.
Salesclosequarter-endae
Write a 3-email follow-up sequence after no reply
beginnerGenerate a 3-touch follow-up sequence for cold outreach that went unanswered, each with a distinct angle to earn a response.
Salesoutboundemailfollow-up
Need help implementing this prompt in your workflow?
Book a call