Problem Statement
The project aims to transform a product’s user events, personas, and constraints into a complete lifecycle and segmentation architecture. The workflow must synthesize lifecycle stages, segment definitions, messaging logic, and implementation specs into a structured output. The goal is to enable teams to consistently generate actionable lifecycle models that can be directly deployed into marketing automation tools.
Steps
Ingest project inputs
INGESTCollect all provided information, including product surface area, key user events, personas, lifecycle stages, and constraints. Parse and normalize inputs so they can be used consistently in downstream steps.
Retrieve behavioral and lifecycle patterns
EXECUTEAnalyze the provided events and persona details to infer typical user flows and milestones. Identify opportunities for segmentation and engagement based on industry-standard lifecycle patterns.
Generate lifecycle model
EXECUTEDraft lifecycle stages, including definitions, entry criteria, exit criteria, and associated event logic. Ensure the stages align with product behavior and realistic user journeys.
Generate segmentation and messaging plan
EXECUTEProduce 5–12 actionable segments with goals, messaging, proof points, triggers, suppressions, and channel sequencing. Create a corresponding message matrix.
Validate implementation spec
EXECUTECheck event names, required properties, and QA checklist for completeness and accuracy. Ensure the final specification is implementable in product analytics and messaging tools.
Prompt Configurations
Lifecycle and Segmentation Drafting Prompt
You are an expert lifecycle marketing architect. Using the provided product surface area, user events, personas, lifecycle stages, and constraints, generate: 1. A complete lifecycle model with stage names, definitions, entry criteria, and exit criteria. 2. 5–12 high-impact behavioral and firmographic segments, each with: goal, primary message, proof points, trigger logic, suppression rules, and recommended channel sequence. 3. A detailed message matrix summarizing messaging across segments. 4. An implementation spec including event names, event properties, and a tracking QA checklist. Tone: professional, precise, and implementation-ready. Constraints: do not invent data beyond reasonable inference; rely primarily on the provided inputs; output must be structured and actionable for lifecycle and CRM teams.
Example Inputs/Outputs
Product: SaaS analytics tool. Key events: signup_started, signup_completed, workspace_created, report_created, share_clicked. Personas: data analysts, product managers. Constraints: email + in-app only; GDPR compliance. Lifecycle stages: Signup, Activation, Engagement. Request: produce full lifecycle+segmentation architecture.
Lifecycle model with defined entry/exit criteria for Signup → Activation → Engagement; 8 segments including Early-stage Evaluators, Power Users, Blocked Onboarding Users; message matrix with onboarding nudges, activation proof points, and engagement reinforcement; implementation spec listing events, required properties such as workspace_id and report_id, plus QA checklist for event validation.