email-marketing
Email Marketing
When to Use
- Building a welcome sequence for new signups or lead magnet downloads.
- Designing a lead nurture sequence to move prospects toward conversion.
- Creating a re-engagement campaign for inactive users or subscribers.
- Writing an onboarding email series that drives product activation.
- Planning a newsletter cadence and format.
- Optimizing existing sequences for open rate, click rate, or conversion.
Context Required
- From startup-context: product description, ICP, value proposition, tone of voice, current user journey stages, key activation metrics.
- From the user: sequence type needed (welcome, nurture, re-engagement, onboarding, post-purchase, educational), audience context (who they are, what triggered entry, relationship stage), current email list size and segments, existing sequences (if optimizing), email platform in use, primary conversion action, any existing performance data.
More from shawnpang/startup-founder-skills
terms-of-service
When the user needs to draft, review, or update terms of service for their SaaS product or web application.
65pitch-deck
When the user wants to create, review, or restructure a fundraising pitch deck for seed or Series A. Also activates when the user mentions "deck", "pitch", "investor presentation", or "slide structure".
55competitive-analysis
When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives.
53review-mining
When the user wants to research customer pain points, complaints, or sentiment using review platforms like Trustpilot, G2, Capterra, or app stores. Also use when the user mentions "what are users saying", "competitor reviews", "pain points", or "voice of customer research".
53data-room
When the user wants to prepare a due diligence data room for fundraising, or when an investor has requested additional materials after a pitch. Also activates for "data room", "due diligence", "DD checklist", or "what documents do investors need?".
51prd-writing
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec.
49