It would be easy to spin up a new product every quarter. The ideas are there — our internal tools folder alone could seed three launches, and every founder chat ends with someone saying "you know what you should build". We don’t, and this post is the honest version of why a studio of twelve people ships exactly two products: Synkly and Autometa CRM.
The cost of a high bar
Every Autometa release is held to the same standard: precise, fast, AI-native, and genuinely pleasant to use. That bar is expensive to clear. It means the tenth revision of a screen nobody will praise, sync engineering that disappears when it works, and saying no to features that would demo well but age badly. A team of twelve can clear that bar for two products. It cannot for ten — and pretending otherwise is how software gets mediocre.
The math is unforgiving. Every product is not just its features — it is its onboarding, its documentation, its support load, its security surface, its migration paths, and its slow accumulation of edge cases. A product portfolio grows linearly; the attention it demands grows faster. Studios that ignore this end up with ten products at sixty percent, and sixty percent software is the kind people tolerate until the first alternative appears.
One engineering discipline, two products
Synkly and Autometa CRM look nothing alike on the surface — one is a watch-party and gaming app, the other runs sales pipelines and operations. Underneath, they share the same discipline: a clean system of record, a real-time layer that keeps every screen live without a refresh, and an automation engine that reacts instead of waiting to be asked.
That shared foundation is the compounding asset. The sync engine that keeps a movie frame-accurate keeps a pipeline board live across a sales floor. The automation model that routes a WhatsApp lead schedules a game-night reminder. The presence system that shows who is in a watch room shows who is viewing a deal. Two products on one foundation means every infrastructure improvement ships twice — and every hard-won lesson from one product hardens the other.
How we decide what to build next
With two products, prioritization is the whole job. Three questions filter every proposal before it reaches a roadmap:
- Does it deepen the record, real-time or automation layer — or is it a detour that only one screen will ever use?
- Will it still be the right call in three years, or does it chase a trend that will look dated by the next cycle?
- Can we support it at our quality bar with the team we actually have — including docs, support and the 2am pager?
Most ideas fail the first question, and that is fine. The internal tools folder keeps them warm. The ones that pass all three tend to ship well, because they were load-bearing before we wrote a line of code.
What focus buys our customers
Depth instead of breadth: the CRM gets a real shared inbox and a real workflow engine, not checkbox versions of each. Stability instead of churn: nothing gets abandoned when a shinier idea appears, because we did not start it unless we intended to keep it. And a support experience where the person answering has usually built the feature you are asking about.
There is a quieter benefit too: trust compounds. Teams bet their pipeline — or their Friday movie night — on software that behaves the same way next month as it did this month. Focus is how a small studio keeps that promise without a hundred-person platform team.
What’s next
More of the same, deliberately. Deeper AI in the CRM’s record layer, more of Synkly’s real-time engine exposed to bigger rooms, and the occasional post like this one when we learn something worth writing down. If that pace sounds slow, it is — in the way a foundation is slow. It is also why both products will still be here, and still good, years from now.