Topic 7 — Demos, objections, and closing

Goal: Present a compelling solution, handle objections, and close the deal.

Lesson 7.1 — The demo is an answer, not a tour

Dario Vance has booked a second meeting with Marcus Thorne, the operations director at a regional carrier, and his sales engineer Priscilla Aoki opens the laptop to start the demo. Before she clicks anything, Dario does something that looks almost lazy: he recaps. "Last time you told me your drivers burn an extra ninety minutes a day on routes that double back, and your fuel spend jumped eleven percent last quarter. Today we're going to show you exactly those two things." Marcus nods. He's already leaning in, and nothing has been demoed yet.

That recap is the whole trick. A tailored demo shows the few things that solve the specific problems the customer named in discovery — not a parade of every feature the product has. Dario isn't going to open the reporting module or the billing integration, however proud the engineering team is of them. Marcus didn't ask about those. He asked about backtracking routes and fuel.

The weak version of this meeting is a feature tour: forty-five minutes of "and over here you can also..." while Marcus checks his phone. The strong version connects every screen to something Marcus said out loud the week before.

A demo isn't "here's what our product does." It's "here's how our product solves your problem" — and you can only do the second if discovery (Topic 6) gave you the problem to aim at.

Dario didn't write a generic demo script. He built this one out of Marcus's own words.

Lesson 7.2 — Outcomes, not buttons

Watch the difference between two ways of saying the same true thing.

Priscilla could say: "This is the route optimization engine. It uses a constraint solver, you set your parameters here, and it recalculates in real time." All accurate. All forgettable.

Instead she says: "Remember that ninety extra minutes a day? Watch." She pulls up one of Marcus's actual lanes, runs it, and the redrawn route lands on screen. "That's about forty minutes saved on this run. Across your fleet, that's the eleven percent you mentioned — most of it back."

Same feature. The second version is outcome storytelling: you lead with the result the customer gets, set in their world, and let the feature be the thing that delivers it. Buttons are boring. A fuel line going down is not boring to the person who owns that fuel line.

Three habits make this land:

• Tie every screen to a need they named. "You mentioned X — here's exactly how we fix that." If you can't connect a screen to something they said, cut the screen.
• Lead with the benefit, then show the mechanism. Result first, plumbing second, and only as much plumbing as they want.
• Use their data, their words, their lanes. A demo on the customer's real routes beats a demo on "Acme Corp" sample data every time.

The feeling you're going for is Marcus thinking this was built for us. That feeling is worth more than any feature you could have shown him.

Lesson 7.3 — Make it a conversation

A demo where you talk for forty minutes straight is a presentation, and presentations don't close deals.

Renske Bauer, the account executive who runs these meetings with Dario, has one rule she repeats to every new rep: stop and ask. After Priscilla shows the route savings, Renske turns to Marcus. "Does that match how your dispatchers actually plan a day, or am I oversimplifying it?" She's confirming it resonates — and inviting the objection now, in the room, instead of in an email after the meeting where she can't respond.

Marcus says, "It's close, but my dispatchers won't touch a tool that takes them out of their current system." Gold. A real concern, surfaced because Renske asked. An interactive demo keeps pulling these out:

• Ask "is this the kind of thing you were hoping to see?" after each major piece.
• Watch their face. Confusion or a flat reaction means slow down, not push on.
• Let them drive a little — hand over a question, ask what they'd want to try.

A monologue assumes you already know what matters to them. A conversation lets them keep telling you, so every objection becomes something you can address while you're still in the room.

Lesson 7.4 — Objections are a good sign

Marcus's line about his dispatchers is an objection — a concern or hesitation that stands between him and yes. The four classics are "it's too expensive," "we already use something else," "I'm not sure it'll work for us," and "the timing's not right."

Here's what new reps get backwards: objections are good news. Owen Driscoll, who runs Dario's SDR team, tells him this on his first week. "The prospect who objects is engaged. The prospect who says 'looks great, send me some info' and then ghosts you — that's the one you've lost. Silence is the bad sign, not pushback." A person poking holes in your product is a person imagining using it.

So you welcome the objection instead of flinching. The method Dario's team uses has a name in the industry — LAARC: Listen, Acknowledge, Assess, Respond, Confirm.

1. Listen — fully, without interrupting or getting defensive. Let them finish the whole thought.
2. Acknowledge — "that's a fair concern" before you respond to it. Validating shows you heard them, which is different from agreeing with them. Arguing immediately pushes them away.
3. Assess — dig into the real issue. Ask a question. "When you say your dispatchers won't switch — is it the retraining, or is it that this would be a third screen open all day?"
4. Respond — answer the true concern with evidence: reframe value, show a relevant example, or clear up a misunderstanding.
5. Confirm — check that it actually landed before you move on. "Does that put the dispatcher worry to rest, or is there more there?"

That last step is the one people skip, and it's why the framework adds it: without confirming, you've assumed you resolved the objection and you're walking into a close on a concern that's still alive.

Lesson 7.5 — "Too expensive" rarely means too expensive

Three weeks later Marcus says the sentence every rep hears: "It's just too expensive."

A panicked rep hears lower the price. A trained rep hears something else. "It's too expensive" almost always means "I don't yet see the value" — a value or trust gap, not a literal number problem. Marcus isn't comparing your price to zero. He's comparing it to a benefit he can't size yet.

So Dario doesn't discount. He assesses. "Help me understand — too expensive compared to what?" Marcus admits he's not sure the fuel savings are real. There it is. The objection was never about the price tag; it was about whether the eleven percent shows up. Dario reframes around value: he walks the math back through Marcus's own numbers — the ninety minutes, the fuel line — and shows the savings dwarf the subscription in the first quarter.

This is also why strong discovery and a tailored demo prevent objections before they happen. Half the price objections a rep hears are really demo failures — the value never got made concrete, so the price has nothing to sit against.

When someone says "too expensive," they're telling you the value still looks fuzzy, not that your price is wrong. Fix the value, and the price usually fixes itself.

Discounting on reflex teaches the customer that your price was made up, and it leaves real money on the table. Reframing value teaches them what they're actually buying.

Lesson 7.6 — Ask for the business

Dario's first month, he ran a flawless meeting — great demo, every objection handled, Marcus practically sold — and then he scheduled a follow-up call and hung up. Owen watched the recording and asked one question: "Why didn't you ask him to buy?"

Closing is simply guiding the customer to a final yes, and the most common closing mistake is the simplest: not actually asking. People run a perfect process and then get shy at the finish, softening "are you ready to move forward?" into "let me send you some more information." If discovery, the demo, and the objections all went well, the close isn't a high-pressure trick. It's the natural next step, and the customer is often waiting for you to propose it.

So you ask, plainly. "Shall we get started?" "Are you ready to move forward?" Then you make yes easy:

• Spell out clear next steps — who signs what, when onboarding starts, how the first week goes.
• Keep the paperwork simple. Friction at the finish line kills deals that were already won.
• Negotiate calmly, and know your limits. Price talk is normal. Defend your value, don't discount reflexively, and aim for a deal both sides are glad they made.

When you believe the product helps, and after good discovery and a tailored demo you should, asking for the business is doing the customer a favor, not pressuring them. The honest version of urgency follows from the same belief: you point at the real cost of waiting (another quarter of that eleven percent fuel spend, burning while Marcus deliberates), never a fake "this price disappears Friday." Honest urgency is both true and kind; manipulative urgency works once and costs you the relationship. Dario asks for Marcus's business because he actually thinks Brightwheel will save the man money, and Marcus signs feeling helped, not handled.

Worked example — Marcus Thorne signs

Pull the whole thread together. Dario booked the account; in discovery Marcus named two pains, backtracking routes and an eleven percent fuel jump.

The demo. Priscilla shows two things, not twelve. She runs one of Marcus's real lanes and lands a route forty minutes shorter, then ties it straight to the fuel line. Renske stops twice to ask if it matches how dispatchers actually work — and that's how the dispatcher objection surfaces in the room instead of in a dead email thread.

The objections. Marcus worries his dispatchers won't adopt a tool that adds a screen. Dario runs LAARC: he listens, acknowledges it's a fair worry, assesses (it's retraining, not the screen), responds with how two similar carriers onboarded in a week, and confirms it's settled. Later comes "too expensive." Dario doesn't flinch or discount — he assesses, finds the real worry (are the fuel savings real?), and reframes value through Marcus's own numbers.

The close. Dario asks. "I think this saves you real money starting next month. Shall we get started?" Marcus pushes on price; Dario holds his value, gives one sensible concession, and points at the honest cost of waiting — another quarter of fuel bleed. He lays out a clean first week and a one-page order form. Marcus signs.

One deal. A tailored demo, welcomed objections, a confident honest close — Topic 6's understanding turned into a won account, with Marcus feeling like a man who just solved a problem. Because he did.