Design a branching B2B nurture sequence with trigger logic

You are a senior B2B lifecycle marketer who designs nurture flows that adapt to behavior, not one-size-fits-all blasts.

Context:
- Product and value prop: [ONE-LINE — what you sell and to whom]
- Entry trigger: [WHAT STARTS THE FLOW — e.g. 'downloaded the pricing guide', 'started but didn't finish a demo request']
- Primary persona and stage: [e.g. 'mid-market ops leader, awareness or consideration']
- Automation tool: [HUBSPOT / MARKETO / ACTIVECAMPAIGN / GENERIC — affects how logic is expressed]
- Constraints: [cadence cap, tone, must-include links, length limit per email]

Design a branching nurture sequence:
1. A flow diagram in text: the entry trigger, the main path, and the branches. State the rule that sends a lead down each branch (e.g. 'opened 2 or more emails -> deep-dive path; no opens by day 5 -> re-engagement path').
2. Four to six emails across the main path, each with: goal, subject line, a 2-3 sentence body preview, a single CTA, and send timing relative to the previous step. Write for the persona, not a generic buyer.
3. Two branch variants: one for high engagement (accelerate or offer a demo) and one for disengagement (a different angle or a break-the-pattern email). Each branch needs its own trigger rule and 1-2 emails.
4. Suppression and exit rules: when a lead leaves the flow (converted, replied, marked sales-ready, unsubscribed). Never keep emailing a converted lead.
5. Personalization tokens used (realistically — first name, company, industry) and where dynamic content differs by persona.
6. A measurement plan: the metric that defines success per branch, and which branch to kill if it underperforms.

Rules:
- Compliance basics: include an unsubscribe path and honor it; no deceptive subject lines; respect the automation tool's send limits.
- Every email has exactly one primary CTA. No decision fatigue.
- Do not invent open or click benchmarks. Frame success metrics without guaranteed numbers.

Output: the text flow diagram, the email specs (main plus branches), suppression and exit rules, and the measurement plan.

Success signal: the output is good only if every branch has an explicit trigger rule, no converted lead stays in the flow, and every email has a single CTA and a stated goal.