How do you create templates that save you time?
- The "from scratch" tax adds up fast: a client update email costs 15 minutes from scratch versus 4 with a template, and a proposal costs 3 hours versus 45 minutes.
- Avoid the 4 common mistakes: templates that sound canned, having too many of them, making them too rigid, and never updating them.
- Start with 5-7 templates covering your most frequent messages, like client updates, meeting recaps, proposals, scope changes, and follow-ups, built from your best real examples rather than written from scratch.
- Build templates with a 5-step process: notice the repetition, save your best version, add bracketed customization points, store it somewhere findable, then use and improve it over time.
A well-customized template should read like it was written just for the recipient. The time savings come from reusing structure, not skipping personalization.
The "From Scratch" Tax You're Paying Every Week
Every recurring message you write from a blank page costs you the difference between these two columns. Add up the savings column and the case makes itself.
| Task | Frequency | From scratch | With template | Weekly savings |
|---|---|---|---|---|
| Client update email | 3x/week | 15 min | 4 min | 33 min |
| Proposal / SOW | 2x/month | 3 hours | 45 min | 68 min |
| Meeting recap email | 4x/week | 12 min | 3 min | 36 min |
| New client welcome email | 2x/month | 30 min | 5 min | 12 min |
| Invoice follow-up | 2x/month | 10 min | 2 min | 4 min |
| Project status report | 1x/week | 25 min | 8 min | 17 min |
| Scope change notification | 2x/month | 20 min | 5 min | 8 min |
4 Template Mistakes That Waste the Effort
Templates fail in predictable ways: they sound canned, there are too many of them, they're too rigid, or they go stale. Here's how to avoid each trap.
Templates that sound like templates
If the recipient can tell it's a template, you've failed. Good templates have customization slots that make each version feel personal. Bad templates have "Dear [NAME]" energy.
The fix: Add 1-2 personal sentences at the top. Customize the specific details. Leave the structure and change the specifics.
Too many templates
You created 47 templates for every possible scenario. Now you spend 10 minutes finding the right one, defeating the purpose. Templates should cover your top 10 repeated tasks, not every edge case.
The fix: Start with 5-7 templates covering your most frequent tasks. Add new ones only when you've written the same thing 3+ times.
Templates that are too rigid
Your template forces a structure that doesn't fit every situation. You end up fighting the template instead of using it. A template should be a starting point, not a straitjacket.
The fix: Build templates as building blocks: a strong opening, key sections, and a closing. Mix and match sections based on the situation.
Never updating templates
Your proposal template still references pricing from 2024 and services you no longer offer. Templates need maintenance: a 15-minute review every quarter keeps them relevant.
The fix: Set a quarterly calendar reminder: "Review and update templates." Delete ones you don't use, update ones that are stale.
5 Ready-to-Use Templates
Copy these into your own library. Everything in [brackets] is a customization point; fill those in and the message reads like it was written just for the recipient.
Weekly Client Update
Use case: End-of-week status update to active clients
Hi [Name], Quick update on [project name] for this week: Completed: - [Deliverable 1] - [Deliverable 2] In Progress: - [Item]: expected completion [date] Needs Your Input: - [Decision/approval needed]: needed by [date] to stay on timeline Next week I'll be focused on [upcoming milestone]. Let me know if you have questions. [Your name]
Customize:
- Project-specific deliverables
- Actual dates and milestones
- Any blockers or decisions needed
Meeting Recap
Use case: Post-meeting summary with action items
Hi [attendees], Thanks for the time today. Here's a quick recap: Key Decisions: - [Decision 1] - [Decision 2] Action Items: - [Person]: [Task], due [date] - [Person]: [Task], due [date] - Me: [Task], due [date] Next meeting: [date/time] Let me know if I missed anything.
Customize:
- Actual decisions made
- Specific action items with owners
- Next meeting date
Scope Change Notice
Use case: When client requests work outside the original agreement
Hi [Name], Appreciate you raising [new request]. Quick note: this falls outside our current scope. Original scope covers: [what's included] New request: [what they asked for] Estimated additional: [hours or cost] I'm happy to take this on. Two options: 1. Add it to the current project at [rate/cost] 2. Scope it as a separate phase after [current project] wraps Which works best? I can send a quick addendum either way.
Customize:
- Specific scope boundaries
- Actual cost/time estimate
- Options that work for your business
Project Proposal (Short)
Use case: Quick proposal for small-to-medium engagements
[Project Name]: Proposal for [Client] Objective: [One sentence describing the goal] Scope: - [Deliverable 1] - [Deliverable 2] - [Deliverable 3] Not Included: [Explicitly list exclusions] Timeline: [Start date] → [End date] ([X weeks]) Investment: $[amount] ([payment structure]) Process: 1. Kickoff call ([date]) 2. [Phase 1]: [timeline] 3. [Phase 2]: [timeline] 4. Final delivery + review Next Step: Reply to confirm and I'll send the agreement. Valid until [date].
Customize:
- Project-specific deliverables and exclusions
- Actual pricing and timeline
- Payment structure (milestone, monthly, upfront)
Polite Follow-Up
Use case: When you're waiting on a response
Hi [Name], Following up on my [date] email about [topic]. I know things get buried. I need [specific thing] by [date] to keep [project] on track. Without it, [consequence]. Can you get me [what you need] by [realistic date]? If that doesn't work, let me know what does and I'll adjust.
Customize:
- Specific item you need
- Realistic deadline
- Actual consequence of delay
How to Build Your Own Template Library
Don't sit down to "write templates." Extract them from work you're already doing, one repetition at a time, with this five-step process.
Notice the repetition
When you write something for the third time, it's a template candidate. Flag it: "I should template this." Don't build the template now. Just notice.
Save the best version
Next time you write it, spend an extra 5 minutes making it great. This becomes your template. Don't write a template from scratch. Extract it from your best real example.
Add [brackets] for customization
Replace specific details with [placeholder] markers. Every bracket is a customization point that makes the template feel personal. Aim for 3-5 customization points per template.
Store it where you'll find it
One folder, one doc, one app. Not scattered across 4 places. Label clearly: "Template - Weekly Client Update" not "email thing."
Use it and improve it
Every time you use a template, notice what you change. If you change the same thing every time, update the template. If a section never gets used, delete it. Templates evolve.
