3 min readproductgrowthromania
Building in a small market is a feature, not a bug
Romania will never be anyone's TAM slide. That constraint shaped how I build products — and I've come to see it as an advantage, not a handicap.
Every startup pitch I’ve ever seen has the same slide: a huge addressable market, a modest wedge, an arrow pointing up and to the right. Romania doesn’t fit on that slide. Nineteen million people, a fragmented SME landscape, a language nobody learns for business reasons. By Silicon Valley logic, the rational move is to build for somewhere else.
I’ve spent the last decade doing the opposite, and I want to make the case that a small market is not a limitation you tolerate. It is a design constraint that produces better products — if you take it seriously.
Small markets punish spray-and-pray
In a huge market you can be mediocre and still grow: there is always another segment to burn through. In a small market, word travels. The pool of Romanian freelancers or accountants is finite, and they talk to each other. If your onboarding is confusing or your support is slow, you don’t get a fresh cohort tomorrow — you get a reputation.
That sounds terrifying. It is actually discipline for free. Retention and referral stop being growth-team metrics and become existential. You learn to fix the funnel instead of feeding it, because feeding it is not an option. Every growth system I’ve built since starts from that assumption.
Local depth is a moat imports can’t cross
Global products win on polish and lose on specifics. The specifics are where a local builder lives. Romanian invoicing isn’t generic invoicing — it’s e-Factura, ANAF tokens, and SPV quirks. Company verification isn’t a Clearbit lookup — it’s five official registries with five different ideas of what an API is.
None of that work is glamorous, and that is exactly the point: no global player will do it properly for a market this size. The integration nobody wants to build is a moat nobody wants to attack. When regulation shifts — and in Romania it shifts often — the local product that already speaks the government’s language wins the entire adoption wave.
Constraints force sequencing
With a small ceiling, you cannot afford five bets at once. You pick the one segment whose problem you understand deeply — freelancers who hate paperwork, firms that get burned by bad-paying clients — and you go uncomfortably narrow. The market size makes focus non-negotiable, and focus is the thing large-market teams struggle to maintain when everything looks like opportunity.
There is a quieter benefit, too: in a market this size you can actually talk to a meaningful share of your users. Discovery isn’t a statistical exercise; it’s a habit. The distance between “we think” and “we asked” is a phone call.
The compounding local reputation
The person who built a product accountants trust is the person whose next product accountants will try. In small markets, personal reputation and product reputation merge — every launch inherits the trust of the last one. That is a compounding asset you simply cannot build as employee #4,000 of a global platform, and it is the honest reason my own site exists: the brand and the products lift each other.
The playbook, condensed
If you’re building in a market the size of mine: treat retention as the only growth channel that matters early. Build the integrations nobody else will. Go narrower than feels safe. Ship trust signals as features. And write about what you learn — in a small market, being the person who explains the system is a distribution strategy in itself.
A small market won’t make you a unicorn. It will make you a better product builder, faster, than a large one ever would. That trade has been worth it every time I’ve made it.