A deck asks the reader to imagine. That's the whole problem with it. You slide someone twelve pages of mockups and bullet points and you're really asking them to build the product in their own head, then trust that the version you eventually ship will match the one they pictured. For a certain kind of buyer, that ask is fine. For the buyer we actually work with, it's a dead end.
The small-business owner is skeptical, busy, and has almost always been burned by a web person before. Somebody took a deposit and disappeared, or delivered a template that looked nothing like the demo, or built something so fragile the owner was afraid to touch it. That person has heard "trust me, it'll be great" and watched it not be great. Saying it again, louder, does not work.
So we build it instead of describing it
Rather than pitch what we could make, we make a version of it and hand it over. We keep a set of clickable demo businesses (a café, a med spa, a photographer, a used-car lot), and each one has a real front end plus a working back office you can actually click through. Not screenshots of a back office. The orders, the bookings, the client list, the invoices. You open it and use it like a person who runs that business would.
Right now there are eleven of these live, several with a working back office behind the storefront. When we reach out to someone who runs a med spa, we don't attach a PDF about med spas. We send the med spa demo and tell them to go break it.
Why it beats a proposal
The mechanics are simple. A proposal lives in the future tense and a demo lives in the present, and the present tense is much harder to argue with. A few things happen the moment someone clicks in:
- The "this is just a fancy Squarespace" objection dies the second they open the back office and see actual software running underneath.
- They feel the capability instead of imagining it. Feeling beats imagining every time, especially with a skeptic.
- Someone who's serious clicks around for ten minutes and comes back with questions. Someone who isn't never opens it. We find out either way without anyone having to sit through a call.
- The demo doubles as the spec. What they click is close to what they get, so the gap between "what I saw" and "what I received" (the gap that burns people) mostly closes before we've written a line for them.
- It removes the leap of faith. Nobody has to trust our taste in the abstract. It's on the screen.
The fastest way to kill "can you really build that" is to hand someone the thing and say: click it.
The honesty part
The demo brands are invented, and we label them that way, loudly, on every page. The café isn't a real café. The med spa doesn't exist. We are not trying to pass off a fake client as a real one, and we'd rather lose a deal than let someone think otherwise.
The point is narrower and, we think, more honest than a deck of stock photos and promises: show the capability on a business shaped like theirs. When a used-car dealer clicks through a used-car demo, the abstraction disappears. He's not evaluating a studio's portfolio in some other industry and doing the translation himself. He's looking at his own business, more or less, already built. The imaginative work we'd normally offload onto him is work we did first.
It costs more up front. Building eleven clickable businesses, several with a functioning back office, is real time we spent before anyone paid us. But it's time spent once, and it converts the exact person a deck can't reach: the one who's been lied to and is done imagining.
A deck says what we would build. A demo lets you use it. Only one of those closes a skeptic.
Questions are welcome: hola@xala.studio