There is no team meeting behind Zorya, no product roadmap debated across six departments, no growth team deciding which notification might lift engagement by two percent this quarter. There is my husband Tomislav and me, working from the same table most days, building something we actually needed ourselves and could not find anywhere else on the market.
We run a two person studio, and the honest truth is that a company that size cannot compete with a funded startup on marketing budget, on paid placement, or on the sheer speed of shipping new features every single week. What it can do, and what we have tried to lean into rather than apologize for, is say no to things a bigger team would feel real pressure to say yes to.
What a small team gets to skip
A funded company answering to investors generally needs a growth story, a path toward recurring revenue, a reason the valuation keeps climbing quarter over quarter. Those pressures shape products in ways that are not always visible to the person actually using the app, but they are there, quietly, in every design decision that nudges toward more engagement, more data collection, more accounts, more upsells stacked on top of one another. We do not have investors asking why the daily active user number dipped last week, so we never had to build anything designed purely to chase that number back up again.
That freedom is not really about idealism, whatever it might sound like described this way. It is mostly just structural. Two people, paid directly by the people using the app rather than by advertisers or data partners sitting somewhere upstream, do not need the same growth engine a venture funded team does to stay afloat. We can build something quieter simply because nobody is standing over our shoulder asking why it is not louder yet.
Why we still build it the slow way
Being small also means everything takes a genuinely long time, and we have made peace with that trade in full. A single feature, like the archive for pregnancy outcomes we shipped a while back, took months of quiet, careful thought before either of us felt ready to write a single line of code for it, because getting it wrong would have meant getting something painful wrong for someone during a moment that mattered enormously to them. A team of fifty might have shipped a rougher version in a two week sprint and iterated later based on feedback. We would rather take the months up front and get it right the first time, since there is no real version two for a decision like that one.
Working together, as two people who built this studio from nothing and happen to also share a home, means the conversations about what to build next never really stop, even well outside anything resembling normal work hours. An idea raised over dinner might turn into a feature we ship the following month. A concern raised at midnight about how a symptom log should behave might genuinely change how we write it the next morning before either of us has had coffee. That kind of continuous, unstructured thinking is hard to replicate across a larger team, and honestly, we would not trade it for the extra resources a bigger one might bring to the table.
What this means for the people using it
None of this is a pitch for smallness as some kind of virtue in itself, since plenty of excellent products come from large, well resourced teams working in a completely different way. It just means that when you open Zorya, you are using something built by two specific people who thought carefully about each part of it, rather than a product shaped by committee, quarterly targets, or a roadmap optimized for numbers neither of us particularly cares about tracking. We built the app we wished existed while expecting our own first child, back when neither of us had any idea how much the two of us could actually build together. Everything since has just been an attempt to build it a little better, one careful decision at a time.
The part we did not expect
What surprised us most, honestly, was how many people wrote in simply to say the app felt calm, a word we did not set out chasing when we started but that seems to matter enormously to the people using it. We did not have a slide deck predicting that outcome or a metric tracking for it. It came from two people building something slowly, arguing over small details at our own kitchen table, and caring more about getting each part right than about getting it out the door quickly. That is still, more or less, how every new part of Zorya gets built today.
Odgovori