Brainforge Knowledge

THURSDAY-BRIEF-SAMPLE

6 min read

Sample Thursday Partnerships Brief (full — every partner, sorted by tier)

Purpose: Full Thursday brief Rico drafts every week and publishes to a Google Doc (shared link to the team). Every partner is listed, sorted Gold → Silver → Bronze → Calibration → Deprioritize. Movement expectations by tier; next actions assigned to specific people (Robert, Uttam). Rico uses the Partner Playbook and Control Centers to draft this.

Where it lives: Google Doc. Rico publishes the brief there each Thursday and shares the doc link (e.g. in Slack or email) so the team can open it; the doc format transfers cleanly and doesn’t rely on Slack formatting.

Cadence by tier (from playbook):

  • Gold — moving every week
  • Silver — moving biweekly
  • Bronze — moving monthly
  • Calibration — calibrating (running first 90-day test, answering “should this be a partner?”)
  • Deprioritize — no new investment; light touch only

Thursday brief content (for Google Doc)

Rico publishes this to a Google Doc each Thursday and shares the link with the team.

Partnerships brief — Week of Mar 7 (Thursday)

Synthesized from repo: knowledge/sales/partners. Full digest: [link].

Cadence reminder: Gold = weekly movement | Silver = biweekly | Bronze = monthly | Calibration = calibrating (90D test in progress).

GOLD (move every week)

Snowflake

  • Movement this week: No repo update.
  • Next action: Collect account lists from Snowflake; create high-value rep materials + Three Whys one-pager; nurture SRs for LMNT and Insomnia Cookies.
  • Blocker: AEs ghosting.
  • Robert — Own rep nurture and account-list ask. Uttam — Support materials/certifications if needed.

Omni

  • Movement this week: No repo update.
  • Next action: [Update Control Center with next action when known.]
  • Robert — Define and document next action in Control Center; keep Gold cadence (touch this week).

SILVER (move biweekly)

Mixpanel

  • Movement this week: Yes — Greg meeting with Michael to highlight the value of MCP.
  • Next action: Follow up after Greg/Michael meeting; document outcome and next step in Control Center.
  • Robert — Silver = biweekly; ensure next touch/action is documented in Control Center.

Amplitude

  • Movement this week: Yes — Back and forth with Hugo; launching 3-month Amplitude Plus for free landing page for Brainforge; planning content campaign around it. Shared leads (Pendo, PostHog) and comparing how other partners are reacting to current sales — insight: possible pricing issue; companies are delaying platform commitments because they’re unsure how AI advancements will impact the tool they lock into.
  • Next action: Run co-marketing content play (Amplitude Plus for free landing page + content campaign).
  • Robert — Own co-marketing content play with Hugo; document in Control Center.

BRONZE (move monthly)

Talisma • Movement this week: No repo update. • Next action: [Update Control Center with next action when known.] • @Robert — Bronze = monthly; next touch due within the month; update Control Center when you move.

Polytomic • Movement this week: No repo update. • Next action: [Update Control Center with next action when known.] • @Robert — Bronze = monthly; update Control Center when you move.

MotherDuck • Movement this week: No repo update. • Next action: [Update Control Center with next action when known.] • @Robert — Bronze = monthly; update Control Center when you move.

CorralData • Movement this week: No repo update. • Next action: [Update Control Center with next action when known.] • @Robert — Bronze = monthly; update Control Center when you move.

CALIBRATION (calibrating — 90D test in progress)

OpenBB

  • Movement this week: Yes — Control Center + formalization doc updated.
  • Next action: Share Snowflake account ID with Ihsan; stand up OpenBB install; create shared Slack channel; ID 3–5 pilot FI accounts.
  • Robert — Share account ID with Ihsan; create Slack channel; own pilot account list. Uttam — Own OpenBB install in our Snowflake account (README/admin commands).

GSV • Movement this week: No repo update. • Next action: [Define next action in Control Center]. 90D goal: 3–5 GSV-intro’d convos + 1 co-marketed asset by 2026-06-01. • @Robert — Calibration = run the first 90-day test; document next step and owner in Control Center.

Glimpse • Movement this week: No repo update. • Next action: [Update Control Center with next action when known.] • @Robert — Calibration = answer “should this be a partner?”; document next step in Control Center.

DEPRIORITIZE (light touch only)

Superposition — No new investment. Light relationship only if helpful. OneSource — No new investment. Light relationship only if helpful. Freshpaint — No new investment. Light relationship only if helpful.

Ask: If you’re tagged, please take the next action and update the Control Center (or comment here) so next week’s brief is accurate. Gold partners should show movement every week; Silver biweekly; Bronze monthly; Calibration = clear next step toward 90D test.

Rico drafting instructions (from playbooks)

When drafting the Thursday brief, Rico:

  1. Read every Control Center under knowledge/sales/partners/[PartnerName]/PARTNER_CONTROL_CENTER.md.
  2. Sort partners by tier (Section 1 PRIORITY or Section 11 Current Tier): Gold → Silver → Bronze → Calibration → Deprioritize.
  3. Apply cadence (from Partner Playbook § Partner Program Tiers):
    • Gold = movement expected every week
    • Silver = biweekly
    • Bronze = monthly
    • Calibration = calibrating (90D test; next step should be clear)
    • Deprioritize = list only; no assignment
  4. Check repo for movement: For each partner, see if their folder had any commits in the last 7 days. Set “Movement this week: Yes/No repo update.”
  5. Pull next action and blockers from each Control Center §2. If blank, write “[Update Control Center with next action when known.]”
  6. Assign an owner for every non-Deprioritize partner. Assign Robert for GTM/relationship/rep nurture and Uttam for technical/Snowflake/install work when the Control Center or next action implies it (e.g. OpenBB install → Uttam; Snowflake rep nurture → Robert). Default to Robert when owner is unclear. (In a Google Doc, use names; if the link is shared in Slack, people can @-mention from there.)
  7. Publish full digest to ops/digests/YYYY-MM-DD-weekly-partnerships-digest.md and link it at the top of the brief.
  8. Publish the brief to a Google Doc each Thursday and share the doc link with the team (e.g. in Slack or email) so everyone can open it. The brief lives in the doc; no need to paste the full message into Slack.

Graph View