Too much admin as a one-person business: where to start, and in what order

Read the table from the top, one row at a time

The table is the rule. Each row is a layer. You build them in order, and you do not start a row until the one above it works.

Why this order? Because each layer stands on the one before it. You cannot hand off a task you have not named. You cannot check a routine that does not run yet. And you cannot stop watching a system that has no alerts.

The first row costs nothing. Days 1 to 3 are about seeing, and about cutting. A task you stop never needs a system, a check or a single minute again.

Days 1 to 3, in detail: see it, then cut it

Pick one ordinary day. Not your worst. A Tuesday.

Write down every task that touched your hands. Next to each one, write who else could do it today, as things stand. Most lines will say "only me." Then ask: is it only me because it needs my judgment, or only me out of habit?

Now sort the habit tasks four ways. Stop it. Automate it. Hand the draft to AI. Keep it. Ask in that order, and stop at the first yes.

Do the stops that same day. And kill the reminder that would start each task again, or it crawls back within a month.

Common admin tasks, and where they usually land

Most guides on admin overload list the same jobs: status updates, invoices and receipts, quotes and rate questions, follow-ups. Here is how the book's four-way sort handles four of them. Treat it as a first guess, not a rule. Your own map decides.

Notice that three of the four felt like they needed you, and only one really did. The test is simple: if you can write the rule, it is not a Keep.

The book also flags the small task that seems too minor to bother with, like the receipt shuffle. That is often the one quietly eating an hour a week, so it belongs in your first pass.

Days 4 to 30: one task, all the way through

Pick one task. The one you do most often. Not the one that annoys you most.

Write a brief for it. Wire it so it starts on an event, like an email arriving, and the draft lands in one folder for a short look. Let it run a week.

Then add a short check: prices, dates, names, promises, checked against a real source. Then look for the small moves you still make between steps, the copy-paste, the "and then I." Then set two alerts, one for failure, one for "needs you," and let the rest go quiet. Last, draw the line around what stays yours.

One task, fully built, teaches you more than eight half-built ones. The confidence to build the second comes only from watching the first one work without you.

The Sunday night you try to fix it all at once

You know this one. It is Sunday. You are fed up. You open five tabs of tools and decide that this is the weekend you sort it all out.

By Wednesday half of it has broken. You can't tell which part. You go back to doing it by hand, and now you also feel like you failed.

That is not a lack of grit. It is the same instinct that kept you stuck in the first place: more effort, applied harder.

Nadia, the wedding photographer in the book, did it the slow way. She did not hire anyone. She built four routines over a couple of months, drew her line, and stopped checking her phone. Her seven-month backlog closed.

I put the order in its own chapter because people skip straight to the tools. You are not the only one. The US Census Bureau counts more than 30 million businesses with no staff. And the NBER study of AI at work found the least experienced workers gained the most from AI help, up to 34% more per hour.

The Leverage Stack chapters behind each row

This is the problem The Leverage Stack was written for.

The Conclusion: Don't Build the Whole Stack at Once is the 30-day order itself, with the 30-Day Rollout page. The Bottleneck covers days 1 to 3, the map of one ordinary day. The Inventory covers the four-way sort and the order that keeps you from speeding up waste. The Pipeline covers days 4 to 10, the five links that make one task start on its own.

The audit, the rollout and every other tool are in the free workbook. If you are not sure what to stop and what to hand off, start with automate, delegate or stop doing a task.