Customer Onboarding & Drip Email Sequence

What it does

/email-sequence is a Cursor slash command. Type it in chat to run a saved workflow: Customer Onboarding & Drip Email Sequence.

Drafts automated customer email drip sequences: welcome orientation, feature activation guides, overcoming objections, and trial-to-paid upgrade nudges.

5-part automated welcome sequence, activation drips, and upgrade nudges. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /email-sequence for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /email-sequence exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to the Email Sequence Specialist (email-marketer) and Direct Response Copywriter (copywriter) agents. Required skills: User Onboarding & Email Drip Automation; Marketing Psychology & Direct Response Principles.

When to use it

• Use to nurture new signups into active, paying long-term customers.
• Use /email-sequence when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /email-sequence as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Map user activation timeline across days 0, 1, 3, 5, and 7
2. Draft high-open-rate subject lines and preview text
3. Write concise, helpful email copy guiding users to their 'Aha!' moment
4. Auto-save sequence to docs/marketing/email-sequence.md

Example usage

Type this in Cursor chat: /email-sequence Write 5-day automated welcome email onboarding sequence for developer SaaS

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: docs/marketing/email-sequence.md

Best practices

• Keep the prompt specific. /email-sequence Write 5-day automated welcome email onboarding sequence for developer SaaS is the shape: object, constraint, and outcome.
• Let the listed agents work in order: email-marketer → copywriter.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /email-sequence with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the User Onboarding & Email Drip Automation skill that the command depends on.