Edition #1: Why I waited 10 years to start

I waited 10 years to start.

That's the biggest failure of my career. Not a missed quarter. Not a botched launch. Ten years of having the time, the material, and the audience that would have shown up, and not doing the one thing I most wanted to do.

The answer for why this happened is shorter than I expected: I was scared of what would happen if it actually worked.

I'm going to walk you through what that means because I think it's the same thing keeping you from whatever you've been quietly avoiding. And the moment that broke it open for me is the same moment that changed everything since.

It happened, of all places, in my kitchen.

I had just gotten off a long call. The kind that drains every ounce of energy one has, the kind that makes you sit down for a minute after, just to find yourself again. I leaned against the counter, rubbed my eyes, and let my mind wander.

And for some reason I still don't know, that day, that moment, I imagined something specific. A stranger, somewhere in the world, buying a course I'd been quietly building for years.

Just one person. One transaction. A name I would never know.

And I froze.

Not "took a deep breath and felt nervous" kind of froze. Actually froze. My chest tightened. My hands went cold. The fear was so physical, so disproportionate to the imagined event, that I had to stop and ask myself what was happening.

Here's the absurd part: it wasn't about the money. I make more in an hour of consulting than I'd ever charge for that course. It wasn't about the work either. I'd shipped harder things a hundred times over.

The fear was about being seen.

Standing alone, in front of a stranger, with something I'd made, saying this is mine.

I'd been quietly avoiding that moment for 10 years. The course outline started in 2011. The book draft started in 2013. Somewhere in between were the social posts I wrote and never published, the videos I recorded and never uploaded, the landing pages I sketched and never bought domains for, and the podcast I never launched. I had the time. I had the material. I just kept finding reasons as to why today wasn't the day.

In that kitchen, leaning against the counter, I finally understood: I was the reason.

Not the market. Not the algorithm. Me.

The kitchen moment, however unexpected, was the aha moment of clarity. The actions that followed came months later, after something else broke first.

I had spent 15 years working 80-hour weeks across three continents, building consultancies, training students, and shipping implementations. And the ironic part? I was the person telling teams to protect their energy, to avoid burnout, to build systems that didn't depend on heroics. Meanwhile, I was running on fumes.

Less than fumes, actually. By April of last year, I was crawling on empty.

Half my staff had been poached. My senior leadership had quietly checked out. A former business partner had held six+ months of unpaid invoices over my head and walked away with people I had trained, mentored and eventually hired. I was sitting in the Mekanys office one morning, looking at a sales pipeline that read zero (overdramatizing for effect), doing the math on a payroll I wasn't sure I could meet, and realising that the only person I had not been protecting was the one running everything.

That's the moment most operators expect to be a low. And it was. But here's the kicker: it was also the moment things finally got clear.

When you have nothing left, the things you used to overthink stop mattering. The voice that asked what will people say if I post this? went quiet. Not because the fear left, but because there was no energy left to spend on it.

In that strange, empty space, I started.

I wrote a LinkedIn post. Then another. The first ones were stiff and awkward and read like a corporate memo trying to be a friend. I knew they were bad. I posted them anyway.

A few months in, I looked back at those early posts and cringed. That cringe was data. It meant I'd grown.

If you'd asked me at any point during those 10 years why I hadn't started, I would have given you a different answer each time. I'm too busy. I don't have a clear angle. The market's too saturated. I'm not ready. I'll start once we hit Q4 numbers. Once I have time to do it properly.

All of those answers were lies. Not deliberate ones, but lies all the same.

The real reason was simpler, and harder to admit: I was protecting an identity I hadn't earned. The quiet expert. The one whose work was supposed to speak for itself, who was too senior to be a beginner at anything publicly.

The day I started posting, I had to surrender that identity.

Because in truth, when you start something publicly, you are a beginner. The 7,300 days of operations work behind me, the 300+ implementations, the hundreds of people I mentored. None of that transferred to the skill of putting yourself in front of an audience and offering something. That was day one. And nobody starts good at it on day one.

The 10-year delay wasn't a time problem. It was a willingness problem. I wasn't willing to be visibly bad at something while I learned to be good.

I'm telling you all this because I want to set a contract with you today, in Edition #1, before either of us has any reason to pretend.

The Exceptional OS is not a marketing newsletter. It's not a curated link roundup. It's not a sales pitch dressed up as content.

It's me, sitting down each Saturday, sending you one applied lesson from 20 years of building businesses that, when I did the work right, kept running without me. And, more honestly, from the ones when I did the work wrong, and they didn't.

Some Saturdays the lesson will be tactical. A framework, a checklist, something you can apply on Monday morning. Other Saturdays it will be more like this one. Closer to the ground, less polished, about the human cost of running a company and the patterns that keep operators stuck.

What I will not do is sell you something every week. The newsletter is free, and it stays free. I run a consultancy that does paid implementation work; if you ever decide that's a fit, you'll know where to find it. But that's not what Saturdays are for.

Saturdays are for the conversation between two operators who are honest with each other.

Over the next few weeks, I'm going to walk you through something I think most consultants get wrong, and most operators feel in their bones but can't articulate.

The thesis is simple: most "AI strategy" engagements solve the wrong problem. The tools didn't fail. The implementation skipped the only step that matters. The CRM that nobody uses, the automation that gets bypassed, the platform sitting next to a folder of spreadsheets that contain the actual work. None of those are technology problems. They're process problems that were never named.

I'm going to show you how I think about that, where the patterns repeat, what to look for in your own operation, and what changes when you fix the underlying thing instead of buying another tool to wrap around it.

But I wanted to start here, with this letter, so you know who's writing the next ones.

What's the project, business, or piece of work you've been quietly avoiding for years?

Not the one you don't have time for. The one you're scared of. The one where finishing it would mean standing in front of a stranger and saying this is mine.

If something came to mind in the last few seconds, that's the one. Reply to this email and tell me. I read every reply, and the answer goes nowhere except my inbox.

The work you've been delaying isn't waiting on a quieter quarter or a clearer head or a better plan.

It's waiting on you.

Go start it.

Iulian

P.S. If this letter found you in a moment when you needed it, forward it to one other operator. The audience for The Exceptional OS is people who understand what it means to be the only one running everything. You probably know one.