How to handle: "We have a procurement process that takes 3-4 months."
Map out procurement timeline and steps, then ask about expedited process if needed so the conversation moves from "we have a procurement process that" to the business outcome they actually care about.
Score your response
What this objection really means
You're talking to a coach, not the economic buyer. Until the real decision-maker is in the room, the deal won't move. For "we have a procurement process that" specifically, the underlying job is to map out procurement timeline and steps before you say anything else — that one move usually reveals whether this is a genuine blocker or a reflex response.
The framework
Map the buying committee → Equip your champion → Earn a multi-threaded conversation → Pre-handle the EB's questions.
Three sample responses
"That's a fair point, and I hear it a lot. Before I respond, can I ask — when you say "we have a procurement process that", what's the specific concern behind it? I want to make sure I address the real thing, not the version I assume you mean."
"Totally understand. Most of our customers raised exactly that before they saw the numbers. The way we'd normally approach it is to ask about expedited process if needed — and then identify key stakeholders at each stage. Would it be useful if we walked that through against your own situation?"
"Let's park the approval question for a second. If nothing changes in the next 12 months, what does that cost you — in revenue, time, or risk? Because you're talking to a coach, not the economic buyer. until the real decision-maker is in the room, the deal won't move."
What a strong response covers
- Map out procurement timeline and steps
- Ask about expedited process if needed
- Identify key stakeholders at each stage
- Discuss how to navigate process efficiently
Common mistakes
- Skipping the "map out procurement timeline and steps" step — reps who jump straight to a rebuttal here lose the prospect's trust before the real response even lands.
- Letting a coach pitch internally for you with materials they don't fully understand.
- Treating 'I need to talk to my boss' as a step instead of a signal to multi-thread.
- Talking before fully understanding what the objection actually means to them.
- Defending instead of diagnosing — turning a question into a debate.
Want to rehearse this one out loud? Run a roleplay where the AI buyer will say "we have a procurement process that" verbatim and score your verbal response.
Handling "We have a procurement process that" by role
The right response changes depending on who is answering. Pick the role-specific playbook below:
- For SDRs — the first 30 seconds — cold outreach, opener replies, and booking the discovery meeting.
- For BDRs — outbound pipeline into named enterprise accounts — multi-threaded outreach across a defined territory.
- For AEs — the full sales cycle from discovery to close — the person with the number on their back.
- For sales managers — coaching reps and forecasting the team's number — objections show up in deal reviews, not on the phone.
- For CSMs — retention, expansion, and renewal — objections here threaten revenue you have already earned.
- For account managers — expansion within existing accounts — new logos in the enterprise are yours, but so is protecting the base.
- For sales engineers — technical validation — demos, proofs of concept, and answering the objections the AE cannot.
- For founders — the first N deals — you are the product, the pitch, and the objection handler until you can hire an AE.
Every objection on this site is one the LemCoach AI buyer actually uses inside our practice scenarios. The rubric on the right is the same one we use to score live roleplays — so the advice here matches the coaching you'd get from the product.
Frequently Asked Questions
Hear "We have a procurement process that" out loud — then answer it
The AI buyer says this objection verbatim and scores your spoken reply. 37 more objections waiting after this one.
No credit card required · 7-day free trial · Cancel anytime