Use cases/Indie hackers
For indie hackers who ship at night

The email client for indie hackers running three side projects from one Mac.

Day job inbox. Three product support addresses. A personal Gmail and a dormant iCloud. STAMP collapses them all into one calm queue and tells you which seven matter.

On-device triage. Reply from the right product domain automatically. Stop opening five Gmail tabs.

No credit card · macOS · 28-second setup

STAMP triage view tailored to indie hackers

The honest version

Three problems specific to indie hackers.

  • Your day job inbox and your support@ shouldn't share a queue.

    The customer who needs a refund deserves a faster reply than the all-hands invite. The all-hands invite shouldn't even be in the same view.

  • Five Gmail tabs is a lifestyle. You should not have a lifestyle.

    Browser tab clutter is the indie tax. STAMP replaces it with one keystroke that flips between accounts.

  • Support quality decays without triage.

    First-time customer questions get the same urgency as a churn risk. STAMP separates them automatically.

How STAMP solves it

Three features. Mapped to your day.

STAMP didn't ship 47 features. The six it did ship cover this whole problem, from triage to send.

Unified

Every product. Every account. One window.

Connect day job Workspace, support@product1, hello@product2, and your personal Gmail. STAMP gives you one keystroke between them.

Triage

Customer threads always rank above newsletters.

STAMP knows that a customer email to support@ is signal and the digest from your hosting provider isn't. The rank is automatic and editable.

Aliases

Reply from the product the customer wrote to.

Customer emailed support@product1? Your reply leaves from support@product1. No 'wait, why did this come from your Gmail' moments.

Indie hacking is an inbox problem before it's a product problem

Most indie hackers don't fail because the product is bad. They fail because the second product steals attention from the first one, and email is where that theft happens. The day job inbox is loud. The support email for product one is loud. The hello@ for product two is loud. By 11 a.m. you've answered everything except the question that mattered.

STAMP solves the attention problem at the inbox level. The home view is the seven threads that need you today across every account you own. The day job all-hands invite gets ranked below the customer churn signal. The newsletter from your competitor goes to the secondary view. The thread you can't deal with until tonight gets snoozed to tonight.

Indie hackers are the people who feel the cost of email volume most acutely because they have the least slack. STAMP buys back the slack.

How indie hackers use STAMP

Morning. Day job. Open STAMP, headline says four threads need attention — two from the day job, two from a product customer. You handle them in twelve minutes from the keyboard. The reply to the customer goes out from support@product1, not your personal Gmail.

Lunch. Side project hour. You hit ⌘+K, jump to the product two view, and triage the three customer questions sitting there. Snooze one to tomorrow morning, reply to two now. Both replies leave from hello@product2.

Evening. STAMP shows the recap: every customer touched today, every commitment made. You copy the support delta into your weekly metrics doc and close the laptop.

Weekend. The day job inbox is silent. You spend the day on product two without the day job all-hands invite breaking your concentration.

Indie defaults that compound

Per-product VIP rules. Tag your top customer once and they bubble up forever, across every product they email. The relationship survives even if they switch addresses.

Product-aware reply alias. STAMP detects the originating product domain and replies from it. The cognitive load of 'which product is this support thread for' goes to zero.

Snooze that survives weekends. Snooze to 'next working morning' lands at Monday 9 a.m., not Saturday 7 a.m. because the math says so.

On-device triage. The product roadmap your customers email you about doesn't get used to train a foundation model. Classification runs on your Mac.

I run two SaaS products and a day job from one mailbox now. STAMP is the only piece of software I'd email-bomb my friends about.

Early access user · Indie founder, two products

FAQ

Three questions you'd ask first.

Will my day job IT department let me connect their Workspace?+

STAMP uses standard OAuth. From the IT department's perspective, it's a connected mail client like any other. Many users connect day-job Workspace alongside personal accounts without issues. Check your company policy first.

Can I keep day job and product mail visually separate?+

Yes. Each connected account has a colour and a one-letter monogram. You can also pin a view that shows only one account or one product. Switching is one keystroke.

Is there a CLI for support automation?+

Not yet. The current keyboard surface lets you write canned replies and reach inbox zero from the keyboard alone, which is enough for most indie hackers. A scripting API is on the roadmap.

One last thing

Tomorrow's inbox is going to look exactly like today's.
Unless you change the tool.

Get early access, free

macOS · 28-second setup · No credit card