Why we still build our own apps while taking client work

Most studios that start by building their own products quietly stop once client work starts paying reliably. It's a rational trade on paper: client work is revenue, your own products are a cost center with no guaranteed return. We understand the math. We've decided not to make that trade.

Trinetra and Urban Hood are both live today, and we design and build for clients the same way we build them: as a full product studio, strategy, design, and engineering under one roof, not two different standards depending on whose name is on the product. Keeping our own apps running isn't nostalgia for how we started. It's the only mechanism we trust to keep our own standards honest.

Here's the failure mode we're avoiding: a studio that only builds for clients stops being its own user. It starts trusting its own pitch instead of its own daily experience of the software it makes. We are our own first users on Trinetra and Urban Hood, which means we feel every rough edge we'd otherwise only hear about secondhand from a client's support inbox. That feedback loop doesn't survive if we ever stop shipping our own things.

A studio that only builds for clients stops being its own user.

We'd rather run two products people love and take on a handful of client projects we're proud of than chase scale we can't stand behind, on either side of the business. It's a smaller, harder-to-optimize shape than "studio" or "product company" alone, and we think it's the only shape that keeps us honest about what we're actually good at.