A demo is usually built as a sales asset: perfect data, happy paths, a narrator. We built ours as a product surface instead — the real dashboard and the real recovery views, running on a sample merchant, clickable end to end. The reason is that the questions a merchant brings to a demo are product questions. What does a failure look like when it lands? Where does the money show up when it is recovered? What will my Monday morning screen actually say?
Sample data answers those honestly in a way a pitch deck cannot. A synthetic store with a realistic failure mix — some expired cards, some payday problems, a few hopeless cases stopped on sight — teaches the taxonomy faster than any copy. And it respects the visitor: no card, no sales call, no gated PDF. Look first; the trial asks for commitment later, in the right order.
That order matters to Swipe Again generally — the funnel is signup, card, then connect, and the demo sits before all of it as pure evidence. Products in this category all claim roughly the same recoveries. The ones that let you watch the machine work, on data that behaves like yours, are making a different claim: that the machine is the pitch. Ours is at the end of the recovery flow — same screens a paying merchant gets, because anything less would be advertising instead.
Top comments (1)
Running the demo on the same screens a paying merchant gets is the strongest version of this, because nothing in it can drift away from the product. Two things I'd watch with a synthetic store. Keep its dates rolling, so recovered payments always land in the last few days and the dashboard never looks like an old snapshot. And reset the sample merchant for each visitor, so nobody walks into a state someone else left behind. For people who won't click through, a short clip of one failure going from expired card to recovered payment can sit next to the link and show the same idea in a few seconds.