Demo before the pitch
Why we build first and write second

Most first contact between a company and a studio is a promise. A deck, a call, a proposal: here is what we could do for you. The buyer has to imagine the result and trust that the people in front of them can produce it. Both are hard, and the buyer knows the studio has an incentive to oversell.

We do it the other way round. Before we write to a business, we build a piece of the system we think it needs. A launch film for a dealer, cut from their own cars and their own showroom. A landing page for a clinic that already answers the questions its patients ask on the phone. A dashboard for a retail chain, filled with the numbers it publishes anyway. Then the first letter says: we made this for you, here it is, this is what we saw.

It costs us a few days per company. It saves the buyer the hardest step, imagining. They are not evaluating a promise, they are looking at a thing and deciding whether they want more of it. The conversation starts from the object, not from us.

It also filters us. If we cannot build something useful for a company from the outside in a few days, we probably cannot build a system for them from the inside in a few weeks either. The demo is the audit we run on ourselves.

Every one of these pieces becomes a Lab entry, numbered, with what it showed. The company stays unnamed until it answers. After that, the entry gets a name and, usually, a second part.