Omni 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 NAMEOmni
PRIORITY THIS WEEKGold
PARTNER TYPEPlatform
PARTNER ARCHETYPEDeal Accelerator + Capability Completer (implementation + AI behind Omni)
SLACK CHANNELpartnership-omni (confirm exact channel name + add link)
ORIGIN STORYCo-sell and implementation on joint customer accounts (e.g. Elements, Eat in Health); building toward same rep-enablement rigor as Snowflake

2. Partner Action Planning

FieldValue
FIRST ACTION DATE2025-09-10 (first documented GTM collaboration thread in #partnership-omni)
LAST ACTION DATE2026-03-06 (Savannah: inbound referral offer for Snowflake+dbt work under Omni)
LAST ACTION NOTESChannel shows real partner momentum: Eden + LMNT execution threads, Max actively staffing demos/SE support, and Savannah offering a direct referral. Also surfaced enablement friction from Eden migration (Blobby whole-workbook recreation quality + dashboard filter layout constraints).
NEXT ACTION NOTES(1) Follow up with Max on current open opps and classify each as 2-week pilot vs 4-8 week implementation. (2) Follow up on Savannah referral with qualification checklist + owner + next meeting date. (3) Convert Eden migration learnings into an AE-facing “what to expect” addendum in the one-pager. (4) Close certification loop and record certified names in this file.
BLOCKERSCertification still treated as a prerequisite for broader implementation pull-through; no centralized rep list yet (only thread-based engagement)

3. Partner Qualification

FieldValue
ICP MATCHYes
ACCOUNTS NAMEDElements, Eat in Health (+ add 1+ net-new target accounts as pipeline builds)
INTRO MECHANISMOmni AEs / co-sell; goal: referrals as implementation partner on qualified deals
ECONOMICSDefault implementation track is fixed-scope 5-8 weeks (Omni Zero-to-One) with optional add-ons; 2-week pilot only when scope/access are tightly bounded

4. 90-Day Activation Plan

FieldValue
90D GOALBy 2026-07-06: Publish a joint Omni + Brain Forge rep-facing motion that separates a 2-week value pilot from a 4–8 week implementation track; run 4+ qualified co-sell conversations with Omni AEs on ICP accounts; close ≥1 joint pilot or implementation SOW; and earn ≥1 net-new intro where Omni positions Brain Forge as the implementation partner (not one-off heroics).
90D START DATE2026-04-07 (adjust to actual “day zero” after Max sync if needed)
90D STATUSOn Track (pending first follow-up execution)

Summary:

Mirror the Snowflake control center discipline for Omni: one place for goals, contacts, rep tiers, and assets. In the next ninety days, make it easy for Omni reps to refer Brain Forge by fixing the timeline mismatch — short Omni trials stay credible when scope is bounded; heavier discovery and build use an explicit implementation track with shared qualification. Success is velocity + trust: faster right motions, not pretending every deal fits two weeks.


5. Relationship Context

FieldValue
KEY CONTACT NAMEMax Smith
KEY CONTACT ROLEOmni AE — primary execution lead on Eden + LMNT threads
ORIGIN STORYStarted as GTM/content collaboration, then moved into active co-sell execution with dedicated Eden/LMNT threads and referral flow via Omni team
RELATIONSHIP NOTESAdditional champions are active: Jon Knapp (partner lead), Savannah English (referral source), Becca (certification/training), Kylee (SE support). Relationship quality is high; now needs repeatable packaging and quantified outcomes.

6. Rep Engagement Summary

FieldValue
REPS BRINGING DEALS2 (Max Smith, Savannah English)
REPS ENGAGED4+ (Max, Jon, Savannah, Kylee)
LEADS GENERATED1 confirmed inbound referral (2026-03-06) + prior LMNT/CTA/Eden motion intros
CLOSED/WON DEALSTBD

Rep Notes (by tier):

  • Tier 1 – Reps Bringing Deals: Max Smith; Savannah English (explicit referral motion)
  • Tier 2 – Engaged Reps: Jon Knapp, Kylee Schroth, Becca (active enablement/certification and field support)
  • Tier 3/4 – Cold/Stale: Broader Omni field unknown; still need intentional 10-15 rep list per rep-engagement playbook

7. Total Activity Tracking

FieldValue
FIRST TOUCH DATE2025-09-10
LAST ENGAGEMENT DATE2026-03-06
DAYS SINCE LAST TOUCH~31 (as of 2026-04-06)
MESSAGES SENTHigh-touch execution thread activity across Eden/LMNT/CTA + enablement follow-ups
SALES ASSETS SENTTrial-vs-implementation outline; onboarding/training materials; AI enablement + certification resources
CO-MARKETING ASSETS CREATEDDraft LinkedIn partner posts; Shoptalk/event concept doc; shared GTM collaboration doc for LMNT pilot accelerator
CALLS BOOKEDMultiple demos and syncs (Eden + LMNT threads), including SE-supported sessions
PROPOSAL SENTLMNT pilot/accelerator doc shared 2026-03-02; other proposal links per deal in HubSpot
IN-PERSON VISITNo confirmed in this file yet

8. Partner Status & Pipeline Stages

Partner Status

FieldValue
LATEST COMPLETED PHASEPHASE 2: Meeting Booked (ongoing deal collaboration; formal partner enablement in flight)

Partner Pipeline Stages

FieldValue
PHASE 1: To-DoFill HubSpot partner record; confirm Max + enablement owner; set 90D start date on first sync
PHASE 2: Meeting BookedStrong: recurring thread collaboration, demos, and Omni SE support for active accounts
PHASE 2.5: Proposal SentIn progress: LMNT pilot accelerator doc shared for feedback; track acceptance + resulting SOW links
PHASE 3: Contract SignedPer-deal
PHASE 4: Post Closed-Won StartHandoff template TBD (align with Snowflake post-close pattern)
HUBSPOT LINKTBD (backfill Eden, LMNT, CTA, referral records + timestamps)
PARTNER NOTION HUBTBD
PROPOSAL FILEPer-deal links (HubSpot source of truth)
CONTRACT FILEPer-deal links (HubSpot source of truth)
PARTNER DRIVEknowledge/sales/partners/Omni/

9. Materials & Assets Overview

Certification & Training

ResourceDescriptionLink
Certification how-toInternal steps, submission links, who should certifycertification-how-to.md
Quickstart guideTemplate materials, rules of engagement, Quickstart overviewomni-quickstart-guide.md
Latest PDF & training guidePartner Portal (Euler) – reach out if no accessContact Peter Whitehead or Becca Bruggman

Rep Enablement

AssetTypeStatusLink
Trial vs. implementation one-pagerOutline → designed one-pager + AE email snippetDrafttrial-vs-implementation-one-pager-outline.md
Qualification checklistTable in outline — extract to slide/deckDraftSame as above
Eden migration learnings addendumAE-facing “what to expect” from real implementation frictionTODOAdd to one-pager appendix
Next-step message kitCopy-paste outreach for Max, referrals, certs, and opsIn usenext-step-message-drafts.md
Weekly channel update playbookOmni-style sample log + Brainforge weekly Slack templateIn useweekly-omni-channel-update-playbook.md

Partner-Facing

AssetTypeStatusLink
Omni quickstart materialsPartner onboarding and implementation guardrailsIn useomni-quickstart-guide.md
Omni certification pathPartner readiness and certification opsIn usecertification-how-to.md

Internal

AssetTypeStatusLink
Partner control center (this file)Single source of truthIn usePARTNER_CONTROL_CENTER.md

Customer-Facing / Co-Marketing

AssetTypeStatusLink
Omni Zero-to-One offerCustomer-facing framing for implementation trackIn useoffer.md
Omni Zero-to-One implementation planTimeline and scope (5-8 weeks)In useimplementation-plan.md
Shoptalk Omni event briefCo-marketing/event conceptDraftshoptalk-vegas-omni-event-research.md

10. Active Motions & Pipeline

[List current motions that involve this partner – deals, events, campaigns – with owner, stage, and how they map to LEADS GENERATED / CLOSED/WON.]

  • Motion 1 — Referral conversion: Owner: [you]; stage: active; convert Savannah’s 2026-03-06 referral into qualified call + owner + close plan.
  • Motion 2 — Rep-enablement packaging: Owner: GTM; stage: build; ship one-pager + checklist + Eden “implementation friction” addendum so AEs set scope correctly.
  • Motion 3 — LMNT pilot standardization: Owner: [you] + delivery; stage: in progress; operationalize the LMNT pilot accelerator doc into reusable template language.
  • Motion 4 — Certification closure: Owner: [you] + delivery leads; stage: at risk; confirm platform/quickstart certification submissions and record certified coverage.
  • Motion 5 — CRM hygiene: Owner: ops; stage: pending; backfill HubSpot opportunity/referral links (Eden, LMNT, CTA, new referral).

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)
QualificationStrong ICP fit; named joint accounts4
EngagementMultiple active Omni stakeholders and clear responsiveness4
VelocityBetter than baseline; still loses time when scope is ambiguous3
OutcomesOne confirmed recent referral + active pilot motions3

Overall

  • Total Score (provisional): 14 / 20
  • Current Tier (Tracker): Gold
  • Recommendation: Maintain Gold while executing 90D plan; promote when ≥3 AEs have used the one-pager and ≥1 net-new referral lands from Omni

12. Notes & Open Questions

  • Snowflake parity: Treat this file like Snowflake/PARTNER_CONTROL_CENTER.md — same sections filled on a steady cadence (dates, rep tiers, HubSpot links, last/next action).
  • Cycle-length narrative: Longer cycles on Elements / Eat in Health = implementation scope, not Omni or Brain Forge “being slow.” Productize that story in the trial vs. implementation outline.
  • Open: Which Omni contacts are officially in “rep enablement owner” role for rollout beyond current champions?
  • Execution signal from Slack: Max explicitly said certifications help him pull Brainforge into future implementation services. This should be treated as a gating risk until closed.
  • Product/implementation learnings to codify: Eden migration thread showed specific friction (whole-workbook Blobby generation quality; manual chart-by-chart assembly) and a workaround path (topic-first + standalone chat + advanced layout flag/docs). Package this into pre-sales scoping language.
  • Playbook gap to close: We still need a 10-15 rep target list (Rep Engagement Playbook Phase 1) and explicit tier movement tracking from real interactions.

13. Next 30-Day Playbook Execution (what to drive next)

  1. Week 1 - Lock the motion
    • Send Max follow-up with one-pager draft and ask to classify 1-2 active opps by motion type.
    • Define day-14 success criteria for pilot opps (3-5 canonical questions answered in Omni).
  2. Week 2 - Build rep surface area
    • Identify 5-10 Omni reps to target (warm first), then launch account-brief outreach cadence.
    • Move reps into Tier 1/2/3 based on response and intro behavior.
  3. Week 3 - Capture conversion evidence
    • Document first intro or deal assist pattern that worked (brief, call support, or proactive account research).
    • Convert that into a reusable AE talking point block.
  4. Week 4 - Scale what worked
    • Double down on reps/motions producing intros; deprioritize stale reps.
    • Update scoring, 90D status, and next action notes with quantified changes.