1 min lesson
Practice a product demo and objections
Talk this through in your own words. "Discovery showed that pull requests wait days for review. What should the demo show and the trial prove?" Finish with the next move.
Step 1 of 2
If the process includes a demo or objection exercise, keep the story tied to the discovery. A feature tour proves memory. A useful demo proves that you can choose the right workflow for the buyer's problem.
Use a short path from problem to capability to evidence. State the claim you can support and leave room for the buyer to test it during an evaluation.
- 1Open with the costly problem and the evidence gathered in discovery.
- 2Show one current Cursor workflow that addresses that problem, such as Agent changing several files or Tab completing a local edit.
- 3Return to the buyer's measure and explain what a trial would need to prove before either side claims success.
"Reviews on your team wait days before the first comment, and you measured the delay on the last pull request. Let me show one Agent change that applies a review comment across several files, so you can judge the reviewable result. If it holds up, we measure review wait time for one team over a fixed period and decide from that number."
Base urgency on the buyer's measured cost and decision timing. A broad claim that every company must adopt AI now is easy to say and impossible to defend in the room.