Sales Discovery and Objection Handling

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Use When

• The brief is incomplete and proposal assumptions must be clarified through discovery questions.
• The evaluator may resist price, timeline, staffing, technology, AI, risk, maintenance, or local-context assumptions.
• The proposal needs a stronger buyer conversation before submission, negotiation, presentation, or BAFO.
• The offer is premium-priced and must defend value without pressure tactics.

Workflow

1. Identify the decision path: sponsor, technical evaluator, procurement, finance, legal, users, and approvers.
2. Convert vague requirements into discovery questions about outcomes, current pain, decision criteria, constraints, budget logic, and success measures.
3. Qualify urgency and value: what happens if the client delays, under-scopes, or chooses the cheapest compliant option.
4. Map likely objections before drafting: price, risk, timeline, staffing, technology, data, maintenance, local delivery, or procurement compliance.
5. Answer objections ethically: acknowledge the concern, clarify the basis, reframe around value or risk, provide evidence, and define the practical trade-off.
6. Add follow-up language that makes the next step easy: clarification request, option comparison, presentation agenda, revised scope, or decision memo.