Brainforge Knowledge

PARTNER_CONTROL_CENTER

3 min read

Polytomic Partner Control Center

Purpose: Single source of truth for this partnership. Mirrors the partner tracker fields and adds context for GTM and agents.

1. Partner Identification

FieldValue
PARTNER NAMEPolytomic
PRIORITY THIS WEEKBronze - maintain technical vendor reliability while validating co-sell relevance
PARTNER TYPEPlatform / Data integration vendor
PARTNER ARCHETYPECapability Completer
SLACK CHANNELYes - #vendor-polytomic (C08DXL2TM8B) + #external-polytomic-lmnt (C0A49DN6RSQ)
ORIGIN STORYPartnered via customer data movement use cases (Snowflake/BigQuery) and recurring connector support needs.

2. Partner Action Planning

FieldValue
FIRST ACTION DATE2025-12-16 (tracked partner ops mentions in #sales-partnerships)
LAST ACTION DATE2026-04-01
LAST ACTION NOTESActive support interactions: Linear connector auth clarification (no action needed for current API-key setup), ongoing PostHog connector troubleshooting, and Calendly connector feature request for Eden pipeline.
NEXT ACTION NOTES1) Consolidate open support asks into one owner-managed ticket list. 2) Confirm ETA on Calendly connector request and communicate to Eden motion owners. 3) Publish a short “known-good connector config” artifact for repeatable setup.
BLOCKERSSupport work is fragmented across threads; feature-request dependency (Calendly) and connector edge-case debugging slow delivery tempo.

3. Partner Qualification

FieldValue
ICP MATCH[Yes/No]
ACCOUNTS NAMED[3+ specific accounts]
INTRO MECHANISM[Sales reps / Referrals / Co-marketing / etc.]
ECONOMICS[Pricing / margin constraints]

4. 90-Day Activation Plan

FieldValue
90D GOAL[Get X quantity Y-quality outcomes by DATE]
90D START DATE[YYYY-MM-DD]
90D STATUS[Not Started/On Track/At Risk/Delivered/Failed]

Summary:

[One short paragraph restating the 90-day plan in plain language.]

5. Relationship Context

FieldValue
KEY CONTACT NAME[Primary partner manager]
KEY CONTACT ROLE[Role/Title]
ORIGIN STORY[How relationship with this contact formed]
RELATIONSHIP NOTES[Trust level, internal champions, dynamics]

6. Rep Engagement Summary

FieldValue
REPS BRINGING DEALS[Number]
REPS ENGAGED[Number]
LEADS GENERATED[Number]
CLOSED/WON DEALS[Number]

Rep Notes (by tier):

  • Tier 1 – Reps Bringing Deals: [Names]
  • Tier 2 – Engaged Reps: [Names]
  • Tier 3/4 – Cold/Stale: [Counts + any important notes]

7. Total Activity Tracking

FieldValue
FIRST TOUCH DATE2025-12-16 (tracked in partner ops channel)
LAST ENGAGEMENT DATE2026-04-01
DAYS SINCE LAST TOUCH6 (as of 2026-04-07)
MESSAGES SENTHigh-volume technical support thread activity in late March/early April (connectors, auth, endpoint behavior).
SALES ASSETS SENTConnector docs links, Lmnt external channel context, and connector request scope notes.
CO-MARKETING ASSETS CREATEDNone recent; mostly technical enablement/support artifacts.
CALLS BOOKEDNot clearly logged in recent thread snippets.
PROPOSAL SENTNo formal partner proposal tracked.
IN-PERSON VISITNot logged.

8. Partner Status & Pipeline Stages

Partner Status

FieldValue
LATEST COMPLETED PHASE[Phase name]

Partner Pipeline Stages

FieldValue
PHASE 1: To-Do[Key todos before first meeting or activation]
PHASE 2: Meeting Booked[Notes on meetings booked]
PHASE 2.5: Proposal Sent[Notes + link if applicable]
PHASE 3: Contract Signed[Notes + link if applicable]
PHASE 4: Post Closed-Won Start[Notes]
HUBSPOT LINK[URL]
PARTNER NOTION HUB[URL if exists]
PROPOSAL FILE[Path/URL]
CONTRACT FILE[Path/URL]
PARTNER DRIVE[Path/URL]

9. Materials & Assets Overview

Rep Enablement

AssetTypeStatusLink
Polytomic connector runbook (internal)Technical enablement playbookIn progressBuild from #vendor-polytomic March-April troubleshooting threads.

Partner-Facing

AssetTypeStatusLink
[Name][Partner deck / JV statement / etc.][Status][link]

Internal

AssetTypeStatusLink
[Name][Playbook / notes][Status][link]

Customer-Facing / Co-Marketing

AssetTypeStatusLink
[Name][Case study / solution brief / webinar][Status][link]

10. Active Motions & Pipeline

  • Motion 1: Connector reliability and support lane - Owner: data platform team - Stage: Active. Resolve PostHog/Linear thread and lock standard configs.
  • Motion 2: Calendly connector request (Eden) - Owner: partnership + implementation owner - Stage: Pending vendor ETA. Use this as key proof point for partner responsiveness.

11. Partner Scoring & Tier Recommendation

Note: This section is where scoring logic will evolve. Fill in qualitatively for now; later it can be numeric and automated.

Subscores (0–5)

DimensionNotesScore (0–5)
Qualification[ICP/Economics assessment][ ]
Engagement[Reps, meetings, responsiveness][ ]
Velocity[Speed through phases, NEXT ACTION discipline][ ]
Outcomes[Leads, revenue, influence][ ]

Overall

  • Total Score (provisional): [ / 20]
  • Current Tier (Tracker): Bronze
  • Recommendation: [Promote / Maintain / Demote + brief rationale]

12. Notes & Open Questions

  • Messaging sequence (next 2 weeks):
    1. Send structured follow-up to Polytomic with 3 prioritized asks (ETA, owner, dependency).
    2. Confirm whether Polytomic remains Bronze-capable vendor partner or should be deprioritized for GTM motions.
    3. Route all partner updates into #sales-partnerships weekly summary.

Graph View