Your Inbox is Eating Six Hours a Week
You are probably not slow at email. You are probably rewriting the same four replies forty times a week.
Open your sent folder and scan the last two weeks. The pattern will show up fast. A pricing question. A scheduling reply. A status update. A polite decline. Maybe a version of “just checking in” or “here’s what happens next.”
Most people do not need a new inbox app, a paid automation tool, or a complicated AI workflow. They need four clear replies saved where they already write email.
The order matters:
Template first. AI second.
If AI writes from scratch every time, it has to guess your voice, your policy, your boundaries, and your level of warmth. That usually creates more editing, not less. If you start with a strong template, AI can do the small part it is actually good at: adjusting tone, adding context, and making the message feel personal.
Here are the four templates to build this afternoon.
Start by finding the emails you already write
Before writing anything new, go to your sent folder.
Search the last two weeks. Do not overthink it. You are looking for messages that have the same shape, even if the words change each time.
Common repeats include:
Pricing questions
Scheduling and rescheduling
Project or order status updates
Polite declines
Follow-ups after a call
“Here is the next step” messages
Answers to common onboarding questions
Copy four or five examples into a blank document. Remove names and private details. Then highlight what repeats.
You will usually find three layers:
The fixed part
This is the information that barely changes. Your pricing structure, process, policy, timeline, or boundary.
The flexible part
This changes based on the person. Their name, project, date, request, or situation.
The tone part
This is how you sound. Warm, direct, brief, detailed, calm, upbeat, or firm.
Most people jump straight to AI because they think they need help writing. The better move is to decide what should not change. That is what turns a one-time email into a template.
A good template does not sound robotic. It sounds like your best version of a reply on a day when you have enough time, sleep, and patience.
Template one answers pricing questions without starting from scratch
Pricing emails eat time because they feel delicate. You want to be helpful, but you do not want to overexplain, discount too early, or bury the next step.
A strong pricing template should do four things:
Acknowledge the request
Give the price or price range when appropriate
Explain what affects the final number
Point to the next step
Here is a simple framework.
```text
Subject: Pricing for [service/product/request]
Hi [Name],
Thanks for reaching out. Based on what you shared, [service/product] typically starts at [price or range].
The final price depends on [factor one], [factor two], and [factor three]. If it helps, most clients choose [common option or package] because it includes [short benefit or scope].
The next step is [call, form, estimate, proposal, link, reply with details]. If you send over [specific needed info], I can give you a more accurate recommendation.
Best,
[Your Name]
```
Here is what that looks like filled in:
```text
Subject: Pricing for your website update
Hi Maya,
Thanks for reaching out. Based on what you shared, a website refresh typically starts at $2,500.
The final price depends on how many pages need updates, whether the copy is ready, and how much design cleanup is involved. Most clients choose the standard refresh because it covers the main pages, mobile review, and a final round of edits.
The next step is to send over your current site, the pages you want updated, and any deadline you are working toward. From there, I can give you a more accurate recommendation.
Best,
Jordan
```
This template saves time because it keeps you from rebuilding the same explanation every time someone asks, “How much does it cost?”
It also protects your energy. You are not apologizing for your price. You are giving context and guiding the person forward.
Template two handles scheduling without turning into a thread
Scheduling replies become slow when every message tries to solve too many things at once.
The best scheduling template gives clear options and reduces the number of decisions. Do not write, “I’m flexible.” That sounds generous, but it makes the other person do the work.
Try this instead.
```text
Subject: Time to connect
Hi [Name],
Happy to connect. I have the following times available:
[Option one]
[Option two]
[Option three]
If one of those works, reply with your choice and I’ll send the invite. If not, send two or three times that are better for you and I’ll do my best to match one.
For the call, we can cover [topic one], [topic two], and [topic three]. It should take about [length of time].
Best,
[Your Name]
```
Filled in, it might sound like this:
```text
Subject: Time to connect
Hi Alex,
Happy to connect. I have the following times available:
Tuesday at 10:00 a.m. ET
Wednesday at 1:30 p.m. ET
Thursday at 3:00 p.m. ET
If one of those works, reply with your choice and I’ll send the invite. If not, send two or three times that are better for you and I’ll do my best to match one.
For the call, we can cover your current setup, what needs to change, and the best next step. It should take about 25 minutes.
Best,
Jordan
```
This template does more than save typing. It prevents the endless back-and-forth that comes from vague availability.
A few small rules help:
Offer three times, not ten
Include the time zone every time
Say who will send the invite
Name the purpose of the call
Set a rough length
That last one matters. A clear time box makes the invitation easier to accept.
Template three gives status updates before people ask
Status updates save time when they go out before someone has to chase you.
The goal is not to write a long report. The goal is to answer the questions people silently have:
Where are we?
What changed?
What is blocked?
What happens next?
Do you need anything from me?
Use this framework.
```text
Subject: Update on [project/order/request]
Hi [Name],
Quick update on [project/order/request].
Since the last update, [completed item or progress]. Right now, [current status].
The next step is [next action]. I expect that to happen by [date or time frame].
I need [specific item] from you before we can [next milestone]. If you have already sent that, no need to resend.
Best,
[Your Name]
```
Here is a finished version:
```text
Subject: Update on the fall campaign copy
Hi Melody,
Quick update on the fall campaign copy.
Since the last update, the first draft is complete and I’ve started reviewing the email sequence for consistency. Right now, I’m tightening the calls to action and checking the flow between messages.
The next step is to send you the full draft for review. I expect that to happen by Thursday afternoon.
I need the final offer details from you before we can move into revisions. If you have already sent that, no need to resend.
Best,
Jordan
```
This template works because it creates trust without adding noise. It is short, specific, and easy to scan.
It also cuts down on “just checking in” emails. Every status update you send early can prevent two or three follow-ups later.
Template four lets you decline without sounding cold
The polite decline is one of the most useful email templates you can write.
Without a template, declines often become too long. People explain too much, soften every sentence, or leave the door open when they really need to close it.
A good decline is kind, clear, and brief.
```text
Subject: Re: [original subject]
Hi [Name],
Thanks for thinking of me for this.
I’m going to pass because [short reason]. I do not think I’m the best fit for [specific need/request], and I would rather be clear than take this on and not serve it well.
If helpful, I’d suggest [alternate path, resource, or type of person to look for].
Thanks again for reaching out, and I hope it comes together smoothly.
Best,
[Your Name]
```
Here is a version for work you do not want to take:
```text
Subject: Re: Podcast editing support
Hi Chris,
Thanks for thinking of me for this.
I’m going to pass because ongoing podcast editing is outside the type of work I’m taking on right now. I do not think I’m the best fit for weekly production support, and I would rather be clear than take this on and not serve it well.
If helpful, I’d suggest looking for an editor who focuses specifically on recurring podcast production.
Thanks again for reaching out, and I hope it comes together smoothly.
Best,
Jordan
```
And here is one for a request you cannot fit into your calendar:
```text
Subject: Re: Workshop request
Hi Dana,
Thanks for reaching out. I appreciate the invitation.
I’m going to pass because I do not have the space to prepare and deliver this well by your deadline. I would rather be clear now than say yes and rush the work.
If the timing changes later in the year, feel free to check back in.
Thanks again, and I hope the event goes well.
Best,
Jordan
```
Notice what is missing. No long apology. No fake enthusiasm. No unclear “maybe.” The message is still respectful, but it does not create extra work.
That is the point of a decline template. It protects the relationship and the boundary at the same time.
Let AI personalize the template after you write it
Once the template exists, AI can help. Before that, it is guessing.
Use AI for the personalization pass, not the policy pass.
Here is the simple workflow:
Paste your template.
Add two lines of context.
Ask AI to adapt the tone without changing the meaning.
Use a prompt like this:
```text
Rewrite this email using the template below.
Keep the message clear, warm, and brief. Do not change the policy, price, deadline, or next step. Personalize it using the context provided.
Context:
[Add two or three details about the person, request, project, or tone.]
Template:
[Paste your template.]
```
For example:
```text
Context:
They are a past client and asked for help on short notice.
I want to be kind, but I cannot take the project this month.
Template:
[Paste polite decline template.]
```
This is where AI is useful. It can soften a sentence, add a warmer opening, or match the energy of the thread. It can help a pricing reply sound less stiff or make a status update more readable.
But it should not invent your process. It should not decide your price. It should not create a new boundary every time.
If you do it backward, you get a machine improvising your business voice from scratch. Then you spend ten minutes fixing tone, removing fluff, and checking whether it promised something you would never promise.
Template first. AI second.
That one rule keeps the time savings real.
Save the templates where you already write
Do not make this project bigger than it is.
You can save templates in almost any email tool. Gmail, Outlook, Apple Mail, and many customer support tools have some version of saved replies, signatures, snippets, drafts, or text replacement.
If your email app does not make templates easy, use a notes app. Even a simple document works.
Use names that match the moment you need them:
Pricing reply
Schedule a call
Status update
Polite decline
Keep the names boring. You are not building a content library. You are trying to find the right reply in five seconds.
Then set one rule for yourself:
Before writing a common reply from scratch, check the template first.
The habit matters more than the tool.
Spend one afternoon and get the hours back
This is a small project with a large payoff.
Set a timer for 20 minutes and pull examples from your sent folder. Set another timer for 40 minutes and write the four templates. Then spend 20 minutes saving them somewhere easy to reach.
That is enough to change your week.
The goal is not to make every email identical. The goal is to stop rebuilding the same structure over and over. Pricing questions should not drain your afternoon. Scheduling should not take six replies. Status updates should not wait until someone asks. Declines should not require emotional labor every time.
Write the four strong versions once.
Save them.
When a real message comes in, add the details. If needed, let AI adjust the tone after the structure is already set.
Four templates. One afternoon. A calmer inbox by the end of the week.
Comments