Asking for the Sale After a Demo

I used to think the hard part of a software demo was the middle—the clicks, the questions, the screen share gremlins.

Turns out the hard part is the end. And whatever you pretend happens after the end.

You know the feeling. The call goes well. People lean in. Someone says “this is interesting.” You hang up feeling like you hosted a successful family dinner: everyone was polite, nobody started an argument, and you still have no idea if anyone actually liked the food.

The room is warm. The deal is cold. Everyone was polite. Nobody committed to anything.

This article is about asking for the sale after a demo—which, in presales, usually means asking for the next committed step before everyone logs off and your proposal dies in someone’s “later” folder.

Most ghosting starts before the follow-up email. It starts when the demo ends with politeness instead of a plan.

Asking for the sale after a demo is not one aggressive line—it is booking the next meeting, naming owners, and giving champions something they can forward without rewriting your pitch.

---

The demo I thought was a 9/10 (and the silence that followed)

Years ago I supported an AE on an enterprise analytics deal. Sharp buyers. Good questions. I left thinking we had just filmed the highlight reel.

My AE sent the deck that night. Then the proposal. Then the friendly bumps.

Nothing.

Not a hard no. Worse—a maybe dressed up as enthusiasm. The kind of maybe where your champion still likes you on LinkedIn but will not reply to email for three weeks, like a relative who said “we should get together soon” in 2019.

I replayed the recording. We had done what I now call a product training demo: lots of screens, lots of “does that make sense?”, lots of backend setup nobody asked to see. The buyer nodded the way my uncle nods when my aunt explains the seating chart—supportive, committed to nothing.

The demo was not bad. It was mislabeled. We performed interest. We did not earn a next step.

That was my expensive lesson: if you are not sure what happens next when you are still on the call, email will not save you.

---

Forty-seven “great” demos and zero sales (the problem you might be solving wrong)

A founder friend ran 47 demos in a few months. Same movie every time: sharp questions, boss joins, “this would save us so much time,” then nothing. No rejection email. Just fog.

He was ready to fix follow-up, pricing, onboarding, the logo, the universe.

Then someone outside the business asked a better question: “What do they say when they turn you down?”

Answer: “They don’t. They disappear.”

So maybe they were not rejecting the product. Maybe they were rejecting change.

We went through his notes together. Painful anthropology.

One procurement lead spent seven hours sourcing a single SKU—copying from a marketplace into Excel, messaging fifteen suppliers by hand, comparing quotes like it was 2009. Twice a month. Every month. Forever.

He showed her the same work in under an hour. She agreed on the math. Asked about price. Asked about implementation.

Vanished.

Another kept supplier contacts in a paper notebook. “I know where everything is.”

Another had a color-coded Excel she built over four months. She was proud of it. Automated quote comparison felt like insulting her hobby.

I stopped thinking his competitor was the other SaaS tool. His competitor was muscle memory and good enough.

Another founder I know sells project management software. Biggest rival? Spreadsheets and Slack threads. Not the logos on the analyst report.

In B2B you are often not selling features. You are selling willingness to change. The deals that actually close tend to be greenfield teams with no sacred spreadsheet yet—or a process so broken they have no choice.

That reframes asking for the sale after a demo:

1. You may be demoing the wrong person.
If your tool automates the room, do not expect the room to sponsor its own replacement. Directors care about throughput and cost; operators care about surviving Tuesday. I push multi-threading and executive pain, not only the person who enjoyed the clicks.

2. “Interested” is not pain.
Twelve hours saved per month can be a vitamin—nice, easy to ignore. Tie to money, risk, or something their boss already cares about. Hours are emotional; dollars and deadlines are political.

3. Efficiency can threaten identity.
One early customer told him: if sourcing takes an hour instead of a week, what does the buyer tell their boss they do all day? I am not saying everyone sandbags on purpose. I am saying adoption is optics, not algebra.

4. A great demo can still offend.
If you parade how fast you are compared to their notebook, their Excel baby, their career story—you are not building curiosity. You are winning an argument they never entered. That is not dinner conversation; that is you explaining why their meatloaf recipe is illegal.

5. After the demo, ask for change—not gratitude.
I like: “If we moved forward, who besides you would feel this in their week—and who might resist?” That surfaces the real deal earlier than another “just checking in.”

When I hear “demos went great, zero sales,” I now ask two questions before I touch the email template: Who were we really competing against? And did we earn a next step, or did we earn applause?

More on reading the room before you close: understanding intent in presales demos.

---

What “asking for the sale” actually means (especially if you are presales)

The phrase sounds like a movie line. Handshake. Music swell. Contract appears.

Early in my career I watched reps split into two camps. Camp A ended with “thanks for your time”—polite, safe, zero points on the board. Camp B actually asked—and sounded like the bad guy in a movie until they learned tone.

I landed in Camp A because I did not want to be pushy. Then a senior AE told me something stupid-simple: you rarely get what you do not ask for. Not a signature every time. A truth. A next step. A no. Anything beats fog.

In real presales demos, I rarely ask “ready to sign?” I ask for:

• a debrief with the people who matter
• a technical validation call with security in the room
• a mutual action plan with dates and owners
• a commercial conversation that is already on the calendar

In enterprise SaaS, “yes” rarely means “sign today.” It means yes, this is worth more of our time through a real process. If you treat politeness as purchase intent, your forecast will look like my grandmother’s guest list: long, hopeful, and mostly fictional.

Set the close before the demo starts

The worst surprise is a closing question they never saw coming—like someone announcing they have already picked the wedding venue for a couple who met Tuesday.

I set an agenda in the first few minutes: what we will show, what we will skip, and what a good end looks like. “If this covers what you need, we will align on next steps before we hang up.” Not sneaky. Not a trap. Just so nobody is blindsided when I stop sharing screen.

That is assuming the sale in the grown-up sense: talk as if we are already solving the problem together—implementation timing, who else cares, what “good” looks like—without cosplaying that legal has signed.

If BANT was fiction and discovery was thin, no magic sentence at minute fifty-nine saves you. The ask only works if the demo earned it.

The line I use when the room is warm

After we show what they came to see—tied to the objections that brought them here—I say:

“If we have covered what you needed to see today, is there anything else that would prevent us from moving forward together?”

Not “any questions?” Not “thoughts?” A barrier hunt. Price, timing, security, internal politics, competitor—they name it, or you learn the deal is softer than the smiles suggested.

In transactional cycles, some reps ask for business throughout the pitch. In enterprise I ask for commitment to the process throughout—then a clear ask at the end. Same muscle, different weight class.

Shooters shoot (and thank-yous walk off the court)

When the demo is working, questions fly. Objections show up. That is the crowd yelling shoot. Thanking them for their time and dribbling a proposal into email two weeks later is picking up the ball, placing it gently on the floor, and leaving to help your wife with something she will redo anyway.

I still get awkward. Asking is the hardest part of the job for me. I do it anyway. The ask is not the whole close—it is refusing to pretend the conversation did not have stakes.

If you only need the mechanics of the last few minutes on the call, read how to end a demo without losing momentum. This piece is what I do after that—diagnosis, talk tracks, and how I stopped sending proposals into a black hole.

---

Diagnose where you lost them (before you “fix” follow-up)

When a team asks me why buyers ghost after a demo, I ask three questions. Boring questions. Useful questions.

1. Could your champion explain the value in one sentence—to their boss, without you in the room?
If not, you gave them a tour, not a story. Fix the demo before you fix the sequence.

2. Did you leave with a dated next step—who, what meeting, what decision?
If you left with “I’ll send the deck,” you left with homework for them and hope for you. That is a process gap.

3. Did you surface what kills deals in their world—security, legal, budget, competing vendor—while they were still talking to you?
If not, you will meet those people later as silence. That is a risk gap.

Most demo mistakes are predictable. Run the checklist before your next customer call.

Generate my checklist

Better follow-up does not fix a demo that never earned momentum. If the live call was messy, start with common demo mistakes that kill trust.

---

Pleasantness is not demand

During the demo you talk to a human.

After the demo, the decision often moves to people who were not on the call—security, legal, procurement—and nobody wants to be the employee who said “trust me” with only a generic deck as evidence.

I learned to treat outcomes like family dinner again:

• Yes is “we’re doing this—here’s who moves it forward.”
• No is “not now / not us”—annoying, respectful, clear.
• Maybe is “everyone smiled and nobody committed to dishes.”

Maybe is where pipelines go to nap.

Discovery should name cost of inaction before you share screen. The demo should connect to that pain. The close should confirm this problem is still worth more meetings—not just worth a nice email from you.

Do not confuse “they were kind” with “they will fight for budget.” Kind is free. Budget is politics.

---

Nobody owes you a purchase because the demo was good

I learned this one outside work, in a home theater store—the kind with a dark demo room where they let you sit for twenty minutes and pretend you are in a movie, not in a strip mall next to a mattress outlet.

I wanted to hear speakers before spending real money. The online price was cheaper. I felt guilty, like I was using the salesperson as a free Spotify playlist with furniture.

So I did what adults do when they are awkward: I over-researched online, then walked in and acted casual. The rep was great. He was not offended that I mentioned another price. He said, “Show me the listing—if it’s legit, we usually match.” We talked about the room, the amp, the weird corner where bass dies. I left with clarity, not obligation.

That afternoon fixed something in my head for B2B demos too.

Your buyer is not rude for comparing options. They are rude if they never had any intent to buy and treated your hour like a free consulting session—but comparing you to a competitor, internal build, or “do nothing” is normal. Same as comparing the strip-mall demo to the website with no sales tax.

What I took from that day:

1. The demo is a service, not a contract.
They owe you honesty and time-boxed attention—not a signature. If your demo only “worked” because you assumed gratitude, you built a birthday party where everyone showed up, ate cake, and went home without planning your gift.

2. Be upfront early so nobody wastes the rep’s time.
On enterprise calls I say out loud what we are doing today and what a good outcome looks like: “If this fits, here’s how teams usually move forward. If it doesn’t, I’d rather know on this call than send you a proposal you’ll ignore.” Wishy-washy “we’ll see” from either side is how you get the Magnolia rep’s nightmare customer—the one who demos everything, commits to nothing, and acts like they invented speakers.

3. Give them a real chance to win before you declare ghosting.
At the store, that was price match. In SaaS, it is commercial flexibility, phased rollout, proof tied to their metric, or a path that beats “build it ourselves.” Ask for the sale can sound like pressure; ask how we earn the business sounds like partnership. I often say: “If we are not the right fit, tell me. If we are, what would you need from us to make this an easy internal yes?”

4. If they only wanted the demo room and never intended to buy, that is on discovery.
Going in knowing you will only purchase if the price “plummets an unreasonable amount” is the consumer version of a prospect who wanted a free POC architecture review. I qualify harder now—not to be cynical, but because my team’s demo room closes too if every call is tourism.

5. Some buyers will pay a small premium for the full experience.
Not always. But when support, time-to-value, and risk reduction matter, “10% cheaper elsewhere” is not the whole math. Your job on the close is to make why you obvious—not to guilt them for shopping.

When I feel bitter after a “great demo,” I ask: did I give them a fair chance to buy from us on the call? Or did I drop a proposal over the fence and sulk like I was entitled to loyalty because the playlist sounded good?

---

Why “I’ll send the deck” is the ghost-invite sentence

It feels adult. Low pressure. Professional.

It also creates a vacuum.

No calendar hold. No shared deadline. No story your champion can tell upstairs except “we saw a demo.” Your proposal becomes something they can open in March without consequence.

In enterprise, interest without a defensible artifact dies quietly. Notes are not enough. They need something they can forward without rewriting your pitch.

What I do instead:

• Book the next meeting before I hang up—debrief, pricing review, or proposal walkthrough.
• Do not send a proposal blind—if they need the doc, we schedule when we walk through it together.
• Write a simple mutual action plan live—timeline, decision criteria, security path, who signs.
• Arm the champion within 24 hours—short exec summary (problem, impact, ROI), recap tied to their workflow, security/procurement answers they will actually get asked.

That is asking for the sale without performing the movie scene.

---

The last five minutes I wish I had learned earlier

When five minutes are left, I stop clicking.

I am not “just showing one more thing.” I am finding out if we are both still in the conversation.

1. Acknowledge time
“We have a few minutes left—I want to use them well.”

2. Name mutual investment
“Getting this right usually means more of your team’s time—another session, a POC, security review. I want to respect that upfront.”

3. Pressure-test—calm, not dramatic
“Based on what you saw today, is it worth continuing to invest time together?”

Or, if you already showed what they asked for: “Is there anything else that would prevent us from moving forward?” Listen. Do not rush to fill the silence. That pause is where deals tell the truth.

4. If yes: WHO / WHAT / WHEN
Who pulls in finance? Who owns security? What happens this week? If they say yes but nobody owns anything, I treat the deal as at risk and I am relieved I learned that on the call, not in month three.

5. Book the next conversation
Technical deep-dive. Stakeholder call. MAP working session. Not “I’ll circle back.”

There is no magical gap between demo and close. There is only the next conversation. Topic depends on stage—but there must be a topic with a date.

For the full call spine, I still use demo structure. When the room wobbles mid-demo, next best move thinking beats panic.

---

The full close (what I say as presales vs what the AE owns)

“Thanks for your time” is manners. It is not a close. I say thanks after the ask—not instead of it.

Recap in outcomes, not menus. One sentence: the pain we opened with, what changed in the room.

Check fit. “Does this match what you needed to see today?” Silence is data.

Barrier hunt. “If we covered what you needed to see, is there anything else that would prevent us from moving forward?” Not “any questions?”—objections, not politeness.

Ask how they buy. “You know your process better than I do—once you have the summary, what usually happens next?” I mirror legal, procurement, security. I make our side sound boring in a good way: parallel security pack, short contract, clear kickoff.

Work backward from go-live. Training, IT, legal. “How realistic is that if we start this week?”

Map the deal. “Who approves budget, what’s the timeline, what can kill this?” I push multi-threading early because I have been burned by one friendly champion too many times.

Then—and only then—send materials. Email supports the plan. It does not replace the plan.

As presales, my “ask” is often: security review scheduled, success criteria for a timeboxed POC, champion armed for the internal meeting.

As AE, it is commercial call booked, proposal walkthrough on calendar, signature path named.

SEs who vanish after “great demo” are why AEs get ghosted later. I try not to be the person who waves from the departing train.

On the call—not in email three— I want the alternatives conversation: “You’re looking at other options—how do we stack up so far? Anything that would keep you from recommending us internally?” If that dialogue never happened live, your follow-up video is just you narrating a mystery you chose not to solve. My mother could leave six voicemails asking if we were “still mad.” I still would not know why. Same energy.

Proposal hygiene I learned the hard way: verbalize range before the doc lands. Walk pricing on a call—do not DocuSign into the void. Unexplained line items become silent nos. Book the expiration conversation when you send the quote: “If we have not aligned by [date], let’s reconnect that day and decide together.”

Below the power line? Ask permission: “Would it help if we presented this with you to [economic buyer] so we can answer their questions in context?” An introduction beats you cold-emailing three “decision makers” you have never heard speak.

---

Good demo, quote out, three polite emails (you are not as far along as you think)

I mentored a founder who did everything reactive right after a strong demo: $30k quote for a 330-person engineering org, three follow-ups, even a personalized video explaining why they should pick him.

Silence.

He was not getting rejected. He was getting stall—the professional version of “we’ll call you.”

What he had missed was on the demo and before the ink dried:

• The economic buyer was not in the room. A manager was on leave. His contact could not champion budget he did not hold.
• He never asked, live, what happens after today—who sees the quote, in what order, what procurement needs, when they decide.
• “We’re looking at alternatives” came after the demo, over email—so he never asked on the call: Are we your lead horse? What would make you comfortable recommending us upstairs?
• He treated demo + quote like a vending machine. Insert webinar, receive PO. Enterprise does not work like a family snack tray—everyone wants something, nobody wants to be the one who picked the wrong chip.

He was below the power line—friendly with the people who could say “interesting,” not accountable for “approved.”

What turned his head (before he finally picked up the phone):

A real champion does more than take meetings. They bring others in. They talk in company outcomes, not “QA would be smoother for me.” If your contact only speaks in personal convenience, you have a guide, not a champion.

Buyers do not buy for a living. You might demo for a living. Your job after the demo is to guide the process they do twice a year—evaluation criteria, timeline, who signs, what “do nothing” looks like. That is asking for the sale without begging.

When you have a proposal out, calling is not “cold.” It is the deal. I like: “I have limited implementation bandwidth next quarter—where should I prioritize you, and can you give me a decision date so I plan honestly?” Scarcity without melodrama. You are allowed to be the prize—not the pen pal.

If they stay vague: “What would need to be true for us to close this—or should I close the file?” Direct questions hurt for thirty seconds. Fog hurts for a quarter.

He called. He was not desperate. He was caught up.

---

After I hang up: warmth without the pathetic bump

I do not ask busy people to do work for free.

Same day: recap email—outcomes, open items, owners, and the invite we already agreed to.

Within 24 hours on enterprise deals: a champion kit. Not a 40-slide monument. A tight summary they can forward, their numbers in plain ROI language, answers to the security questions that always show up late.

If they stall: I point back to what they said—their date, their pain, their event:

“When we spoke you wanted to be live by [date] because [reason]. To hit that, we need [step] by [date]. Is this still a priority?”

Sometimes I send a simple status ask—reply 1 / 2 / 3—so I get signal instead of guessing. Not clever. Just respectful of their time.

Follow-up with substance, not “checking in.” Industry benchmark, implementation checklist, answer to the objection they almost raised—anything but the empty bump. If I have nothing to add, I call instead of emailing courage into the void.

After two real value drops with no movement: I write a clean breakup—or ask if I should close the file. No is better than fog. Fog eats quarters.

Enterprise cycles are long. Momentum is still optional—and on you.

If the call broke live—wrong screen, tough question—I still own recovery. See how to recover from demo mistakes.

---

What I tell myself now

Asking for the sale after a demo is not a closing trick.

It is refusing to end in polite fog.

It is refusing to leave your champion alone in the building with nothing to forward except “we liked them.”

Diagnose demo vs deal. Pressure-test the last five minutes. Book the next conversation. Arm internal sellers. Then send docs.

If you want a prep habit so the close is not an afterthought, I use our Demo Checklist Generator—before the call, not after the ghost.