What Should a Founder Delegate First?

Most founders delay delegating because they’re not sure where to start, and “everything” feels like too big an answer to act on.
Here’s a simpler way to think about it.
Start with the two-question test.
For any task on your plate, ask: does this require my specific judgment or relationships? And, would I be embarrassed if someone found out I was still doing this myself?
If the answer to the first is no and the second is yes, that’s your starting list.
For most founders, that list looks something like this:
Inbox triage.
Not every email needs your eyes.
Someone can sort, flag, and draft responses so you’re only touching what actually requires you.
Calendar management.
You shouldn’t be the one accepting or declining meeting invites.
That decision belongs to whoever’s protecting your priorities.
Travel and logistics.
Booking flights, hotels, ground transport — this is pure task work with zero strategic value in you doing it personally.
Research and first drafts.
Vendor comparisons, first-pass proposals, meeting prep docs.
Someone else can get it to 80%, and you finish the last 20% with your judgment.
Recurring admin.
Expense reports, scheduling recurring check-ins, chasing signatures — the stuff that’s not hard, just constant.
What you should NOT delegate first — the things that still need to sit with you a bit longer, at least early on: anything involving a decision only you have context for, sensitive people conversations, and the relationships you’re personally responsible for building.
The mistake most founders make isn’t delegating too little — it’s trying to delegate the wrong things first, get burned by a bad handoff, and conclude “delegation doesn’t work for me.”
It wasn’t the wrong move.
It was the wrong starting point.
Want a second opinion on your list?
We help founders build their first delegation map in one call.












