Two Separate Tasks.

He called it the exact catch-22 everyone in the room was caught in.

You can’t hand the work off until it’s written down.

You can’t write it down because you’re too busy doing the work.

So the work keeps winning.

Andrew knew that loop well. It had already cost him a business.

Before AI, before clients, before any of this, Andrew owned a cell phone repair business.

It made seven figures. He’d basically worked his whole life to get there.

And it had become, in his words, his prison.

His wife would call a little after midnight. Andrew retold the line on stage:

He dreaded that phone ringing. In his own retelling, it meant he’d let her down again, lost track of time, buried in work.

The problem wasn’t that he didn’t hire help.

He hired plenty.

He described it later as "another hired trainee.. another several weeks invested only to be let down again.."

The pattern never changed. Bring someone in. Pull himself away from the work to teach them. Watch it fall apart. Start over.

Training was always a second job, stacked on top of the first one.

And the first one never stopped.

Sales slid from $80,000 a month to $50,000, then $30,000, then $15,000. He needed at least $12,000 just to keep the lights on.

Then someone broke in through a window AC unit and walked out with over $30,000 in cash and phones.

The next morning, he locked the doors.

All the income went away overnight.

The bills didn’t.

Andrew rebuilt from zero.

Some time later, he was working as COO for LeadGenJay, running operations inside Jay’s business.

And eventually he faced the same wall he’d hit in the shop.

He needed to hand his role to someone else.

Which meant training her.

On everything.

So he didn’t try to find the time. He gave her access to three things: his email, his Notion and his Loom account.

He opened a blank database.

And the very first thing he recorded?

As he explained it later:

The rule from that point on was simple.

Every time a task came up that hadn’t been documented yet, you hit record before you started. You talked through what you were doing while you did it. When you finished, the recording went into the database, along with the step-by-step guide and the transcript Loom generated from it.

The work didn’t stop so the training could happen.

The work became the training.

She took care of the customer. She delivered whatever needed delivering. She documented it as she went, then made sure the SOP was complete and in the system. Anything urgent, anything rated seven or higher, surfaced straight to Andrew and Jay.

And every recording only ever had to be made once.

Think about what that means.

In the shop, every new hire meant starting the teaching over from scratch.

Here, every task that got done also got taught, permanently, to whoever came next.

Same problem.

Opposite result.

Andrew started noticing that he did this everywhere.

A client call wasn’t just a client call. A build wasn’t just a build. He’d look at whatever was in front of him and ask what else it could finish while he was already doing it.

In a workshop, he put the reason plainly:

So anytime something took his time, he was asking how he could use it in more than one way.

He gave the idea a name: multiplied leverage.

And he got specific about what it isn’t.

It isn’t multitasking, which is doing two things badly at once. It isn’t repurposing, where you do one thing and chop it up afterward.

The definition he settled on is that one action checks off several things you already had to do, wanted to do, or would have been a great advantage to do. At full quality. With the multiplication built into the move from the start.

The opposite is what most of the coaching and course world sells.

You’re overwhelmed, so here’s a course. Here’s a framework. Here’s another call to attend.

On stage at a CEO event, he asked the room a simple question about documentation.

Then he gave them the fix he’d used himself.

He even turned it into a rule for his own calendar.

In other words, an hour with Andrew should hand you back at least an hour or two of finished work. Not homework.

Then Andrew met Kofi and his business partner, who run a marketing agency serving roofers and other local service businesses.

And he recognized the pattern immediately.

They wanted their time back. To get it, they believed they needed to hire.

So they hired. And then they didn’t have time to train the new person. Or they spent all their time training them. Either way, the new hire didn’t know what to do, frustration built, and they’d end up letting the person go.

Then they’d blame the assistant. Or the company that supplied the assistant.

It was the shop all over again. Just a different business.

Andrew told them where the real fault was.

Their plan was to find an extra hour or two each week to sit down and write everything up.

Andrew had seen where that kind of plan leads. He’d lived it in the shop.

So he gave them the same move he’d made when he had no time to train his replacement.

When you’re about to start a task, open Loom. Talk through what you’re doing while you do it. And as Andrew put it, "nobody’s going to care if I’m talking to myself." When you finish, the link goes into a Notion database. An assistant can clean up the generated SOP, fix the misspellings and add the links.

No separate documentation day. No extra block on the calendar.

Just the job, done out loud.

Some time later, Kofi posted this, tagging Andrew:

Close to a year.

That’s how long the training nobody had time to write had been sitting on his list.

It didn’t take finding a free week.

It took the training no longer being a separate task.

Andrew likes to say that multiplied leverage is "always very meta". Even defining multiplied leverage happened while he was in the middle of doing something else.

But the most telling thing he ever wrote about it wasn’t about efficiency at all.

In the middle of a build, coding an app while he was also building a campaign for an offer and teaching himself something new, he stopped and wrote down why it mattered so much to him. The more you work this way, he wrote, the more you can achieve:

Notice where husband and father land on that list.

Right at the front.

Because this was never really about SOPs.

It was about a man who once had every hour of his day eaten by the work, and the work that came on top of the work, until his wife was calling after midnight to remind him it was already tomorrow.

The answer was never more hours.

It was making sure nothing he does is only one thing.

You don’t need more time to create systems.

You need the systems to come out of the time you’re already spending.

That’s the answer Andrew didn’t have in the shop.

It’s the one he’s been handing out ever since.