How to Clear Your “Someday” Backlog With an AI Agent
The "someday" backlog never clears because clearing it means you sitting down and doing it yourself — and your hours already lost that fight to whatever's on fire this week. The fix isn't discipline; it's changing whose labor the backlog is priced in. Hand the items to a background agent one job a day, and the pile clears itself while you run the company.
Every founder past $5M has the list. The data cleanup that's been "next quarter" for four quarters. The competitive teardown you'd genuinely use. The internal tool that would save your team an hour a day. None of it is hard. All of it is hours — your hours — and that's exactly why it's still sitting there. Here's the method for feeding that list to Harry, the Optimus background worker, until it's gone.
Why doesn't the backlog ever clear on its own?
Be honest about the mechanism. Each item survived triage because it's worth doing but not worth more than what you're doing instead. That's not a moral failing — it's correct prioritization. The problem is structural: as long as the backlog is priced in founder-hours, "correct prioritization" and "never happens" are the same sentence.
So the unlock isn't a better task manager or a heroic weekend. It's severing the link between "this gets done" and "you do this." (If you want to feel the number, the math is in what a stalled backlog actually costs a founder — deferred items aren't free just because they're quiet.)
Step 1: Dump the whole list, no editing
Get every "someday" item out of your head, your notes app, and your guilt into one flat list. Don't pre-filter for "AI-suitable" — you'll filter wrong, because you're still pricing in your own hours. Fifteen minutes, everything on the table: reports, cleanups, migrations, research, tooling, content, the works.
Step 2: Sort by "definable done," not by importance
Now split the list with one test per item: can you write what "done" looks like in two sentences?
- Pass: "Every contact in the CRM has a verified email and owner assigned; dupes merged; report of what changed." → agent queue.
- Fail: "Rethink our positioning." That's not a task, it's a decision wearing a to-do's clothes. → stays with you (though the agent can prep the research that feeds it).
Most founders find the majority of the backlog passes. It was never strategy debt — it was labor debt.
Step 3: Hand off one job a day
Resist the urge to dump twenty items at once. The constraint isn't Harry's capacity — he runs on his own compute in the background, with zero babysitting. The constraint is your brief quality. One well-briefed job a day beats twenty vague ones, and it builds the delegation muscle: outcome, context, constraints, definition of done. (The full briefing method is in how to delegate work to an AI agent.)
One job a day is 20+ cleared items a month. Run that against how much backlog you cleared last year.
Step 4: Let the reports come to you
This is where the honey badger model differs from every tool that still needs your attention. You don't check on Harry. He runs PLAN → EXECUTE → TROUBLESHOOT → HEAL → REPORT and messages you when the work is ready — result in hand. If a job hits a wall that genuinely needs your judgment, you get "here's the exact next step," never a silent dead end. Your involvement per item drops to: brief it once, read the report, done.
Step 5: Re-queue the fallout, keep the decisions
Cleared backlogs breed new items — good ones. The CRM cleanup reveals a broken lead source; the teardown suggests a pricing experiment. Route the new tasks straight back into the queue. Route the new decisions to yourself. That division is the whole architecture: agents execute, the architect decides. Owners who run the Optimus crew do this triage from the portal, where Ollie keeps them in the know and dispatches the heavy lifting to Harry behind the scenes.
What changes after the first month
Two things, and the second one matters more.
First, the obvious: the pile shrinks. Items that aged for a year clear in a week, because the labor stopped being yours.
Second, the backlog changes character. When execution is cheap, you stop suppressing ambition to protect your calendar. Ideas you never even wrote down — because you knew you'd never get to them — start making the list, and then getting done. The backlog stops being a guilt ledger and becomes what it should have been all along: a queue of compounding improvements to your business, draining faster than it fills. And because Harry heals workflows as he goes, the system runs each recurring job cleaner than the last.
The old way: a backlog of "someday" tasks that never clears, because clearing it means you have to sit down and do it yourself. The Harry way: hand it over and forget it — the only time you hear about it is when it's done.
FAQ
Why doesn't my backlog ever clear on its own?
Because every item on it is priced in your hours. The backlog is the list of work that's worth doing but not worth more than whatever you're doing instead — so it loses the calendar fight every week, forever. It clears when the labor stops being yours.
How many backlog items should I hand to an agent at once?
Start with one a day. The constraint isn't the agent's capacity — it's the quality of your briefs and your willingness to review reports. One well-briefed job a day is 20+ cleared items a month, which is more backlog progress than most founders make in a year.
What backlog items should not go to an agent?
Items that are secretly decisions, not tasks — "figure out pricing" is a judgment call wearing a to-do's clothes. Delegate items with a definable outcome; keep the irreversible decisions and the strategy calls. The agent preps, the architect decides.
Do I need to watch the agent work through the backlog?
No. Harry runs in the background on his own machine and messages you when each job is done — result in hand, or the exact next step if something needs your call. The backlog clears itself in the background; the only time you hear from him is when it's done.