What Is The Waiting Tax?

The waiting tax is the bill you pay every day you postpone moving on AI. It is not a metaphor for being behind. You are not behind. You are waiting: for proof, for a competitor to go first, for the tool that finally works out of the box, for the quarter when things calm down. Each of those waits has a sentence attached to it, and each sentence costs you real weeks while a leaner team quietly does the work you keep meaning to do.

Where the name comes from

I coach $1-50M founders. Over fifty-plus hours of real calls, the same thing kept happening. An owner would describe a process an agent could clearly run, I would ask what was stopping them, and the answer was never technical. It was a sentence. A reasonable-sounding, grown-up sentence that ended the conversation and kept the status quo in place.

I started writing the sentences down. There turned out to be fourteen, and nearly every stalled founder was running two or three at once. The waiting tax is what those sentences cost. Not "falling behind," which is vague and lets you off the hook. A bill. Payable weekly. Charged whether or not you notice it.

The fourteen sentences

Read them as diagnostics, not accusations.

1. "I'll wait until somebody proves it works." You do not believe it is capable, so you want someone else to take the risk.
2. "Everyone else is already ahead of me, I'll catch up later." Waiting for somebody else to go first, dressed up as patience.
3. "I tried AI. It gave me junk. It's not there yet." You judged the whole category on an out-of-the-box result with no setup.
4. "I'm not really a tech person." An identity statement doing the job of a decision.
5. "I'll get to it once I've watched a few more videos." Consuming instead of creating.
6. "It works for Brad. I'll be the one who breaks it." Pre-deciding your own failure.
7. "My gut knows which idea will win." Refusing a cheap test in favor of an expensive opinion.
8. "I don't want that live on the internet." Shipped means judged, so nothing ships.
9. "I'll plan this out for the quarter first." A planning cycle standing in for a first move.
10. "I'll lose three days if I open that box." The time-suck fear, usually a fear of not knowing where to start.
11. "One more SaaS will finally do it." The tool-shopping loop.
12. "Nothing moves without my say-so." The approval gate that makes you the bottleneck on your own progress.
13. "I'll be the one who breaks something." Treating a reversible experiment like an irreversible one.
14. "They'll know it's AI." The detection fear, which assumes your customers care more about the tool than the result.

Every one is a sentence I have heard from a real founder mid-stall. None is stupid. That is exactly why they work on you.

How the bill accrues

The tax is not charged in one lump. It accrues the way interest does, in small increments that are easy to ignore individually.

Start with the work that currently has no owner because the role is unfilled or the agent is undeployed. That work does not disappear. It lands on you, or on your best people, at the margin of their day. What an unfilled role actually costs you every week walks through how to put your own number on that, using your own inputs rather than anything I invent for you.

Then add the compounding you forfeit. The founder who started recording calls and building their first agent six months ago is not six months ahead of you. They are further ahead than that, because each small win made the next one cheaper. The founder who spent six months watching videos and evaluating tools has a bookmark folder. The decisions that compound sorts one kind of move from the other.

Then add the hidden cost of the sentences themselves. Each one trains your team. Say "nothing moves without my say-so" long enough and your team stops bringing you things that could move. The tax is partly cultural, and culture compounds too.

Why it is not a technology problem

The honest diagnosis from those coaching calls is uncomfortable: we are not blocked by tech, we are blocked by admin. When a team stalls, the proximate cause is very often that nobody has the login, the API key, or the permission to connect the tools that already exist. The first homework in the course is a fifteen-minute Access Audit for exactly that reason. It unblocks a surprising share of stalled teams before mindset even comes into play.

Once access is sorted, what remains is the fourteen sentences. Those are not fixed with a better tool. They are fixed with a reframe.

The reframe: borrow the confidence, earn the evidence

Here is the chicken-and-egg problem at the center of all fourteen sentences. You will not move without confidence that it works. You cannot get evidence that it works without moving. So the waiting founder sits at the intersection, waiting for evidence to arrive from somewhere else, which it never does in a form specific enough to act on.

The way out is to borrow the confidence. Not blind faith. I have receipts. But the confidence I hand you is a loan, not a gift. You use it for a week to ship the smallest honest bet: one agent on one repeatable task, one page live by Friday. Then you look at what happened. Now the evidence is yours, specific to your business, which is the only kind that ever actually moves an owner.

Confidence I hand you. Evidence you earn back. That is the whole loop.

What to do this week

• Write down which of the fourteen sentences you have said out loud in the last month. Be honest.
• Run the Access Audit: list the accounts, access, and permissions your team would need to connect one agent to one real workflow. Fix what is missing. Fifteen minutes.
• Pick the smallest bet that produces a result you can look at by the end of the week. Not the most important project. The smallest honest one.
• Decide in advance what "it worked" looks like, so the result cannot be argued away afterward.

If you want the fourteen reframes in order, with the belief under each sentence and one concrete first move for each, that is the free course: fourteen lessons, five to seven minutes each, inside Optimus.University. If you are weighing a seat you keep not filling, the honest math of hiring now versus waiting is the next thing to read.

FAQ

Is the waiting tax a real cost or just a way of talking about procrastination?

It is a real cost, it is just not itemized on any invoice. The work that has no owner lands on you or your best people. The compounding you would have earned from an early start does not accrue. And the sentences you repeat train your team to wait too. None of that shows up as a line item, which is exactly why it goes unpaid attention to for years.

Which of the fourteen sentences is the most expensive?

The one you are currently saying. Seriously. They are all expensive in the same way: each one stops a small reversible experiment from happening, and the experiment is where the evidence comes from. If I had to pick, the tool-shopping loop and the planning-for-a-quarter block waste the most calendar time because they feel so much like progress.

Do I need to be technical to stop paying it?

No. The Access Audit is admin, not engineering: accounts, logins, permissions. The first agent you deploy should be on a task you already understand completely, so the only new thing is the tool. Every founder I have watched get unstuck did it by shipping something small, not by learning to code.

How is this different from just telling me to take action?

Telling you to take action ignores why you have not. The waiting tax names the specific belief under each delay, gives you a reframe for it, and prescribes one concrete first move. The point is not motivation. The point is that confidence has to come from somewhere before the evidence exists, so you borrow it for a week and then earn your own.