90-Day Partner Activation – Execution Runbook
Audience: Humans (ops/PM + partnerships). This is the checklist version of the 90-Day Activation Playbook, wired to concrete assets and agent workflows.
Use with:90-day-activation-playbook.md(conceptual),PARTNER_CONTROL_CENTER.md, partner tracker, and relevant agents.
1. Inputs (Before You Start)
For each partner:
PARTNER_CONTROL_CENTER.mdexists (from template).- Partner row exists in the tracker with:
- Partner Type + Archetype
- ICP Match, Accounts Named, Intro Mechanism, Economics OK
- You can name:
- 1–2 primary partner managers
- 2–3 candidate reps/founders for intros
2. Phase 1 (Week 0–2): Qualify + Intro
Goal: Confirm this partner deserves a 90-day test and set up a clear intro motion.
2.1 Fill/confirm Control Center basics
- In
PARTNER_CONTROL_CENTER.md:PARTNER TYPEandPARTNER ARCHETYPE(matchstrategy/ideal-partner-profile.md).PRIORITY THIS WEEK(Calibration, Bronze, etc.).ORIGIN STORYand coreRELATIONSHIP NOTES.
2.2 Define the 90D goal
- Use
playbooks/90-day-activation-playbook.md(Steps 1–3) and:- Fill section 4 in the Control Center:
90D GOAL90D START DATE90D STATUSSummary(1–2 sentences).
- Fill section 4 in the Control Center:
2.3 Draft mutual intro emails
- Start from any relevant draft in
drafts/(e.g.GSV_INTRO_MEETING_DRAFT.md). - Use:
playbooks/partner-playbook.md→ Three Whys.templates/outreach-sequences.md→ structure and tone.
- Produce:
- Partner → Founder / AE intro email.
- Brainforge → Founder / AE follow-up email.
2.4 (Optional) Agent dry run
- Use the VP of Partnerships agent (
partnerships/agents/vp-partnerships-agent.md) to:- Pressure-test the 90D goal.
- Critique the mutual intro email for clarity and value exchange.
3. Phase 2 (Week 2–6): Rep / Founder Enablement
Goal: Give the partner’s reps/founders a clear, easy way to bring Brainforge into deals.
3.1 Create partner-specific co-sell play(s)
- Use
templates/co-sell-playbook-template.mdto define:- Play Name: “Brainforge x [Partner]: [Outcome]”
- Target account profile, pain points, Brainforge approach, partner platform role, outcome.
- Link the finished play under Materials & Assets Overview → Partner-Facing in the Control Center.
3.2 Select / adapt proof assets
- From
knowledge/sales/marketing-assets/case-studies/:- Pick 1–3 case studies that best match this partner’s ICP.
- Add them under:
- Internal and Customer-Facing / Co-Marketing in the Control Center.
3.3 Internal briefing
- Use
templates/account-brief-template.mdas a pattern to create:- A short Partner Brief for Brainforge:
- Who the partner is, why they matter, what the 90D test is, what a “good intro” looks like.
- A short Partner Brief for Brainforge:
- Store it under Internal in the Control Center.
4. Phase 3 (Week 6–12): Pipeline & Review
Goal: Turn activity into pipeline, then make a tier decision.
4.1 Weekly ops routine
- In the tracker (
partner-tracking-system.mdschema):- Update:
- Intros made, Qualified Convos, Deals Brought In, CLOSED/WON DEALS.
- Keep
Next Action Date/Type/Repfresh.
- Update:
- In the Control Center:
- Update
LAST ACTION DATE,LAST ACTION NOTES,NEXT ACTION NOTES. - Log new motions under Active Motions & Pipeline.
- Update
4.2 90D review
- At the end of 90 days:
- Use Partner Scoring & Tier Recommendation section to:
- Score Qualification / Engagement / Velocity / Outcomes.
- Write a 2–4 sentence recommendation.
- Update:
Current Tier (Tracker)(Calibration → Bronze/Silver/Gold or Deprioritize).90D STATUSto Delivered / At Risk / Failed.
- Use Partner Scoring & Tier Recommendation section to:
5. Where Agents Fit In (Optional Wiring)
For engineers wiring Cursor agents, this runbook surfaces touchpoints, not wiring details:
- Planning: VP of Partnerships agent to refine goals and paths.
- Outreach: Sequence/intro agents that use:
templates/outreach-sequences.md- Drafts under
drafts/
- Content: Content-generation agents that transform:
- Co-sell templates → partner-specific one-pagers.
- Case studies → partner-tailored proof assets.
- Review: Analysis agents that:
- Read the tracker + Control Centers.
- Generate weekly / 90D summaries and tier recommendations.
The low-level wiring (subagent types, prompts, feedback loop integration) should live under gtm/agents/ workflows, not in this doc.