If you have answered the same question three times this month, you are going to answer it a fourth time. The only decision left is whether that fourth answer takes you two minutes of retyping or ten seconds of pasting.
Templates and snippets are the least glamorous productivity habit in email, and also one of the highest return. Here is how to build a library that actually gets used.
The difference between a template and a snippet
They solve different problems, and conflating them is why most people's template folders die within a month.
A snippet is a small, reusable fragment: a paragraph, a sentence, a link with context. You insert it into an otherwise personal reply. “Here is our onboarding doc: [link]. Let me know if anything is unclear.” You still write the greeting, the specific context, the sign-off, yourself.
A template is a full email shell: subject line, structure, and most of the body, with blanks for the specific details. A meeting reschedule request. A pricing follow-up. An invoice reminder. You fill in a name and a date and send.
Snippets keep replies feeling personal while cutting typing time. Templates are for genuinely repeated, structurally identical situations. Using a template where a snippet would do makes your replies feel canned. Using a snippet where you actually need a template means retyping the same structure by hand every time.
When to templatize
Ask three questions about a recurring email.
- Does the structure repeat, not just the topic? “People ask about pricing” is a topic. “People ask the exact same three pricing questions in the exact same order” is a structure. Only the second is worth a template.
- Does personalization actually change the outcome? If a slightly generic version works fine (a shipping delay notice, a meeting confirmation), templatize fully. If the recipient would notice and care about a canned reply (a client complaint, a sales objection), keep it a snippet plus your own framing.
- Have you answered this more than twice? Once is a coincidence. Twice might be. Three times is a pattern worth a template.
Building the library
Start smaller than you think. Five snippets and two templates cover most people's repeated traffic in the first pass.
- Audit a week of sent mail. Look for replies that are 80 percent identical to something you sent before. That 80 percent is your snippet.
- Write the snippet as a fragment, not a full email. No greeting, no sign-off. Those stay personal every time.
- Name templates by the situation, not the content. “Reschedule request” is a better name than “Meeting email 2,” because you search by situation under time pressure, not by remembering exact wording.
- Review the library monthly. Delete anything you have not used in a month. A stale template library is worse than none, because you waste time scanning options that no longer apply.
Where templates hurt more than they help
Two failure modes worth naming.
The over-templated apology. A frustrated customer can tell when they are getting a form response, and it makes the frustration worse, not better. Anything involving an upset person, a mistake on your side, or a negotiation should start from a snippet at most, never a full template.
The stale template. Pricing changes, product names change, your team changes. A template that quotes last year's price and gets sent unread is worse than typing it fresh. If you templatize anything with numbers or names that change, put a visible placeholder ([CURRENT PRICE]) that forces you to check before sending, not a number you might forget to update.
How STAMP fits in
STAMP surfaces snippets inline as you type, matched against the thread's content, so you are not digging through a separate app or a notes file to find the fragment you need. Because classification runs on-device, matching a snippet to “this looks like a pricing question” happens instantly and privately, without your draft or the thread content leaving your machine.
Cmd+K also jumps you straight to a saved snippet or template by name, which matters more than it sounds: a library you cannot search fast enough under real time pressure gets abandoned within a week, however good the content in it is.
What to try this week
Pull up your last 20 sent emails. Flag anything you have written something close to before. Turn the three most common into snippets, and if you find a full recurring structure, build one template. Use them for a week and see how much retyping disappears.
Write it once, use it forever. hello@stamp.email