Stop retyping the same five emails every day

Almost everyone who writes email for work has five of them. The polite follow-up. The “here is the info you asked for”. The meeting confirmation. The gentle payment reminder. The “thanks, received, I will get back to you”. They change a name and a date each time, and the rest is muscle memory typed out in full, several times a day.

A text expander fixes this in an afternoon, but most snippet libraries die young for the same reason most to-do apps do: they get set up in a burst of enthusiasm and never match how you actually work. This is the workflow that avoids that, and it takes about an hour.

Step 1: Find your real five

Do not guess. Open your sent folder and scan the last two weeks. You are looking for emails where you recognize the shape before you read the words. Search helps: try your own most-typed phrases, things like “just following up”, “attached you will find”, “does that time work”.

Pick the five that appear most often. Not the longest ones, the most frequent ones. A two-line reply you send eight times a day saves more time than a page-long email you send monthly.

Step 2: Turn each one into a template

Paste a real example of each email into a snippet, then strip out everything that changes between sends:

• Names, dates and amounts become fill-in fields. In FillKit these are {curly} tokens that pop up a small form when the snippet expands, so you type just the parts that differ.
• Things your expander can compute stay automatic: {date} for today’s date, {clipboard} for whatever you just copied, which is perfect for pasting a link or an order number into a template.
• Your name, role and signature can come from a profile, so updating your job title once updates every snippet that mentions it.

Resist the urge to make one mega-template with ten optional fields. Two similar snippets beat one complicated one, because the point is to think less, not to fill in a form.

Step 3: Pick shortcuts you will remember under pressure

Shortcut design is what decides whether the library survives. A few rules that hold up:

• One prefix for everything. Start every shortcut with the same character, like ;, so triggers never fire while you write normal prose.
• Name by situation, not by content. ;followup, ;confirm, ;received, ;invoice. Six months from now you will remember the situation, not the wording.
• Keep them short but readable. ;fu saves keystrokes over ;followup and costs you a confused pause every time. The pause is more expensive.

Step 4: Use them for a week before adding more

Install the five, then stop. For one week, every time you catch yourself typing a known email by hand, use the shortcut instead, and every time you write something repetitive that is not covered, add it to a note. At the end of the week, promote the two or three most frequent notes to snippets.

This sounds slow. It is the opposite: libraries built five snippets at a time get used, libraries imported fifty at a time get abandoned. The habit is the asset; the snippets are just its storage format.

The math, since you are wondering

Say your five emails average 60 seconds of typing and you send them ten times a day between them. That is ten minutes a day, or roughly 40 hours a year of retyping the same sentences. An hour of setup against a work week of typing is the rare productivity claim that survives arithmetic.

If you do not have an expander yet, FillKit is ours: it lives in the Chrome side panel, needs no account, and keeps your snippets in your browser. The workflow above works the same in any of them.