When rejection is gold. But in hindsight.

"You're not ready for this."

‍

Back in 2012, I was sitting across from a consultant who specialized in helping companies incorporate abroad. I'd been chasing him for weeks — even though his services weren't cheap. I wanted to open a US entity for my agency, convinced it was the missing piece. Other founders in my circle kept telling me that American clients prefer working with a local business. No messy international wire transfers, no foreign jurisdiction anxiety. Made total sense. I was sure we were losing deals left and right because we didn't have that.

‍

He looked at me and said the last thing I expected: "Eugene, I could happily take your money. But you're not ready."

‍

He laid it out. Opening a company in another country isn't just access to opportunities you may or may not actually get — it's a financial and legal weight. Accounting, compliance, reporting, local regulations full of traps you don't see until they bite you. "All those stories about simply registering a corporation in Delaware," he said. "They're not untrue. They're just not the full picture. People leave out the hard parts because it's easier to sell the dream." Instead of chasing a shortcut to the US market, he told me, I should be building better sales and stronger delivery with the clients who were already willing to work with an overseas agency. That was harder. Less glamorous. No silver bullet.

‍

I didn't want to hear it.

‍

And here's the part I'm most grateful for. We had to play on hard mode — no US entity, no local advantage, no easy wins. We had to get better at selling, better at delivering, better at proving we were worth the hassle of an international transfer. It took time. It was uncomfortable. But it made us stronger in ways a Delaware registration never would have. Two years later, I found a partner in the States who became a co-founder. By then, my business, my team, and I were actually ready for what that partnership opened up. And when it was time to formally incorporate abroad, I went back to the same consultant — the one who'd turned me away. Because his "no" was the reason I now understood what I was doing. I could make real decisions instead of guessing. I knew the right questions to ask and why his answers mattered.

‍

"It'll just work on its own"

‍

A few months ago, a founder reached out to me. He runs a small SEO agency — him and a handful of people. He wanted operational architecture. Systems, automations, a workspace that would make everything run smoothly.

‍

I turned him down. Twice.

‍

Not because he didn't need help — he did. But I could hear something in what he was asking for that I recognized too well. He wanted the system to fix the problem by itself. Set up the tools, flip the switch, and suddenly the team stops making mistakes, stops needing supervision, starts taking ownership. No more checking everyone's work. No more reshuffling priorities. Just order, delivered in a Notion package. I've made that exact wish. Over the years, before AI was even in the picture, I went through the same cycle with my own agency. Redmine. Trello. Jira in every configuration imaginable. Custom automations we spent thousands building — and then threw away. Each time, I believed the tool was the answer. Each time, the tool sat unused within weeks because the team didn't see the point, or something urgent came up and the process got abandoned. Or — and this was the hardest one to admit — I was the first person to stop following it.

‍

When I finally did build systems that stuck, it wasn't because the tool was better. It was because I started small enough that people could actually adopt it. One habit. One rhythm. I had to explain, over and over, what was in it for them — not just hand them a workspace and expect compliance. I dealt with resistance, sabotage, eye-rolling. The moment I tried to roll out three things at once, something fell apart. The moment a client emergency hit, everything got dropped.

‍

And I have to say something that's harder to admit publicly. In my consulting work, not every project has been a success. The ones that failed had one thing in common: I took on a founder I could see wasn't ready. Someone looking for a silver bullet. I did the work, built the architecture, handed it over. And it sat there. Unused. Because the founder expected it to run without him — without conversations with his team, without pushing through the uncomfortable period, without being the first one to follow the rules he wanted everyone else to follow.

‍

That was my mistake. Not theirs. I should have said no.

‍

What I've come to understand over the years — from that consultant's refusal and from my own failures — is that "not ready" isn't an insult. It's timing. The tool, the framework, the system — none of it matters until the person adopting it has done the boring groundwork first. Getting the team to buy in, not just informing them. Starting small enough that the habit actually takes root. Showing up yourself, every single time, before expecting anyone else to. That consultant didn't refuse me because my idea was wrong. He refused me because my foundation wasn't there yet. And I try to do the same thing now — even though it means turning away work.

‍

Something to try this weekend:

‍

Before you invest in a new tool, a new system, or a new hire to fix your operations — pick one small ritual. Just one.

Maybe it's a Friday async update where every team member posts what they worked on, what's stuck, and what's next. Make it non-negotiable. Do it yourself first. Don't add anything else for a month.

If one ritual can't survive four weeks, no system will survive a quarter.

‍

I'm curious: have you ever been told "you're not ready" — by a mentor, a consultant, a partner — and fought it, only to realize later they were protecting you from yourself?

‍

P.S. When I went back to that same consultant in 2014, he didn't say "I told you so." He just helped me do it right. That's how I knew I'd picked the right person to say no to me.