What Does a Stalled Backlog Actually Cost a Founder?

A stalled backlog costs you on three layers: the founder-hours it would eat if you ever did it yourself, the monthly returns of every shipped-someday improvement you're not collecting, and — the expensive one — the systems that never get built because execution is priced in your hours. None of it shows up on a P&L, which is exactly why it survives.

Every number below is illustrative math on stated assumptions — not a study, not a benchmark. The point is the structure of the calculation. Swap in your own numbers; the shape of the answer won't change, but the size might scare you.

Layer 1: What is your hour actually worth?

Start with the shorthand every owner should keep loaded: effective hourly value = target owner earnings ÷ ~2,000 working hours a year.

Say you're running a $10M company and your target owner earnings are $1M a year. That's $500/hour. Now look at the backlog honestly: suppose it holds 20 items averaging 3 hours of your focused work each. That's 60 founder-hours — $30,000 of your labor, parked. Do those hours yourself and you didn't save $30K; you spent it on work a machine or a hire could do, at the exact hours your business needed an architect.

That's the visible layer, and it's the smallest one.

Layer 2: What does deferral cost while you wait?

Backlog items aren't chores — most of them are improvements with a return attached. A cleaned-up CRM that stops leads leaking. A follow-up sequence that actually fires. A weekly report that catches a margin problem in week one instead of quarter three. Improvements compound from the day they ship. Every month an item sits in the backlog is a month of its return you never collect — and never compound.

Illustrative math again, stated plainly: say just five of your 20 items would each produce a modest $1,000/month once shipped — a recovered lead here, a saved team-hour-per-day there. Stalled for a year, that's $60,000 of foregone return — double the labor cost of the entire pile, and it re-bills every year the backlog stays stalled. Run your own version: for each item, ask "what does this make or save per month once it exists?" and multiply by the months it's been sitting. That number is the carry cost of "someday."

Layer 3: What never gets built at all?

The costliest layer never even makes the list. When execution is priced in founder-hours, you pre-filter your own ambition: ideas that would obviously take ten hours of your time don't get written down, because you already know the answer. The backlog you can see is the survivor of that filter. The backlog you can't see — the tooling, the experiments, the systems a $50M version of your company runs on — died at the whiteboard.

This is the hell scenario, and it's quiet: nothing breaks, nothing fails, you just stay the size that fits inside your own calendar while a competitor who solved execution keeps shipping. The cost of layer three is the gap between the company you have and the one you'd build if execution were nearly free.

What are the standard fixes, and what do they cost?

• Do it yourself. Costs $500/hour of architect time (your number may vary) plus the strategy work those hours displace. This is the most expensive labor in your company doing its cheapest work.
• Hire for it. Right answer for judgment-heavy work. But for labor-shaped backlog items, a real hire means salary, ramp, and management overhead — a five-figure monthly commitment before item one clears, and now the backlog has a headcount attached.
• Chatbot-assist it. Cuts the hours but keeps them yours. A 3-hour item becomes a 1-hour item that still loses the calendar fight. (Why that is: chatbot vs. agent.)
• Hand it to a background agent. Your cost per item collapses to the brief and the report review — minutes of architect time instead of hours of labor. The work runs on the agent's compute, not your calendar.

How does the math change with a background agent?

Structurally, not incrementally. Harry — the Optimus background worker — takes the job, runs PLAN → EXECUTE → TROUBLESHOOT → HEAL → REPORT on his own machine, and messages you when it's done. Your 60 parked founder-hours become roughly 20 briefs and 20 report reads. Layer 1 stops billing you. Layer 2 starts collecting — every shipped improvement's monthly return turns on and compounds. And layer 3 quietly reverses: when execution stops costing your hours, the ideas you used to suppress start making the list. (The working method is in how to clear your "someday" backlog.)

Because Harry heals workflows as he goes, recurring jobs get cheaper still — each failure fixed once stays fixed, so the maintenance tax that normally eats automation gains doesn't accrue.

Run the three layers on your own numbers before you decide anything. If the total is a rounding error, ignore all of this. For most $5–50M owners it isn't — it's one of the larger unbilled line items in the company, and it renews annually. More on the operating philosophy behind that math at Make More Marbles.

FAQ

Isn't a deferred task free until I do it?

No — deferral has carry costs. Improvements compound from the day they ship, so every month an improvement sits in the backlog is a month of its returns you never collect and never compound. A quiet backlog isn't a free backlog.

How do I estimate what my own backlog costs?

Count the items, estimate hours each would take you, and multiply by your effective hourly value (a common shorthand: your target owner earnings divided by about 2,000 working hours a year). Then add the harder layer: for each item, what monthly return would it produce once shipped? Every stalled month burns that amount.

Why not just hire someone to clear the backlog?

You can, and for judgment-heavy work you should. But most backlog items are labor-shaped, not judgment-shaped, and a hire for them costs salary, ramp time, and management overhead — a real hire is a five-figure-a-month commitment before they clear item one. A background agent takes the same class of work without adding headcount.

Does an AI agent really change the math, or just move the work?

It changes the math structurally: the labor stops being priced in your hours. Your cost per item drops to briefing it and reading the report — minutes, not hours. Harry runs the job in the background on his own compute and messages you when it's done, so the backlog clears without competing for your calendar.