The email client for consultants who bill the hour and lose two of them to email.
Four engagements. Three client domains. A personal account you check between calls. STAMP gives you the seven threads that matter and gets out of the way.
Reply from the right address every time. Snooze a deck question to Tuesday. Stop searching three mailboxes for one invoice.
No credit card · macOS · 28-second setup
The honest version
Three problems specific to consultants.
Your billable hours leak through your inbox.
Time spent searching, sorting, and apologising for late replies isn't billable. STAMP gives those hours back, and they compound.
Engagement-specific context lives in too many places.
The thread you need is in client B's domain, but you replied from your personal Gmail, and now the trail is broken. STAMP keeps the context where it should be: in the thread, in the right account.
Frustrated stakeholders rarely say so explicitly.
You learn about an unhappy client at the steering committee, not in the inbox. STAMP flags tone shifts before they become escalations.
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.
Per-engagement tags, learned automatically.
Tag a sender once with a client name and STAMP applies it to the engagement going forward. The view by client is one keystroke away.
Reply from the right address, every time.
Connect every domain you bill from. STAMP detects the originating account and replies from it. The cognitive overhead of 'which account am I in' goes to zero.
Frustrated tag before the steering committee.
Tone shifts in stakeholder threads get flagged. You see the friction the day it shows up, not the day it becomes a meeting.
Email is the consultant's pricing problem
Consulting work is sold in hours and outcomes. Time spent in the inbox is, almost always, neither. The thirty minutes a day you spend searching across mailboxes, replying from the wrong account, and re-reading threads you've already read is unbillable, and it adds up to a working week per quarter.
STAMP is built for the kind of person who has four engagements running concurrently. Each one has its own domain, its own steering committee, its own deck cadence. The inbox is the connective tissue, and most clients can't handle it gracefully.
The triage layer handles the priority question — which seven of these forty-seven threads do I have to handle today? The unified layer handles the account question — which engagement does this thread belong to, and which alias do I reply from?
A consulting week, with STAMP
Monday 8:42 a.m. The week opens with a headline: 'Six need attention. Two are from your B engagement, one is the steering committee for A.' You handle the two from B in eleven minutes. The steering committee thread you snooze to 4 p.m. on Tuesday, after the prep session.
Tuesday 4 p.m. The snoozed thread surfaces with the original tag and your context. You reply from the right alias. The chair of the steering committee never knows you nearly forgot.
Wednesday morning. STAMP flags a Frustrated tag on a stakeholder you haven't heard from in three weeks. Tone has shifted across two replies. You add a 30-minute call to the day. You save the engagement before it becomes a re-scope discussion.
Friday end-of-day. STAMP's recap shows every commitment made and not-made by email this week. You forward it to the engagement manager. Done.
Defaults consultants like immediately
Per-engagement billing tags. Tag a thread Billable and STAMP starts a soft timer. Reply, hand off, and the thread closes with a time estimate you can paste straight into your timesheet.
Snooze that respects calendar context. Snooze to 'after the steering committee' uses your calendar, not a fixed clock. The thread comes back when you said it should.
Recap reports that read like a status update, not a Gmail digest. Send to your engagement manager weekly. They love them.
On-device triage. NDAs survive. Your client's strategy doesn't get used to train an LLM. The classifier runs on your Mac.
“I bill in 15-minute increments. STAMP gave me back eight increments a day. The maths takes care of itself.”
Early access user · Strategy consultant
FAQ
Three questions you'd ask first.
I work under multiple NDAs. Is on-device classification enough?+
Yes. Triage runs locally on your Mac. The threads, the metadata, and the body are never shipped to a third-party server for sorting. STAMP does not train models on your inbox.
Can I bill time directly from STAMP?+
Soft timers attach to threads tagged Billable. You can export weekly summaries to CSV for your timesheet tool. A direct integration with Harvest is on the roadmap.
What about my dormant iCloud or my old freelancer Gmail?+
Connect them. They become part of the unified queue. Replies still go from the address they should. The cognitive overhead of 'which old account is this' disappears the day you set it up.
Keep reading
Related use cases
Agency owners
The email client for agency owners running fifteen client conversations at once.
Read moreFreelance designers
The email client for freelance designers who'd rather be drawing.
Read moreiCloud + Gmail
One inbox for iCloud Mail and Gmail.
Read moreInbox zero, real version
Inbox zero on macOS, without declaring email bankruptcy.
Read moreOne last thing
Tomorrow's inbox is going to look exactly like today's.
Unless you change the tool.
Get early access, freemacOS · 28-second setup · No credit card