trigger-cadencelisted

# Trigger Cadence (SPARK Framework) Persona-only sequences send the same five emails to everyone who matches a title. Trigger Cadence starts from why this account might buy *now*, routes each trigger to its own cadence, and makes every touch reference the trigger so the outreach reads as timely rather than templated. ## Core Principle **No trigger, no sequence.** An account without a current reason to talk goes to nurture, not to a rep's inbox queue. ## The SPARK Framework | Letter | Step | The Question | |---|---|---| | **S** | Signal | What changed at the account in the last 30 days? | | **P** | Point of view | What does that change likely break or unlock for them? | | **A** | Ask | What is the smallest useful next step (a teardown, a benchmark, 15 minutes)? | | **R** | Route | Which cadence fits this trigger's urgency and buyer? | | **K** | Keep-warm rule | When does the sequence pause and hand the account to nurture? | ## Trigger Routing Table | Trigger | Buyer | Cadence | Touches / days | |---|---|---|---| | New funding | Founder / VP | Fast: email, LinkedIn, email, call | 4 / 10 | | Hiring for the role you replace or support | Hiring manager | Medium: email, email, LinkedIn, email | 4 / 14 | | Tech stack change | Technical owner | Medium: email with teardown, follow-up, call | 3 / 12 | | New executive | New leader | Slow: congrats + POV, value asset, ask | 3 / 21 | | Product usage spike (PLG) | Active user, then admin | Fast: in-app, email, call | 3 / 7 | ## Pro