Purpose
Use this guide anytime KZ needs to write an email promoting a service offering, such as an SEO health check, analytics review, website support offer, AEO/GEO review, PromptThis implementation, roadmap review, or post-launch website check.
This guide is about writing the email itself. It is not about list strategy, sending cadence, segmentation, tracking, or campaign planning.
Core Idea
A good service offering email should feel useful before it feels promotional.
The reader should understand:
- What problem we are pointing out
- Why it matters
- What we can help with
- What the next step is
The transcripts repeatedly come back to the idea that email should reward the reader for opening and reading. The email should provide a clear useful point, not just ask for something.
Basic Structure
Use this structure for most service offering emails:
- Subject line
- Preview text
- Opening problem
- Useful insight
- Service offer
- Clear CTA
- P.S.
The goal is to keep the email focused and easy to scan.
1. Subject Line
The subject line should be specific, clear, and connected to a real client concern.
Avoid vague or overly salesy subject lines.
Weak:
Improve your website today
Better:
Is your website tracking still working properly?
Weak:
KZ SEO Services
Better:
A quick SEO health check for your website
Weak:
New service offering from KZ
Better:
Small website issues that can quietly add up
A good subject line should make the reader think, “That might apply to me.”
2. Preview Text
The preview text should support the subject line. Do not let the email platform automatically pull random first-line text.
Use it to clarify the value of the email.
Examples:
We’re offering a focused review of metadata, broken links, and tracking basics.
A quick check can reveal small issues before they become bigger roadmap items.
Useful for websites that have not had a recent analytics or SEO review.
The transcript specifically points out that preview text matters because people often use it to decide whether the email is worth opening.
3. Opening Problem
Start with the problem, not the service.
The reader should recognize the situation before we explain what we offer.
Weak:
We are now offering SEO health checks.
Better:
Websites tend to collect small issues over time: missing metadata, old redirects, broken links, outdated tracking, or pages that Google can crawl but not clearly understand.
This works because it gives the service a reason to exist. The transcript recommends introducing the problem or condition that makes the solution relevant before presenting the solution.
4. Useful Insight
Every offering email should give the reader one useful idea, even if they do not click or reply.
This can be:
- A simple explanation
- A common issue we see
- A small checklist
- A practical tip
- A warning sign
- A useful question to ask internally
Example:
One simple thing to check is whether your most important pages have unique page titles and meta descriptions. These small pieces of content help search engines understand the page and help users decide whether to click.
This makes the email feel helpful instead of purely promotional.
5. Service Offer
After the problem and insight, introduce the service as the next logical step.
Keep it simple. Do not over-explain every detail of the service.
Example:
We’re offering a focused Website Health Check for organizations that want a clearer picture of what needs attention. The goal is to identify practical fixes, not create a huge unnecessary project.
The offer should feel specific and manageable.
6. CTA
The CTA should be clear, low-friction, and connected to the email.
Avoid generic CTAs like:
Contact us today.
Use CTAs that feel natural:
Reply to this email if you’d like us to take a quick look.
Let us know if you’d like this added to your roadmap.
Send us your URL and we can confirm whether this would be useful for your site.
Book a quick review call and we can walk through the main opportunities.
The transcript makes a useful point that CTAs should be contextual, not copied and pasted into every piece of content. The ask should connect directly to the topic of the email.
7. P.S.
Use the P.S. to reinforce the main point or make the CTA feel easier.
The P.S. is useful because many people skim the body and still read the ending. The transcript specifically calls out the P.S. as one of the most-read parts of an email after the headline.
Examples:
P.S. If your site has not had a recent review, this is a good way to catch small issues before they turn into bigger roadmap items.
P.S. This is especially useful for sites that have been live for a while and have not had a recent SEO or analytics check.
P.S. Even if everything is mostly working, a quick review can help confirm what is worth prioritizing next.
Recommended Tone
KZ offering emails should sound:
- Helpful
- Practical
- Clear
- Professional but not stiff
- Confident but not hypey
- Specific, not generic
- Low-pressure
Avoid language like:
Unlock explosive growth.
Supercharge your digital presence.
Don’t miss out on this limited-time opportunity.
Use language like:
This can help identify what is working, what needs attention, and what can wait.
The goal is to give you a clear list of practical next steps.
This is useful if your site has not had a recent review.
