Run a discovery call that earns a useful next step
A discovery call should establish whether there is a problem worth solving together. A feature presentation delivered before understanding the customer's workflow often misses the buying reason.
Structure the conversation around change
Ask what prompted the enquiry, how the work happens now and what happens if nothing changes. Understand stakeholders and timing. Summarise what you heard and check accuracy before describing possible scope. Finish with a mutually understood next action rather than an ambiguous promise to stay in touch.
A worked example
A founder learns that a reporting request is driven by a new branch launch. That context changes the proposed sequence from a broad dashboard project to a focused launch-readiness diagnostic.
Illustrative scenario; this is not a claim about an actual Conxn client or guaranteed results.
Your action checklist
- Confirm the trigger
- Summarise the problem in the buyer's words
- Agree an owner and date for the next step
Should discovery always end with a proposal?
No. Another stakeholder conversation, a paid diagnostic or a respectful decline may be more appropriate when important facts remain unclear.
AI-assisted editorial guide for practical business planning. Adapt the framework to your context and seek qualified advice for material financial, legal, employment or contractual decisions.