Published October 19, 2026
How founders manage email with an assistant and a clear delegation workflow
Founders get email from every direction at once: customers, investors, candidates, partners, vendors, lawyers and the team. Past a certain point, reading it all yourself stops being diligence and starts being a bottleneck. The founders who keep email under control rarely do it by working faster. They do it by deciding which emails only they can answer, and by building a simple workflow so an assistant handles everything else. This guide explains how founders manage email with an assistant, from the first day of delegation to a routine that runs without daily supervision.
Signs it is time to delegate your inbox
Delegation feels like a big step, so many founders wait too long. These signals usually mean the inbox is costing more than an assistant's time.
- You spend more than an hour a day in email and still end the day with unread messages.
- Customers or candidates wait days for answers that someone else could have given.
- You find important threads a week late, buried under notifications and pitches.
- You reply from your phone at night because the day was full of meetings.
- Scheduling, invoices and vendor questions take more of your email time than strategic decisions.
If two or more of these sound familiar, the question is not whether to delegate, but how to do it safely.
Decide what only you should answer
The core of the workflow is a short written list that splits email into three groups. Write it down and share it with your assistant on day one. It is the single most useful document in the whole setup.
Founder only
Investor updates and questions, board matters, key hires, major customers at risk, legal and anything emotionally sensitive for the team. Your assistant reads these, summarizes them and flags them, but does not draft a substantive answer without your input.
Assistant drafts, founder approves
Customer follow-ups, partner introductions, candidate scheduling with context, replies to advisors and answers to known questions. Your assistant prepares a draft, and you approve or edit it in seconds.
Assistant handles fully
Meeting scheduling, receipts, vendor invoices, tool notifications, event invitations, cold pitches and routine requests with standard answers. These never need you, and seeing them only costs attention.
Set up access the safe way
Never share your password with an assistant. Gmail and Google Workspace support mail delegation, and Microsoft 365 supports delegate access and shared mailbox permissions. Both let another person read and draft in your mailbox under their own login, and both let you remove that access at any time. Decide up front whether your assistant can send on your behalf or only draft. Many founders start with drafting only, and allow sending for a narrow list of routine replies after a few weeks of trust.
- Use delegation or delegate access, not a shared password.
- Keep two step verification on your own account.
- Agree on a signature that makes clear when your assistant writes as themselves.
- Review access every quarter, and remove it the same day someone leaves.
A label system you both understand
Delegation fails when the founder and the assistant cannot see each other's decisions. A shared label system solves that. Keep it small and use the same names in Gmail and Outlook if you work in both.
| Label | Meaning |
|---|---|
| For you | Founder only, with a short summary from the assistant |
| Approve | Draft ready in Drafts, waiting for your OK |
| Waiting | Reply sent, waiting on the other side |
| Scheduled | Meeting handled, calendar updated |
| Done | Handled fully by the assistant, for your record |
The founder works almost entirely from For you and Approve. Everything else is visible but does not ask for attention.
The daily rhythm for founder and assistant
A predictable rhythm turns delegation from constant messages into two short check ins. The plan below fits a founder who spends most of the day in meetings.
| Time | What happens |
|---|---|
| Early morning | Assistant sorts overnight mail, drafts replies and writes a short summary |
| Morning, 15 minutes | Founder reviews For you and approves drafts in Approve |
| Midday | Assistant sends approved replies and handles new routine mail |
| Late afternoon, 10 minutes | Founder clears new items in For you and Approve |
| End of day | Assistant updates Waiting and lists open threads for tomorrow |
Keep urgent issues out of email. Agree that anything truly urgent goes to a phone call or a direct message, so neither of you has to watch the inbox all day.
Teach your assistant to write like you
The biggest fear founders have about delegation is that replies will not sound like them. Fix it with a short voice guide. Collect ten of your own sent emails that you like and share them as a reference. Write down a few rules: how you open and close emails, whether you use first names, how long your replies usually are, and words you never use. Ask your assistant to keep drafts shorter than they think is polite. Founders almost always prefer brief replies that decide something to long ones that explain everything.
Two messages that make the handover smooth
When your assistant starts writing on your behalf, it helps to tell regular contacts once, so nobody is surprised. These two templates keep it short.
Subject line, Introducing [assistant name], who helps with my calendar and email
Hi [first name],
I want to introduce [assistant name], who now helps me with scheduling and email. You can reach [assistant name] directly at [assistant email] for meetings and logistics. For anything about [topic only you handle], I will still reply personally.
Best,
[your name]
Subject line, Re: [original subject]
Hi [first name],
I help [founder name] with email and scheduling. [Founder name] would be glad to meet, and I have proposed two times below. If neither works, send me a few options and I will confirm.
[time option one]
[time option two]
Thanks,
[assistant name]
The first month of delegation, week by week
Trust builds in steps. A gradual handover lets your assistant learn your priorities without risking an important relationship on day one.
| Week | What to hand over |
|---|---|
| Week 1 | Assistant reads and labels only, founder still replies to everything |
| Week 2 | Assistant handles scheduling, receipts and notifications fully |
| Week 3 | Assistant drafts replies for the Approve label, founder edits and approves |
| Week 4 | Founder reviews only For you and Approve, assistant runs the rest |
At the end of the month, spend thirty minutes together reviewing the drafts you changed most. The pattern in your edits is the best possible update to the voice guide, and it usually shows two or three simple rules your assistant can apply from then on.
Ask for summaries, not forwards
A forwarded email chain with "see below" pushes the reading work back to you. Ask your assistant to send the opposite: a short summary at the top of anything in For you. Three lines are usually enough. What happened, what the other side is asking for, and by when. Add a suggested answer if your assistant has one. With that format, most founder only emails take a minute to decide instead of ten minutes to read, and the full thread is still there if you need the detail.
Mistakes to avoid when you delegate email
Most delegation problems come from unclear rules, not from the assistant. Watch for these.
- No written list of founder only topics, so the assistant guesses.
- Reviewing every routine email anyway, which doubles the work instead of halving it.
- Letting drafts sit in Approve for days, which blocks the assistant and the other side.
- Mixing personal and company mail in the same delegated mailbox without clear rules.
- Never giving feedback. A two line note on why you edited a draft improves every future draft.