The delegation black hole
Every founder delegates constantly. “Can you handle the vendor proposal?” “Please send the updated deck by Friday.” “Loop in finance on the new pricing.” Dozens of these go out every week, in mail, in chat, and out loud after meetings.
Then they vanish into your sent folder. Unless you remember to check back, unless you keep a spreadsheet, those asks enter a black hole — and most of what you delegate needs at least one follow-up before it is actually done.
Try the test: without opening anything, list everything you delegated in the last seven days. Most founders can name four or five; the real number is several times that, and the gap is where work goes to die. If you cannot answer “did the ops lead finish the vendor review?” in ten seconds, you have a delegation habit with no accountability — and you are the bottleneck you cannot see.
Why spreadsheets and to-do apps fail
David Allen’s Getting Things Done gave us the waiting-for list: write down everything you are waiting on from other people, review it weekly, follow up. In theory, perfect. In practice, an executive who sends forty messages a day, a third of them containing an ask, would have to log a dozen new items daily. The overhead of maintaining the list eventually exceeds the cost of keeping it in your head, so you stop, and things slip.
Project tools are better, but they only capture what gets formally entered. Most founder delegation is informal — a quick email, a chat message, a verbal ask on the way out of a meeting — and that informal layer is where the bottlenecks form. The problem is not discipline. Tracking delegation is a clerical job nobody at the top has time for.
How PILOT tracks delegation
PILOT is a private AI chief of staff. It ingests your sent mail, Teams chat and transcripts, and voice notes into a private knowledge graph, and it tracks commitments in both directions — what others owe you, and what you owe them.
The ledger builds itself. Every ask gets a recipient, the substance, a detected deadline if there is one, and a clock. Identity resolution matches “Sarah” to the right Sarah and the ask to the project it belongs to.
Items close when the reply arrives. When someone answers, delivers the file, or confirms, the item resolves. A partial or ambiguous reply stays open, and PILOT tells you rather than closing it silently.
Stale items surface. A deadline is checked on the date. An ask with no movement for ten days or more is flagged under “Pilot noticed”. What is due or overdue lands in the 07:00 briefing — “You asked Marc for the vendor comparison four days ago; no reply yet” — capped at about seven items. You decide whether to nudge or let it ride.
Ask it anything. “What did I delegate last week?” “What is outstanding with each direct report before the one-to-ones?” “Did I already ask someone to handle this?” Answered in chat or by voice.
You send the follow-up. PILOT drafts it if you ask; it never sends. A human confirms every outbound write PILOT initiates.
The weekly review you actually do
Almost nobody does the Friday review. PILOT’s weekly review does the delegation half for you — how many asks went out, how many came back, how many are overdue — scored as part of your week out of ten. You scan the overdue items, send two follow-ups, and you are done in minutes rather than an hour of scrolling through sent mail.
The founders who scale delegate aggressively and follow up systematically. PILOT gives you the systematic half without the overhead: keep delegating at your natural pace, and nothing disappears.
Built by its founder and running on his own working life every day. Staff for one principal, not a team tool — your delegation ledger lives in your own private database schema, isolated by architecture, EU-hosted on Azure.
