If you are a one-person company in 2026, your inbox is your support desk, your sales pipeline, your billing department, your beta-tester chat, and your friends asking how launch is going. All in one place. All looking identical.
The fix is not a fancier tool. The fix is a tighter system.
The five lanes of an indie inbox
Every email an indie hacker gets falls into one of five lanes:
- Support. “Help, this is broken.”
- Sales. “Tell me more about your product.”
- Billing. Stripe, taxes, accountants.
- Beta and feedback. Users telling you what they think.
- Personal and life admin. Family, banking, the dentist.
Each lane has a different SLA. Treating them with the same urgency is what burns you out.
| Lane | Reply within | Time per reply | | --- | --- | --- | | Support | 24 hours | 3-8 minutes | | Sales | 4 hours during day | 5-15 minutes | | Billing | When asked | 1-2 minutes | | Beta and feedback | 48 hours | 2-3 minutes | | Personal | Same day-ish | 30-90 seconds |
If you cannot keep these lanes mentally separate, you spend 20 minutes on a customer support reply that should have been 4. You let a sales email rot for a week. You burn out.
The 60-minute daily cap
An indie hacker should spend, on average, 60 minutes a day on email. That is one focused hour, broken into two 30-minute slots, or three 20-minute slots. Not eight 90-second checks.
Three rules to make this work.
Rule 1: batch the lanes. Do all support in one slot. Do all sales in another. Do not jump lanes mid-slot. Context-switching across lanes costs you 25 percent of the time.
Rule 2: stop checking on phone. Phone email is a relapse trigger. You see a support ticket, you stress, you do not act, you carry the stress for two hours. Phone gets personal lane only.
Rule 3: snooze ruthlessly. Anything not in the current slot's lane gets snoozed to its lane's next slot.
The support workflow
Most indie hackers spend 60 percent of their email time on support. Three patterns to compress this.
Templates for the top 10 questions. Write 10 reusable replies for the questions you get every week. Use a shortcut tool (Alfred, Raycast, Text Replacements). Reduce a 6-minute reply to 90 seconds.
One-line acknowledgement plus a follow-up. “Thanks for the report. Looking now.” Sets expectation. Buys you time. Does not commit you to a fix.
Public docs as a reply. If a question hits the same answer twice, write a docs page. Next time, your reply is a one-line link.
After three months of this discipline, your support volume drops by half because the FAQ has caught the easy questions.
The sales workflow
Sales email for an indie hacker is a different beast. Two kinds: inbound prospects and cold outreach.
Inbound prospects are the easier kind. Reply within four hours. Three sentences. Short. Do not pitch in email. Move to a 15-minute call or a Loom.
Cold outreach to you is mostly noise. Two questions to ask:
- Do they know what you actually sell?
- Are they offering something specific or asking you to “hop on a call”?
If no on both, archive. If yes on either, give it 90 seconds and a courteous decline if not relevant.
What to do about feedback emails
Beta users will email you with thoughts. Some are gold. Some are noise. Same inbox.
A simple system:
- All beta emails get auto-tagged “Feedback” (in STAMP this happens automatically).
- Twice a week, sit with the feedback queue for 20 minutes.
- Reply to the gold ones. Archive the noise ones. Do not reply to noise out of guilt.
This is a place where indie hackers most often over-spend. You feel obligated to engage with everyone who tried your product. You do not have to. Pick the high-signal feedback and engage deeply with that.
The personal lane
Family, banking, the dentist. These should never be in the same view as a support ticket.
Two solutions.
Solution one (low-tech): check the personal email account on your phone, twice a day, briefly. Never on the laptop where work email lives.
Solution two (with STAMP): all accounts in one queue, but personal threads are auto-tagged “Personal” and live in their own filter. Your default view is “Work,” and you switch to “Personal” when you intend to.
Either works. The point is to never accidentally see your bank notifications while you are heads-down on a customer fire.
The Friday close
Indie hackers benefit hugely from a Friday email close. 25 minutes, end of week.
- Read your sent folder. Did you commit to anything you have not delivered?
- Read the Feedback tag. Anything you should turn into a roadmap item?
- Archive anything older than two weeks that you have not touched.
- Close the laptop. Weekend.
The close is not productivity theater. It is the thing that keeps you from carrying email anxiety into Saturday.
What STAMP ships for indie hackers
Three things specifically:
- Auto-detected lanes. Support, sales, billing, feedback, personal, all classified on-device.
- Stripe parsing. Stripe receipts and disputes get tagged correctly so they do not spam your urgent queue.
- Cold-outreach quarantine. Bulk cold pitches go to a separate queue.
All on $8/month, locked. We are biased about how much that matters for an indie running a $20K MRR business, but the math seems clean.
Where to go from here
For the broader system, the founder's email triage system. For the freelancer-specific version, the freelancer's guide to surviving 4 client inboxes.
Less email, more shipping. hello@stamp.email