I sleep on a mattress so my kid doesn't have to

A few months ago, I had a diagnostic call with a founder who ran a small marketing agency. It started like most of my calls — swapping notes, talking shop, me sharing scars. Standard stuff.

Then somewhere in the middle, he said something that turned the conversation into something else entirely.

‍

I'd asked him: "What do you actually want? Not just 'more revenue' — what's this all for?"

He paused for a long time. Then:

"I want to give my kid a chance at a better life. So they don't have to go through what I did. And for that, I'm willing to sleep on a mattress for as long as it takes."

‍

He wasn't being dramatic. He meant it literally.

‍

He'd moved to the US a year earlier — a leap of faith, leaving his family behind temporarily while he got things stable. His agency was doing six figures in revenue. On paper, successful.

But he was living in a nearly empty apartment with a mattress on the floor, working 12-15 hours a day, seven days a week. His wife and kid were still back home. He flew back when he could, but it was never enough time, and the guilt was eating him alive. "She supports me," he said. "I'm lucky. But I know I can't keep this up. I need to figure out how to make this work without killing myself."

‍

The trap he was stuck in

‍

He had seven freelancers: designer, ad specialist, copywriter, automation guy, web developer, SEO person, and an outsourced bookkeeper. No client manager. No project manager. No ops person.

Just him holding everything together.

He set all the tasks, handled all client communication, reviewed every deliverable before it went out — because freelancers would miss things, send incomplete reports, forget deadlines. He did the sales, the approvals, the quality checks, the follow-ups. Everything. And he was drowning.

‍

"I know this isn't sustainable," he told me. "But I don't even know where to start. I'm willing to work hard — I just want that work to actually move me toward the goal instead of just keeping me stuck."

That hit me hard because I recognized it immediately. I've been there. My parents were there in the '90s, trying to give us a better life in a collapsing Soviet Union.

This wasn't complaining. This was desperation for a way out.

‍

We walked through the Ops-On-Demand Sprint together.

First, we mapped out the structure and architecture his business actually needed — not some theoretical org chart, but what would work for his situation with freelancers and tight resources.

Then we identified which roles he was playing that he shouldn't be. The answer? Almost all of them. We designed clear expected outcomes for every role so people knew what success looked like without needing constant check-ins.

And we built an operational rhythm — daily, weekly, monthly — so he wasn't just reacting to whatever fire appeared that day, but had a clear understanding of who does what, when, and why.

‍

The biggest shift was in realizing he needed at least one full-time person — not another freelancer, but someone emotionally invested in the company. Someone who would help maintain and run the system.

We designed an ops manager role with some light project management — T-shaped skills for a small team. Someone who could wear multiple hats but knew exactly which hat they were wearing and what they were responsible for.

Most importantly, we identified decisions he could safely delegate. Not everything — freelancers aren't the relationship where you hand off strategic choices. But daily operations? Routine client updates? Quality checks on standard deliverables?

Those could go to the ops manager.

‍

The moment that stayed with me

‍

Two weeks later, we had the handoff call — the final session where I walk through the entire system, showing how each piece works, what it's for, and how it frees up time.

He listened carefully, asked questions, took notes. Then he said: "I finally see it. I finally understand how this is supposed to work."

His voice caught a little when he said it.

‍

And I felt something I don't feel often enough in this work: the weight of actually mattering. Not just "here's a system, good luck." But knowing that what we built together could genuinely change the trajectory of his life — and his family's.

We're still working together now, halfway through the 90-Day Opstructure Sprint where I help adapt, implement, and support the system as it goes live. Adjusting based on real feedback, troubleshooting what's not working, helping him actually launch the structure instead of just having it sit in a document somewhere.

‍

He's still sleeping on that mattress. Because his dream isn't an Instagram version of success — it's real, it's specific, and it requires sacrifice. But now the sacrifice has direction.

Before, he was working 15-hour days just to stay afloat, with no clear path to anything different. Now he has a map. He knows what needs to happen, in what order, and why.

He's building a team, not just hiring hands. He's delegating decisions, not just tasks. He's creating a structure that can hold more weight as he grows instead of collapsing under it.

‍

What this actually means

‍

There's no shortcut out of his situation. I told him that on the first call. Building real structure takes time. Hiring the right person takes patience. Getting freelancers to follow protocols requires consistency. But the difference between sacrifice with a plan and sacrifice without one is everything. One leads somewhere. The other just grinds you down until something breaks — your health, your relationships, your dream.

Some founders are willing to do whatever it takes. They'll sleep on mattresses, work brutal hours, sacrifice time with family.

But willingness isn't enough.

‍

They need clarity on how to turn that sacrifice into progress instead of just survival. That's what systems do. Not because they're efficient or scalable or any of that consultant bullshit. But because they turn desperate hustle into deliberate movement toward something real.

So I want to ask you something. Are you sacrificing right now? Time, health, relationships, sanity? And is that sacrifice actually moving you toward something — or just keeping you stuck in place?

Because if it's the second one, you're not being disciplined. You're just trapped. Hit reply and tell me. I'm curious how many founders are grinding without a map.

‍

P.S. That founder is still working brutal hours. Still sacrificing. But now when his kid asks "when are you coming home?" he has an actual answer. Not "I don't know" but "Here's what I'm building, and here's when it'll be ready." That clarity alone is worth more than any revenue number.