Implementation concern
Customer says: “We are interested, but implementation could take several months.”
Say This Next: “Ask which internal dependency is most likely to delay implementation.”
Backup Question: “Who would need to be involved before implementation can begin?”
Why This Matters: “Identifies the real blocker without debating the timeline.”
Source: Implementation Playbook
Pricing objection
Customer says: “This looks useful, but the price is higher than we expected.”
Say This Next: “Ask what outcome they expected the investment to create before discussing the number.”
Backup Question: “Which part of the expected return feels least certain right now?”
Why This Matters: “Moves the discussion from price alone to value and risk.”
Source: Pricing Objection Playbook
Existing vendor
Customer says: “We already use another provider and do not want to replace everything.”
Say This Next: “Ask what they would improve about the current setup if switching were not required.”
Backup Question: “Where does the current process still create friction for the team?”
Why This Matters: “Surfaces unmet needs without forcing a replacement conversation.”
Source: Competitive Positioning Playbook
Budget timing
Customer says: “The budget may not be available until next quarter.”
Say This Next: “Clarify whether the constraint is timing, approval, or confidence in the business case.”
Backup Question: “What would need to be true for this to become a priority sooner?”
Why This Matters: “Separates a real budget constraint from unresolved buying risk.”
Source: Budget Timing Playbook