Notes for owners · Sales management
Why technology leads go cold between demo and proposal
A buyer who liked your demo and then went quiet usually has no next step that belongs to anyone. Here is how to close a demo with an owner and a date, and what to do when it goes silent.
The GullySales team · Updated 17 Oct 2026 · 6 min read
On this page
- What actually happens in the silence?
- How do you end a demo so the next step has an owner?
- What should the written note after the demo say?
- Which leads are really cold, and which are waiting?
- For example: a fleet-tracking vendor and a Nashik bus operator
- What belongs in a proposal that follows a demo?
- Keeping the pipeline honest
- Before your next demo
Technology leads go cold after a demo because the meeting ends with a feeling and no task. The buyer liked it and said they would discuss it internally. Nobody wrote down who does what, or by which day. Close every demo by agreeing one next step, its owner and its date, in writing, before the call ends. Then follow up on that step, not on the demo.
What actually happens in the silence?
The buyer's day goes on. The person who watched your demo has to explain it to a finance head, a boss or an IT team who did not. They try, and they cannot answer the questions that come back. Price, who will maintain it, what happens to existing data, whether the Tally entries will match. It can feel easier to wait than to ask you.
Meanwhile you wait for them. Each side thinks the other will move, and nobody does. Four weeks later your "any update?" lands in a different week of the buyer's life. No answer.
Silence is not always a no. In the example below it was a task nobody picked up.
How do you end a demo so the next step has an owner?
Reserve the last five minutes of every demo for this. Say so at the start: "I'll keep five minutes at the end to agree what happens next." Then use this script.
- Recap what they asked for. "You said the main problem is purchase approvals taking four days. This is the part that covers it."
- Ask what stands between them and a decision. "Who else needs to see this, and what will they ask?"
- Offer one specific next step. A costed proposal, a session with their IT person, a trial on their own data.
- Fix the owner and the date. "I'll send the proposal by [day]. Can you send me the number of users and the list of reports by [earlier day]?"
- Confirm in writing the same day. Three lines by email or WhatsApp.
The point is that the buyer now owns something small. A person with a task has a reason to reply, which a vague impression does not give.
What should the written note after the demo say?
Keep it short enough to read on a phone. A working template:
Thanks for your time today. Here is what we agreed.
You need: [the problem in their words]
We will: [your action] by [date]
You will: [their action] by [date]
Next meeting: [date and time, or "to be fixed after the above"]
People who will see it: [names and roles]
If anything here is wrong, tell me and I will correct it.
The last line matters. It gives the buyer an easy way to reply, and a correction is better than silence.
Which leads are really cold, and which are waiting?
Do not treat every quiet lead the same way. Sort them before you write anything.
| Signal | Likely meaning | What to do |
|---|---|---|
| Buyer owes you a document or a number | Waiting on a task | One reminder with the exact item and a way to make it easier |
| Buyer named a meeting or an approval date that has not passed | Waiting for the process | Wait until the date, then ask how it went |
| Buyer named no next step and no one else involved | Interest, no owner | Ask who else needs to see it; offer a one-page summary for them |
| Buyer's date has passed and your last two messages are unread | Cold | One closing note, then move on |
| Buyer asked a question you have not answered | Your move | Answer today |
Check your own sent folder before you blame the buyer; the last row is easy to miss.
For example: a fleet-tracking vendor and a Nashik bus operator
Imagine an invented software firm in Pune that sells vehicle tracking. It demonstrates the product to the owner of a Nashik bus operator with about sixty vehicles. The owner is enthusiastic. The vendor leaves with "I'll send a proposal" and does so three days later, with a price and a feature list. A month passes without a reply.
Looking back, three things were missing. The owner never said who would watch the screens, the depot supervisor had not seen the demo, and the proposal never touched the real worry: drivers switching the device off. The vendor handles the next demo differently. It asks who runs the depot, then writes: "I will bring a one-page note on tamper alerts and a sample report from a dummy route. Please send me the vehicle count by depot." The proposal that follows opens with the tamper question, and the supervisor joins the next call because the owner asked. The supervisor will not commit to sixty vehicles, only to a trial on five, and the month ends with no signed order. Not every lead warms up like this, but the vendor now knows where it stands.
What belongs in a proposal that follows a demo?
A proposal should answer questions the buyer has already asked. One that has to introduce a new idea has skipped a step that belonged in the demo. Include the problem in their words and the people who will use it. Add what is in and out of scope, the price with what drives it, and the first step if they say yes. What to do when a proposal goes unanswered is in why customers stop responding after a proposal.
If the buyer will not tell you the budget, offer two options at different scopes rather than one. That gives them something to compare.
Keeping the pipeline honest
Add one column to your lead sheet or CRM: "next step, owner, date". If a lead has no entry in it, it is not in the pipeline; it is a hope. Review the column before you review the names. Keeping that column honest is the core of pipeline management.
Before your next demo
Tell the buyer at the start that the last five minutes are for agreeing a next step, and write the note the same day. Other work for software and IT firms is under technology sales and marketing. If you would like help shaping your demo close and your follow-up, tell us what you need.
