Chapter 05
A founder demoed her product for 40 minutes, proudly walking through every feature. The prospect said it was really impressive and never replied again. The prospect's actual problem, the one thing they'd said mattered most, never came up. It was buried in slide 34 of 40.
Fig: Choosing the screens that actually matter
Here’s the trap almost every beginner falls into at this stage: you finally get to show your product, and the temptation is to show everything it can do, because you’re proud of it. This backfires almost every time. A buyer sitting through a 40-minute tour of every feature leaves thinking that was impressive and does nothing, because nothing in that tour was clearly theirs.
A demonstration shows how the proposed change would work. A proposal documents the shared plan. Objection handling clarifies uncertainty. Treat all three as decision-support activities, not performances designed to overpower resistance.
Confirm goals and agenda first: "Based on what we discussed, I'll show you X and Y, stop me if that's not the priority." Link every screen to a discovery finding and a stakeholder. If a screen has no clear link, cut it. Feature tours that ignore this discipline are the single most common reason demos fail to move a deal forward; the buyer leaves impressed but unconvinced, because impressive and relevant are different things.
A good demo often needs only three screens, each mapped directly to something the buyer said in discovery. Skip reporting customization, integrations, or the mobile app if none of it came up. The fewer screens you show, the more each one has to earn its place.
Focused Demo, Not a Feature Tour
Commercial translation: if a screen or line could go unchanged to any buyer, cut it. A three-path demo built around what one specific buyer said in discovery will always outperform a full feature tour built to impress everyone a little.
Restate situation, outcomes, scope, responsibilities, timeline, investment, assumptions, success measures, and next step. It should help an internal champion accurately explain the decision to people who weren't in the room. "This will save you a large, round number" is weak. "Based on your stated numbers, a 30 percent reduction would free measurable hours a week, checked against your own data starting week one" is strong.
A well-formatted document, even a clean PDF or shared doc, is entirely sufficient for beginners and freelancers; structure and honesty matter far more than software. Walk through the proposal live and invite correction rather than emailing it cold.
Commercial translation: a proposal should contain no surprises. Walk through it live and invite correction; an emailed-cold proposal loses the chance to catch a costly misunderstanding before it's signed.
Listen, Acknowledge, Explore, Respond. The goal is clarity, not verbal victory. When a buyer says your price is higher than another proposal, acknowledge it's a fair concern, then explore which difference actually matters: budget, implementation effort, or confidence in the outcome. Only respond once the real driver surfaces.
Price is only one design variable. Move it together with scope, payment terms, or support level, never discount price alone. An affordability concern calls for a phased scope, not a discount. A risk concern calls for a smaller pilot, not a discount. A comparison concern calls for a structured, honest table, not a discount.
The LAER Sequence
Commercial translation: objections are a good sign, not a bad one. A buyer who has stopped objecting has usually stopped considering.
The Signature Framework
Interactive Decision Tree
Did they explicitly say it's a budget problem?
Terms to Know
A guided proof that selected capabilities can support the buyer's use case.
A reasoned comparison of expected benefits, costs, risks, and alternatives.
Acquisition plus implementation, operation, training, risk, maintenance, and switching costs.
Applied Exercise
Fill in the book's planning matrix for one screen or feature you plan to show next.
Discovery finding: [discovery finding]. I'll show: [screen or feature], for [stakeholder]. Opening line: "[opening line]"
The Complete Handbook
This site gives you one real, working lesson per chapter. The book is the full 130-page reference: every framework, every worked example, and every fillable template in one place.
Educational product. Not legal, financial, or professional advice.