Worker: Partner Co‑Sell Assets

Category: Content Generation
Status: Planned (scaffolding)
Audience: Engineers + Cursor agents


1. Purpose

Generate and maintain partner-specific co‑sell assets that “talk for themselves”:

  • Short co‑sell play descriptions (per templates/co-sell-playbook-template.md).
  • One‑page briefs for reps and founders.
  • Snippets for LinkedIn/Slack/email that explain “Brainforge x [Partner]”.

This worker should take partner context and produce ready-to-use text assets that can be dropped into decks, docs, and communications.


2. Inputs

Required:

  • partner_name
  • partner_type and partner_archetype (from IPP / Control Center)
  • primary_use_cases – 2–3 bullets (what we actually do together)
  • target_audience – e.g., “partner AEs”, “portfolio founders”, “joint customers”
  • goal – what this co‑sell asset should support (e.g., “help AEs pitch Brainforge as the data/AI arm”)

Optional:

  • Paths to reference docs:
    • Control Center: knowledge/sales/partners/[Partner]/PARTNER_CONTROL_CENTER.md
    • Case studies: knowledge/sales/marketing-assets/case-studies/
    • Any existing partner deck/notes.

3. Outputs

Markdown block with:

  • Co‑sell Play Summary (1–2 paragraphs)
  • Bullet Version:
    • Who it’s for
    • Problem
    • Brainforge + Partner solution
    • Outcomes / proof points
  • Rep Script Snippets:
    • 1–2 talk tracks a rep can say out loud or paste into email/Slack.

4. Rules

  • Always name both sides clearly (“Brainforge” and the partner) and what each brings.
  • Anchor on operator-level outcomes, not just technology.
  • Keep a version that is:
    • Safe to paste in internal partner docs (no client-sensitive details).
    • Easy to adapt to slide bullets or one-pagers.