For sixteen years I was inside a business — not next to one

I built, hired, fired, sold, counted money, solved operational problems and scaled a system. I built and developed 11 units; at its peak the network counted 14. For the fourth year now, part of that system runs without my daily involvement.

What I built

A partner distribution network in wellness. The model didn't rest on customer acquisition alone. What mattered was a repeatable unit, customer retention, repeat purchases and recurring economics.

Back then I didn't call it unit economics, retention or recurring revenue. I simply knew: if a system can't hold a customer and reproduce a result consistently, it can't be scaled properly.

What broke — and what held

Then the system met something I couldn't influence: COVID, and later the full-scale war. Part of the business didn't survive those changes.

Part of it did. And today, in its fourth year without my involvement in operations, it runs and produces more turnover than during the period I was actively working in it.

Why I left

I didn't leave because of the crises — the system survived those. I left because I hit a ceiling built into the model itself: part of the rules the result depended on weren't written by me.

I realised I no longer wanted to build my life around something I can't influence. So I stepped out of operations and started building the next stage.

What I do now

I'm building bottleneck — a practice of business diagnostics and operational advisory.

Why diagnostics? Because looking back, for all sixteen years I was doing the same thing: working out what exactly was limiting the system, why it wasn't performing as it could, and what had to change for it to perform better.

I just didn't call it a bottleneck back then.

Honestly about how old this practice is

It's young. A few months old. Behind it stand sixteen years of operational experience and one completed project that I took to a result — and that I'm willing to discuss not only through the good numbers but through what didn't work.

I won't pretend I already have twenty cases in every industry. I don't.

What I do have is knowing what it's like to build a business yourself: hiring and firing people, counting money, working with customers, living through operational trouble, looking for growth, scaling a system and eventually stepping out of it.

Where this goes

The long-term goal is to grow the advisory practice and gradually move from working with businesses to participating in their development and investing in them.

bottleneck is the first stage of that path.

Personal

I live in Odesa. My family is here, my life is here, and this is home.

I'm not building this for a professional title or another line on a CV. What interests me is creating an environment of people who build real things, taking part in strong projects, and gradually gaining more freedom — in time, in decisions, and in choosing what to take on.

Diagnosing other people's business systems is the first school on that path. And so far the best one I know.