Founders do not have email problems. Founders have decision-making problems that show up in email.
Every thread in a founder's inbox is a request for a decision: hire, fire, fund, refuse, sign, decline. The volume is not the problem. The cognitive cost of context-switching between high-stakes decisions, hundreds of times a day, is the problem.
Here is the triage system we have seen work for three founders across nine startups. Adapted to use STAMP, but the principles work without it.
The four queues
Most founders run their email as one queue. Wrong. There are four queues, and they need separate treatment.
Queue 1: Investors and capital.
The thread that becomes a wire transfer. Always urgent. Always reply within 2 hours during business days.
Queue 2: Customers and prospects.
Revenue is on the line. Reply within the day. Treat the third follow-up like a fire.
Queue 3: Team and internal.
Async-by-default. 24-hour reply window is fine for most.
Queue 4: Vendors, recruiters, FYIs, and noise.
Reply only if asked a question that has not been asked elsewhere. Most can be archived.
If you mix these into one queue, every thread asks for the same level of attention. Your accountant looks identical to your largest customer. By 11 a.m., you are spent.
The 7-email rule, applied
The 7-email rule says you can give thoughtful attention to about seven threads a day. For a founder, the breakdown looks roughly like:
- 2 from Queue 1 (investors, capital).
- 3 from Queue 2 (customers, prospects).
- 2 from Queue 3 (team).
- 0 from Queue 4 (everything else).
If your day looks like 5 from Queue 4 and 2 from Queue 1, your week is going badly. The triage system is a way to make sure the right queue is getting the attention.
The morning ritual
This is the actual sequence we recommend. About 12 minutes a day.
Step 1 (90 seconds). Open inbox. Identify the two Queue-1 threads. Reply or snooze with note. Do not let an investor wait.
Step 2 (3 minutes). Identify the three Queue-2 threads. Reply with sentence-level answers. Long answers go to a 30-minute slot later.
Step 3 (4 minutes). Identify the two Queue-3 threads. Reply, decide, or delegate.
Step 4 (3 minutes). Triage Queue 4. Most of it is archived. The rest is snoozed to a Friday batch.
Step 5 (90 seconds). Close the laptop. The inbox is at zero. The day starts with focus, not with reaction.
What goes wrong
Three failure modes we see in founders.
One: the dopamine slide. You start with Queue 4 because the easy emails feel productive. By the time you get to Queue 1, you are tired. Investor reply is rushed. Customer reply gets skipped.
Fix: do Queue 1 first. Always. Even on a Friday afternoon when you do not feel like it.
Two: the inbox-as-task-list. You leave Queue-2 threads in the inbox “so you remember.” The inbox grows. By Wednesday you cannot find the actual urgent ones.
Fix: snooze with note. The thread leaves the inbox, comes back at the time you decide, with the context you wrote down.
Three: the meta-email loop. You spend 40 minutes scheduling a 30-minute meeting. Six emails about the calendar invite.
Fix: send your calendar link in the first reply. Stop discussing times in email.
What VIPs are for
Every founder has 8 to 15 people whose emails you want to never miss. Investors, board members, top-five customers, founder peers. Tag them as VIP in your client.
In STAMP, VIP threads always surface in the headline regardless of other classification. They never sit unseen. The cost of a missed VIP email is asymmetric: most are fine if you are slow, but the one that is not fine, costs you.
Asymmetric stakes deserve asymmetric attention.
How to handle “quick question” from the team
Internal email from your team is the trap most founders fall into. The volume is high. Each one feels small. Five quick questions a day is 25 minutes.
Three rules.
One: push to async docs. A team using Notion, Linear, or shared docs should ask 80 percent of their questions there, not in email. Reduce the channel.
Two: time-box. A team email gets a one-sentence reply in under 90 seconds. Anything longer is a meeting or a doc.
Three: empower. Most “quick questions” from the team are decisions you have already made and they need confirmation. Build a pattern where they make the call and CC you, not where they ask permission.
The recurring weekly review
Friday afternoon, 25 minutes. The review.
- Read the three Queue-1 threads of the week. Synthesize what investors are saying.
- Read the three biggest Queue-2 threads. Note any pattern (feature requests, complaints).
- Review snoozed threads. Anything snoozed twice gets dealt with now.
- Archive what is left.
This is the closing ritual. It catches what the daily triage missed. It also sets up the following week.
A typical founder day with STAMP
Real example, lightly anonymized. Founder, B2B SaaS, $4M ARR, 14 employees.
8:42 a.m. Coffee. Open STAMP. Headline: “Working late, James. 5 need attention.”
- Top: lead VC partner, contract amendment, tagged Reply needed VIP. Reply with a sentence and a link to the doc. 90 seconds.
- Next: largest customer, frustrated, third follow-up. Reply. Apologize. Schedule a call. 3 minutes.
- Next: Head of Sales, internal, tagged Reply needed. Decision delegated. 30 seconds.
- Next: investor intro. Reply with a Calendly link. 30 seconds.
- Next: contract from a partner. Snoozed to 2 p.m. with note “sign after lunch.”
11 minutes. Inbox at zero. The 47 newsletters and CC chains are quietly out of sight. James goes to a board prep doc.
What we built for founders specifically
STAMP ships three founder-specific behaviors:
- Investor tag with hysteresis. Once a sender is tagged as an investor, the tag persists across email-thread breaks. Investor replies do not get demoted to FYI by a quiet thread.
- Customer escalation detection. Sentiment shift in a customer thread (a polite first email becoming a frustrated third) triggers a Frustrated tag automatically.
- VIP override. Marking a thread VIP applies to the whole thread, future replies, and any forward chain.
These are small. They cost a lot to build. They save you from missing the ones that matter most.
Where to go from here
For the broader system, the 7-email rule and how to actually reach inbox zero. For the operator equivalent, how operators handle 300 emails a day.
The triage layer founders need. hello@stamp.email