Skip to main content

Claude/ChatGPT Prompt to Write a 6-Email SaaS Onboarding Sequence

Generate an activation-focused 6-email SaaS onboarding sequence with timing, subject variants, CTAs, and 120-word bodies that drive first value.

Fill in the placeholders

Edit the values, then copy your finished prompt.

Your Prompt
prompt.txt

                                

What this prompt does

This prompt casts the AI as a senior lifecycle marketer and makes it produce a six-email onboarding sequence optimised for activation, not opens. You provide the [product], the [aha_moment], the [cadence_days], and the sending tool [esp]. For each email it returns the day and single goal, two subject-line variants with preview text, a primary and secondary CTA, a 120-word plain-text-friendly body, and the activation event that should advance or exit each user — all pointed at the aha moment.

The structure works because it ties every send to a real activation event and an exit condition. Onboarding is where most trials quietly die, so the prompt insists each email push one user toward [aha_moment] rather than just saying hello. [cadence_days] sets the timing rhythm, [esp] shapes the format so it loads into your tool, and the arc moves from a day-zero quick win through a use-case deep dive, social proof, and a reactivation nudge. The activation gates keep the sequence honest.

When to use it

  • You are building onboarding and want every email driving toward first value.
  • Your trials drop off and you need an activation-focused sequence, not a welcome series.
  • You want subject-line variants and preview text ready for each send.
  • You need the sequence formatted to load into a specific ESP.
  • You want an activation event and exit condition defined per email.
  • You want a day-zero quick win before any deeper use-case content.

Example output

You get six ready-to-paste email blocks, one per send day: the day and single goal, two subject-line variants with preview text, a primary and secondary CTA, a 120-word plain-text-friendly HTML body, and the activation event that advances or exits each user. The arc runs from a quick-win setup through a use-case deep dive, social proof, and a reactivation nudge, all aimed at the aha moment.

Pro tips

  • Define [aha_moment] as a concrete first-value action, since every email is pointed at it and a vague moment weakens the whole sequence.
  • Set [cadence_days] to a real rhythm; the model writes one block per day, so the spacing shapes the pacing.
  • Match [esp] to your actual tool so the formatting and merge style drop in cleanly.
  • Build the day-zero quick win first — it carries the most weight in getting a user to activate.
  • Use the per-email activation event and exit condition to keep users from getting emails they no longer need, which is what keeps the sequence feeling relevant.
  • Keep each 120-word body focused on a single goal, since an email that asks a new user to do three things usually gets none of them done.
  • Test both subject-line variants against each other rather than picking one on instinct, and let the activation rate, not the open rate, decide the winner.

Frequently Asked Questions

Why optimise for activation instead of opens?
Opens measure curiosity, not progress. The sequence is built so each email moves a user toward `[aha_moment]`, the point where they actually get value. A high open rate means nothing if trials still die before reaching first value, which is why activation is the right target.
Can I load the emails straight into my ESP?
They are written as ready-to-paste blocks with plain-text-friendly HTML bodies, formatted for the `[esp]` you name. You will still set up the actual automation, merge fields, and triggers in your tool, since the prompt produces content, not the live sequence configuration.
What does the activation event per email do?
Each email defines an event that should advance a user to the next step or exit them from the sequence. That keeps people from receiving emails they no longer need, like a setup nudge after they have already set up, which makes the flow feel relevant rather than robotic.
Can I change the number of emails or cadence?
The prompt is built around six emails across the days in `[cadence_days]`, so adjusting that variable changes the timing. For a different count you would adapt the request, though six sends spanning roughly two weeks is a sensible default for most trials.
Engr Mejba Ahmed

Need this built for real?

Engr Mejba Ahmed

AI Developer · Software Engineer

I'm Mejba — I design and ship production AI systems, automations, and full-stack apps. If you want this turned into a working solution for your team, let's talk.

More in AI for Business & SaaS

Engr Mejba Ahmed

Engr Mejba Ahmed

Claude Code Expert · Online

👋

Hey there!

Quick Actions

WhatsApp Instant reply

Chat on WhatsApp

+880 1723 741224 · Instant reply

Popular Questions

Engr Mejba Ahmed is connected
Engr Mejba Ahmed is typing...
Engr Mejba Ahmed avatar

✉ Want me to follow up? Drop your email

Engr Mejba Ahmed avatar

📞 Connect Directly

Choose how you'd like to reach me

WhatsApp

+880 1723 741224

Email

[email protected]

✓ Details sent! I'll get back to you shortly.

Powered by OpenAI

335+

Blog Posts

25

AI Courses

63

Projects

Services & Expertise

Pricing & Process

Learning & Resources

Connect & Support