Drip Campaign Skill

Design nurture as progressive context, not a pile of delayed emails. Each step should advance readiness or route the contact elsewhere.

Fit Check

Primary lens: time-based nurture streams, branching logic, lead scoring hooks, and conversion analysis.
Common request signals: nurture sequence planning, lead scoring hooks, drop-off analysis, sales handoffs, and timed education streams.
Default posture: Design nurture as progressive context, not a pile of delayed emails. Each step should advance readiness or route the contact elsewhere.
Useful output family: drip maps, nurture briefs, branch logic tables, scoring hooks, drop-off diagnoses, and conversion-focused rewrite plans.
Production boundary: separate recommendation from execution.
Evidence boundary: say which source material supports the recommendation.
Review boundary: identify the human owner for risky changes.
Data boundary: do not assume missing fields, consent, or suppression state.
Platform boundary: describe provider-specific steps in operational language.
Measurement boundary: define what success or recovery will look like.