Brainforge Knowledge

partner-activation-90d-workflow

2 min read

Workflow: 90-Day Partner Activation

Purpose: Coordinate workers for a full 90-day partner activation: plan → intro → enablement → review.
Audience: Engineers + Cursor agents (humans can read for understanding).

1. Overview

This workflow turns the conceptual 90-day activation pattern into a repeatable, mostly agent-driven process for each partner (Snowflake, GSV, Omni, etc.).

High-level flow:

  1. Plan: Define 90D goal and path (human + VP Partnerships worker).
  2. Intro: Generate and refine partner intro emails / sequences (Partner Intro Email worker).
  3. Enablement: Generate co-sell assets / briefs (Partner Co‑Sell Assets worker + existing content workers).
  4. Review: Summarize performance and make tier recommendation (Partner 90-Day Review worker).

2. Workers Used

  • Outreach
    • VP Partnerships – workers/outreach/vp-partnerships/
    • Partner Intro Email – workers/outreach/partner-intro-email/
  • Content Generation
    • Design-Ready Copy – workers/content-generation/design-ready-copy/
    • Partner Co‑Sell Assets – workers/content-generation/partner-co-sell-assets/
  • Analysis
    • Partner 90-Day Review – workers/analysis/partner-90d-review/

3. Flow (Per Partner)

Step 1 – Plan (Week 0–1)

  1. Human fills / updates:
    • Partner tracker row (IPP, Qualification, economics).
    • PARTNER_CONTROL_CENTER.md basics (Type, Archetype, Origin Story).
  2. VP Partnerships worker:
    • Pressure-tests the proposed 90D goal.
    • Suggests refinements to path and success factors.

Step 2 – Intro (Week 1–2)

  1. Partner Intro Email worker:
    • Input: partner context + goal + intro_type.
    • Output: 1–3 email drafts for:
      • Platform / ventures team.
      • Optionally, event/summit or other motions.
  2. Human selects and lightly edits emails; sends via email/CRM.

Step 3 – Enablement (Week 2–6)

  1. Partner Co‑Sell Assets worker:
    • Input: partner context, use cases, relevant case studies.
    • Output: co‑sell play summary, one-pager copy, rep talk tracks.
  2. (Optional) Design-Ready Copy worker:
    • Turn co‑sell summary into formatted 1–2 pager.
  3. Human updates Control Center “Materials & Assets Overview” with links to final assets.

Step 4 – Review (Week 6–12)

  1. Ongoing: tracker + Control Center kept up to date with actions and metrics.
  2. Partner 90-Day Review worker (end of period):
    • Reads tracker row + Control Center.
    • Produces 90D summary + tier recommendation + suggested next test.
  3. Human makes final tier decision and updates tracker + Control Center.

4. Inputs & Outputs (Workflow Level)

Inputs:

  • Partner tracker row + Control Center.
  • Partner-specific context (IPP, Joint Value Proposition, etc.).

Outputs:

  • Activated intro motion (emails sent, meetings booked).
  • Co‑sell assets and briefs stored in Control Center.
  • 90D review summary and clear tier decision.

5. Notes

  • This file intentionally avoids tool-specific wiring (subagent types, MCP calls).
    That detail belongs in implementation notes or code; this is the conceptual workflow spec.

Graph View