The demo is the highest-leverage thing you will do as a partner, and almost everyone gets it wrong the same way: they present.
Here is the whole reframe. You are not showing a product. You are showing an owner their own week, running. Everything below follows from that.
At a glance:
- Prepare one thing — their business, not your slides
- Open by asking, not by explaining
- Put it on the screen and shut up
- Answer the second question well — it’s the real one
- Leave something real behind, not a follow-up promise
Prepare one thing
Not a deck. Not a feature tour. Learn enough about their business to put it on the screen: what they sell, when they’re busy, what question customers ask them forty times a week.
Ten minutes of homework is enough. Walk past, look at the menu, read their reviews, notice that every third review mentions the same question. That’s your demo.
Open by asking
The first two minutes belong to them. What eats your week? What do you answer over and over? What happens to the calls you miss while you’re serving someone?
This isn’t rapport-building filler — it’s you finding out which of the things you’re about to show is the one that matters to this person. An owner who has just described their problem out loud is a different audience from one who hasn’t.
Put it on the screen, then stop talking
Now show their business, running. Their twin answering the question their reviews complain about. Their day, organised. Whatever the opening conversation told you to show.
Then stop. The silence is doing the work — this is the moment they either recognise their own week or they don’t, and you cannot talk anybody into recognition. Your job here is to shut up at the right moment, which is harder than it sounds and is the single skill that separates a good demo from a bad one.
Show one thing well. A demo that covers everything demonstrates nothing.
The second question is the real one
The first question is usually polite. The second one is what they actually care about — what happens to my existing setup, who sees this, what if it gets something wrong, what does this cost me.
Answer that one carefully and honestly, including the parts that aren’t flattering. If you don’t know, say you don’t know and find out — #training is where you go, and coming back tomorrow with the true answer beats improvising today. An owner remembers being told the truth about a limitation far longer than they remember a smooth pitch.
Leave something real behind
The worst ending is “I’ll send you some information.”
The best ending is that something exists now that didn’t exist an hour ago. A twin with their business in it. A question it can already answer. And where it applies, the Echo OS pilot — approved businesses get credit toward the work their twin does, which means the conversation can end with real work rather than a maybe. Applying isn’t the same as being approved, so say that plainly rather than implying it’s automatic.
The mistakes I’d warn you about
Demoing the platform instead of their business. Nobody buys an architecture.
Talking through the silence. See above. It’s the whole thing.
Overpromising on the roadmap. Anything not live today is coming, and you say so. A partner who oversells a feature is the reason a customer feels lied to in month two, and you’re the one still standing there in month two.
Treating a no as a failure. A demo that ends in “not for us” and a good relationship is a better outcome than a yes you had to push for. You’re going to be on this street a long time.