Code is the easy part.

One of the first things we ever shipped was a clean little site for a company just getting off the ground. It worked, it loaded fast, it looked right. And then nothing happened. No one arrived. The client had paid for a website and quietly assumed a website meant customers. It doesn’t. We’d handed over a well-built room with no door.

That gap stuck with us. Writing the code is, most of the time, the part we worry about least — it’s a solved problem, and there are people here who are very good at it. What actually decides whether something lives is everything wrapped around the code: whether it’s positioned so a stranger understands it in five seconds, whether the page earns the click, whether search can find it at all, whether there’s a real plan to put it in front of the people it’s for.

Most of what makes software succeed happens after the software is done. So we stopped treating that part as someone else’s job.

It’s why the collective was never only engineers. The same group that builds a thing also shapes how it’s said, how it looks, and how it reaches a market — the domain and mailbox that make it feel real, the search and analytics plumbing underneath, the positioning and growth work on top. Not bolted on afterward by people who never saw the code, but part of the same piece of thinking.

We’re learning it on ourselves now

The two products we’re building in the lab — our accounting platform VANTA and our procurement tool Tawrio — are teaching us the same lesson from the other side. Both can be genuinely good and still sit unnoticed if we skip the unglamorous distribution work: the naming, the story, the channels, the follow-through. Building our own has made us sharper at the last mile for everyone else — because now we’re the client too, and the silence after a launch is ours to fix.