Aveny started the way most small studios do: client work. Digital media projects, B2B platforms, the kind of engagements where someone else has the idea and you bring the execution. It is honest work, and for a while it was the entire business.
It also has a ceiling built into it that no amount of skill removes.
What client work does not give you
Every client project ends the same way, regardless of how well it went: you hand it over, the relationship winds down, and you start the next one from zero. Revenue resets every quarter. Nothing compounds — not the product, not the audience, not the brand, because none of those things belong to the studio. You get better at delivering, but you never get to keep what you deliver.
There is also a subtler cost. When every project is scoped by someone else's brief, you spend all of your judgment executing someone else's vision and none of it building your own. That is fine for a while. It stops being fine once you notice you have opinions about what should get built that no client brief will ever ask you to act on.
Where Voisary came from
Voisary did not start as a business plan. It started as an annoyance — the same one described in a few of the posts on this blog: good ideas showing up at inconvenient moments and dying there because capturing them took longer than having them did. We tried the existing tools, ran into the same reliability problems everyone else describes, and eventually asked the obvious question: if we are going to spend real engineering time solving this for ourselves, why not build it properly and let other people use it too.
That is a very different starting point from a client brief. Nobody handed us a spec. We got to decide what mattered — which is why reliability came before any feature, and why the design system had to feel like something we would actually want to open every day.
How the two feed each other
Client work and product work are not really in competition inside the studio, even though it might look that way from outside. Client projects fund the runway that lets us build something like Voisary without needing it to be profitable on day one — a product needs time to be good before it needs to be commercially successful, and client revenue buys that time. In the other direction, everything we learn building Voisary — the design decisions, the engineering discipline that comes from local-first architecture, the discomfort of shipping something with our own name attached to the outcome — makes us better at the client work too, because it is no longer theoretical. We are not advising clients on decisions we have never had to live with ourselves.
Where this goes
The plan is not to abandon client work the moment a product takes off, and it is not to treat products as a side project either. It is to keep both running, because each one is honest in a way the other cannot be alone: client work keeps us accountable to what people will actually pay for right now, and product work keeps us accountable to the things we believe should exist whether or not anyone asked for them yet.
Voisary is the first product built this way. It will not be the last.