Every time you sign a new client, you write roughly the same five emails. The welcome email. The kickoff invitation. The asset request. The Week 1 recap. The Day 30 review invitation. You write them fresh each time because it feels more personal, and each one takes 15-20 minutes of staring at a blank draft.
Over 15 new clients a year, that’s 15 hours of email writing that produces more or less the same result every time. The only thing that changes are the names, dates, and project-specific details.
Write them once. Save them as templates. Personalize in 3 minutes. The client gets the same level of professionalism, you get 14 hours back, and your onboarding communication becomes consistent instead of dependent on how much energy you have the day you hit send.
Below are the five templates. Copy them into your email client, task manager, or a document, and stop rewriting them.
Template 1: Welcome / Contract Confirmed
When to send: Within 2 hours of receiving the signed contract.
Purpose: Acknowledge the agreement, set expectations for the first week, give them one clear action item.
Subject: Welcome to [ProjectType], [Your Name] / [ClientName]
Hi [Name],
Thrilled to be working with [Company]. Your contract is confirmed and I’ve set up your project workspace at [link], I’ll walk you through it at kickoff.
Here’s what the next few days look like:
By tomorrow: I’ll send you a kickoff meeting invitation with the agenda. Please confirm your availability for [proposed date/time] or suggest an alternative.
At kickoff: We’ll confirm the 30-day milestone plan, go through the shared workspace, and cover revisions and communication. Should take about 45 minutes.
Week 1 goal: [First specific milestone, e.g., “Receive your brand assets and confirm the copy brief so I can start the first draft.”]
My one ask before kickoff: gather any brand materials (logos, fonts, brand guide) and add them to the Assets folder in the workspace. If you don’t have access yet, I’ll sort that at kickoff.
Looking forward to getting started.
[Your name]
What to personalize: [Name], [ProjectType], [Company], [workspace link], [proposed kickoff date/time], [first milestone description].
Do not add: Excessive thanks, “I’m so excited,” or more than one action item. Keep it professional and efficient.
Template 2: Kickoff Meeting Invitation
When to send: 2-3 business days before the kickoff meeting.
Purpose: Give the client an agenda so they arrive prepared. Clients with agendas give better input than clients who are learning the agenda in real time.
Subject: Kickoff Meeting, [ProjectName], [Date]
Hi [Name],
Our kickoff is confirmed for [Day, Date] at [Time] via [Zoom/Meet/etc., link below]. The meeting will run 45-50 minutes.
Agenda:
- Introductions (if there are additional team members), 5 min
- 30-day project roadmap review, 10 min
- Shared workspace tour, 5 min
- Alignment conversation (expectations, success definition, Day 30 goal), 15 min
- Communication and revision process, 5 min
- Asset checklist review, 5 min
- Open questions, 5 min
Please have ready:
- Any brand guidelines or assets you want me to reference
- Access credentials for [any relevant tool/platform] if applicable
- Your main question or concern about the project (we’ll address it in point 7)
[Calendar invite / Zoom link attached]
See you [day].
[Your name]
What to personalize: Meeting details, project-specific agenda items, and the “please have ready” list based on what you actually need.
Add to this template only: If the project has specific pre-kickoff prep (like reading a document or completing a questionnaire), add it here.
A detailed kickoff agenda signals that you run organized projects. Most clients have worked with freelancers who showed up to a kickoff with no structure. Your agenda creates instant contrast, before the meeting even happens.
Template 3: Asset Request
When to send: Within 24 hours of kickoff, or sooner if asset delivery is on the critical path.
Purpose: Make asset requests specific, dated, and easy to fulfill. Vague requests get vague responses.
Subject: Asset Request, [ProjectName], Needed by [Date]
Hi [Name],
Following kickoff, here’s the complete asset list for [Project]. I need everything below by [Date] to stay on schedule for the Week 2 milestone.
Brand Assets (Folder: Assets & Brand in workspace)
- Logo files: SVG, PNG, transparent background preferred
- Brand guidelines PDF or link
- Font files or license link
- Approved color palette (hex codes)
- Brand photography library, if available
Project-Specific Assets
- [Specific document, e.g., “Current About page copy for reference”]
- [Specific access, e.g., “HubSpot access to review existing email templates”]
- [Specific information, e.g., “Three examples of competitor messaging you find compelling”]
People to Meet
- Intro to [role], [purpose, e.g., “to understand the sales team’s language and common objections”]
You can upload files directly to the workspace or reply to this email with attachments for smaller items.
If anything on this list will take longer than [Date], please flag it today so I can plan around it.
[Your name]
What to personalize: All checkboxes, deadline date, and any project-specific requirements.
Critical rule: Always include a deadline. “When you can” means next month. “[Specific date]” means by that date. Use the deadline from your project plan, not an arbitrary one.
Template 4: Week 1 Recap
When to send: Every Friday afternoon, starting Week 1.
Purpose: Maintain visibility, surface client action items, and train the client to expect consistent updates.
Subject: Week 1 Recap, [ProjectName]
Hi [Name],
Quick Friday update:
Completed this week:
- [Milestone or task 1]
- [Milestone or task 2]
- Shared workspace set up and confirmed (link: [workspace link])
Coming up Week 2:
- [First deliverable or milestone], target by [date]
- [Next step]
One item that needs you: [Specific action item with deadline, e.g., “The brand assets folder is still empty, I need logos and brand guide by Monday to stay on track for the Week 2 draft. Can you upload by EOD Monday?”]
Updated project plan attached.
[Your name]
What to personalize: Completed items, upcoming milestones, and the “one item that needs you” section, this is always specific to that week.
The rule on this email: Never send it without a specific client action item. If you have nothing to ask, create the habit anyway but note that all is on track. Never let a week pass without a touchpoint.
Template 5: Day 30 Review Invitation
When to send: At the end of Week 3 or beginning of Week 4, early enough for the client to prepare.
Purpose: Formally invite the review, set the agenda, and frame it as a productive checkpoint rather than a performance review.
Subject: Day 30 Project Review, [Date], Agenda Inside
Hi [Name],
We’re approaching the 30-day mark, time for our first project review. I’d like to schedule this for [proposed date/time]. Can you confirm, or suggest an alternative within the same week?
Agenda for the Day 30 Review (30 minutes):
- Progress vs. 30-day milestone, 5 min
- Results and early indicators vs. the success definition document, 10 min
- What’s working well / what to adjust, 5 min
- Priorities and plan for the next 30 days, 10 min
Before the meeting, I’ll send:
- Updated project plan showing progress
- Summary of deliverables completed in Month 1
- Early data on [relevant metric, if applicable]
If you’d like to prepare anything for point 3 (“what to adjust”), it’s useful to have your team’s top 1-2 observations ready, this helps make the adjustment conversation actionable.
Looking forward to it.
[Your name]
What to personalize: Meeting details, relevant metric in the preparation section, and any project-specific agenda adjustments.
Using Templates Without Sounding Like a Template
The common objection to email templates is that they sound canned. Here’s how to avoid that:
-
Personalize the first sentence. Always open with something specific: a reference to the kickoff conversation, something about their industry or recent news, a specific goal they named. One specific sentence makes the rest of the template feel personal.
-
Update the “specific” fields every time. The asset request template with generic placeholders isn’t a template, it’s a draft. The specific items (which assets, which date, which contacts) must be filled in correctly for every client.
-
Adjust the tone to the client. A Fortune 500 enterprise gets more formal language. A startup founder you’ve known for years gets something more casual. The structure stays the same; the register adapts.
-
Remove anything that doesn’t apply. If there are no “people to meet” in the asset request, delete that section. Don’t send a template with empty sections, that’s when it reads like a template.
Done correctly, templated emails look like well-prepared, professionally consistent communication. The client doesn’t need to know you used a template. They just need to feel like they’re working with someone organized.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
