Open with a clear agreement
The meeting structure here comes from Sandler: establish rapport, agree the purpose and process, understand the problem, discuss fit, and establish an outcome. Sandler's up-front contract is a mutual agreement about how the conversation will run. It is not a trap and not a device for forcing a purchase.
That gives the buyer a voice and makes the end of the meeting less awkward for both sides. Then ask about the current workflow, the problem, its impact, the reason to act now and who else is involved in the decision. Learn enough to tailor what you show, without turning the call into a questionnaire that postpones all value to the back half.
Prepare for the merchant, not the deck
Before the call, look at the account's site, the signal that prompted contact and whatever the buyer has already said. Choose the workflow and the proof from that, then prepare questions about what you still do not know. You want enough context to avoid a generic presentation and enough humility to let the buyer correct what you got wrong. Do not spend hours estimating every number about their business from outside. Ask for the inputs when the conversation reaches the financial case. They have the real ones.
The three-view demo
| View | What it shows | The question it answers |
|---|---|---|
| 1. Deck | The problem, the relevant outcome, customer proof and the commercial story | Why does this capability matter? |
| 2. Live merchant experience | How shoppers or other external users encounter the product | What does the result look like? |
| 3. Platform back end | How the merchant's team configures and operates it | Can our team run this? |
Some apps have no shopper-facing interface. In that case show the relevant external output or workflow, and do not invent a view to satisfy the framework.
Start with a relevant example, then show how it is produced, so the merchant sees the result before the settings. For a shopper-facing app, use a real or clearly labeled demonstration store. For an internal tool, show the operator's task and its output. The deck frames the story and carries the commercial context. It is not there to narrate buttons. Stop occasionally and check: "This is the workflow you described. Is anything important missing?" That costs ten seconds and can save the remaining forty minutes from a wrong assumption.
Build an honest financial estimate
Use inputs the merchant can inspect, and state the period, the baseline, the expected change and the relevant cost. Keep estimates visibly separate from established results.
The merchant handles 500 monthly tasks and estimates two minutes saved on each. That is 1,000 minutes, or roughly 16.7 hours. At their own $30 hourly labor assumption, the capacity value is about $500 a month. Against a $150 fee, the modeled difference is $350 before any other costs.
This is an estimate about capacity, and capacity is not cash. Nothing here guarantees that paid labor expense actually falls. Where task volume or time saved is uncertain, show a range.
At one minute saved per task, the same model gives about 8.3 hours and $250 of capacity value. The lower scenario is still useful, because it gives the merchant a floor to judge the fee against.
Make an offer with a real decision date
A time-limited incentive can help a merchant act. State the actual offer, the eligibility, the deadline and the normal price. A $2,000 annual plan offered at $1,000 illustrates a pricing structure. It is not a recommendation that every app discount by half.
The deadline must correspond to a real commercial offer or implementation commitment. Announcing a final deadline every week for a month teaches the buyer that your dates mean nothing, and that lesson is hard to unteach. Where fit is established, ask for the business. Where the merchant needs another step first, agree what has to happen, who owns it and when you speak next.
Handle a feature gap directly
If the app cannot do something the merchant needs, say so plainly. Then find out whether an existing configuration or an acceptable workaround meets the business need. If new work is genuinely under consideration, separate that decision from the demo you are in. Do not make an engineering commitment because a prospect feels close to signing. Give the team enough detail to estimate the effort and decide whether the capability belongs in the product at all.
A confident limitation preserves trust. A vague promise can close the conversation and create a delivery problem that returns later as churn and a public review.
Review the demo as an operating asset
Where recordings are available and appropriate, use them on yourself. Ask five questions each time.
- Did the discovery questions change what you showed?
- Did you make a claim you cannot support?
- Did the merchant see the workflow that matters to them?
- Was the pricing clear?
- Was the next step explicit?
Review losses and wins. A won deal can contain habits that will fail you elsewhere, and a lost deal is sometimes well-qualified work that kept an unsuitable customer out of the business.
Do this week
- Write your opening agreement and say it aloud once before your next demo.
- Prepare the account: their site, the signal that prompted contact, the workflow and the proof you will show.
- Build a financial estimate template that uses merchant-supplied inputs and shows a low and a high scenario.
- Review three recent demos against the five questions and revise your agenda from the gaps.
Questions
How long should a Shopify app demo be?
The book does not set a length. It sets a structure: agree the purpose and process, understand the problem, show the parts that matter, and leave time for pricing and next steps. Let the merchant's situation decide what you show, not a full feature tour.
What is a Sandler up-front contract in a software demo?
It is a mutual agreement about how the conversation will run, including that either side can say it is not a fit. It gives the buyer a voice and makes the end of the meeting easier. It is not a trap or a device for forcing a purchase.
What should I do when my app lacks a feature the prospect needs?
Say so plainly, then find out whether an existing configuration or workaround meets the business need. Keep any product decision separate from the demo, and do not make an engineering commitment because the prospect feels close to signing.
Related guides
Chapter 3: Self-serve, assisted or hybrid: how should Shopify merchants buy your app?Chapter 13: How to keep Shopify app deals moving or close them outNumbers marked as planning examples are arithmetic illustrations, not Shopify benchmarks or promised results. Founder-reported figures are not independently audited. Platform rules change: confirm current requirements with Shopify before you act.