PRD: Weekly Partnerships Digest

Purpose: A weekly partnerships digest synthesized from updates in the GitHub repo (knowledge/sales/partners). The team works in the partnerships framework and updates Control Centers as they go; the digest reflects what’s in the repo and what didn’t move. One owner: Rico (EA). Rico synthesizes the update, fills in blanks when there was no partner movement, and on Thursday sends a message to everybody if cadence wasn’t hit. Audience: Team (consumers of digest); Owner (sole): Rico (EA)
Status: Draft for review
Last updated: 2026-03-05

1. Problem & Goals

Problem

Partner state lives in the repo (Control Centers, meetings, engagement) in the partnerships Cursor environment. If the team doesn’t update the repo, we don’t know what moved.
There’s no single weekly view driven by repo state: what changed, who’s overdue, who had no movement when they should have.
Cadence (next actions, updates) can slip without one person responsible to synthesize and nudge.

Goals

Digest is synthesized from the repo — Control Centers and (optionally) recent changes in knowledge/sales/partners/ — not from manual pulls from HubSpot/Slack/email.
Team uses the framework — everyone works out of the partnerships structure and updates the repo; the digest reflects that.
Rico is the single owner — no shared “GTM or AI team” run; Rico produces the digest and enforces cadence.
Blanks are filled — when there was no partner movement that should have happened, Rico flags it in the digest.
Thursday cadence nudge — if we weren’t hitting cadence (overdue next actions, no updates where expected), Rico sends a message to everybody on Thursday.

2. User Stories

Who	Need	So that
Rico (EA)	One clear process: read repo → synthesize digest → fill blanks → Thursday message if cadence missed	I own the whole flow and don’t depend on others to feed me data from HubSpot/Slack/email.
Team	A weekly view of what’s in the repo: who moved, who’s overdue, who had no update	We can see partnership state and fix gaps (update Control Centers) before or after the nudge.
Robert / decision maker	At-a-glance view from repo state: who’s on track, who’s at risk, what’s next	I can prioritize without chasing multiple tools.

3. Scope

In scope

Primary data source: GitHub repo — specifically knowledge/sales/partners/ (Control Centers, partner folders, any updates the team makes in the partnerships Cursor environment). The digest is synthesized from:
- Current content of each PARTNER_CONTROL_CENTER.md (e.g. LAST ACTION, NEXT ACTION, BLOCKERS, 90D STATUS).
- Recent repo updates (e.g. which partner folders/files changed in the last 7 days via git history) so we know “who moved” vs “no recorded movement.”
Weekly digest document produced by Rico: rollup (partners needing action, 90-day summary, “no movement” list) + per-partner blocks pulled from Control Centers + “Housekeeping” (blanks: overdue, no update).
Rico as sole owner: Rico runs the synthesis, fills in blanks, and sends the Thursday message to everybody when cadence wasn’t hit (overdue next actions or expected movement that didn’t happen).
Thursday: The cadence-enforcement message goes out on Thursday (not “by end of week”).

Out of scope (for v1)

Pulling from HubSpot, Slack, or email as required inputs to the digest. Repo is the source; Rico may optionally add a line or two from other tools if something critical is missing, but the process does not depend on it.
Multiple people “running” the digest (GTM, AI team). Only Rico.
Digest for non-partnerships GTM.

4. Data Source: Repo (knowledge/sales/partners)

The digest is repo-driven.

What	Where in repo	How it’s used
Current partner state	Each `knowledge/sales/partners/[PartnerName]/PARTNER_CONTROL_CENTER.md`	Rico (or a script) reads each Control Center and pulls: LAST ACTION DATE/NOTES, NEXT ACTION DATE/NOTES, BLOCKERS, 90D STATUS, and optionally §6–7 (rep/deal counts). This is the synthesis of “what’s true today.”
Who moved this week	Git history for `knowledge/sales/partners/` (e.g. last 7 days)	List commits or changed files under each partner folder. Partners with no changes in the last 7 days but with a NEXT ACTION DATE in the past (or due this week) → “No recorded movement” / blanks Rico fills in.
Active partners	Partner folders present under `knowledge/sales/partners/` (e.g. OpenBB, Snowflake, Omni, …)	List of partners to include. “Active” = has a Control Center and is not Deprioritize (from Control Center §1 or tracker).

Sync principle: The team is expected to work in this repo and update Control Centers when they take actions or when next actions come due. The digest does not require Rico to log into HubSpot, Slack, or email; it is synthesized from what’s already in the repo. If nothing was updated, the digest and Thursday message make that visible so the team can fix it.

5. Digest Structure

5.0 Tier order and cadence (every partner, sorted)

The digest and Thursday brief list every partner, sorted by tier (from Partner Playbook § Partner Program Tiers):

Gold — move every week
Silver — move biweekly
Bronze — move monthly
Calibration — calibrating (first 90-day test in progress; next step should be clear)
Deprioritize — light touch only; list but no assignment

Gold movement is highest priority; Silver next; Bronze and Calibration per playbook. Rico uses Section 1 (PRIORITY THIS WEEK) or Section 11 (Current Tier) in each Control Center to sort.

5.1 Rollup

Week of: [date range]
Partners needing action: Partners where NEXT ACTION DATE (from Control Center) is in the past or this week.
No recorded movement this week: Partners that had no changes in the repo (no commits touching their folder) in the last 7 days but had an overdue or due-next next action. (Blanks Rico fills in.)
90-day status summary: Count by 90D STATUS across Control Centers: On Track / At Risk / Delivered / Failed / Not Started.
Movement this week (from repo): Short list of which partner folders/files were updated in the last 7 days (from git). Optional one-line “Focus this week” if known from last digest or a note in repo.

5.2 Per-partner block (from Control Centers)

For each active partner (folder with a Control Center), one block. All fields come from current Control Center content (repo).

Field	Source in repo
Partner name	Folder name / Control Center §1
90D status	Control Center §4
Last action	Control Center §2 LAST ACTION DATE + LAST ACTION NOTES
Next action	Control Center §2 NEXT ACTION DATE + NEXT ACTION NOTES
Blockers	Control Center §2 BLOCKERS
Rep / deal momentum (optional)	Control Center §6 (REPS BRINGING DEALS, LEADS GENERATED, etc.)

No “How messages are going” or “Slack/Email this week” required from external tools; if the team has captured that in the Control Center or in meeting notes in the repo, it can be summarized. Otherwise the digest stays repo-only.

5.3 Housekeeping (blanks)

Overdue next actions: List partners where NEXT ACTION DATE is in the past and (if detectable) no update in repo this week.
No update where expected: Any partner the team or Rico had flagged as “should have moved” but no commits in their folder. Rico fills this in so the Thursday message can reference it.

5.4 Thursday brief: full message, assignments (no generic nudge)

The Thursday message is a full brief of every partner’s activity, not only a “go nudge” list. Rico drafts it using the partner playbooks and Control Centers:

Content: Every partner listed, sorted Gold → Silver → Bronze → Calibration → Deprioritize. For each (except Deprioritize): movement this week (from repo), next action, blockers if any, and assigned owner.
Assignments: Each next action is assigned to a specific person so the team can push forward. Tag @Robert for GTM/relationship/rep nurture and @Uttam for technical/Snowflake/install work when the Control Center or next action implies it. Default to @Robert when owner is unclear. Deprioritize partners are listed with no tag.
Cadence reminder: At the top, remind the team: Gold = weekly, Silver = biweekly, Bronze = monthly, Calibration = calibrating.
Ask: If you’re tagged, take the next action and update the Control Center (or comment) so next week’s brief is accurate.

Sample full brief: THURSDAY-BRIEF-SAMPLE.md.

6. Success Criteria

Digest is produced from repo only — no dependency on Rico manually pulling from HubSpot/Slack/email for the core content.
Every partner is listed in the digest and Thursday brief, sorted Gold → Silver → Bronze → Calibration → Deprioritize.
Tier cadence is clear: Gold = weekly, Silver = biweekly, Bronze = monthly, Calibration = calibrating.
Next actions are assigned — each partner’s next action has an owner (e.g. @Robert, @Uttam); no generic “go nudge” without a named owner.
Rico drafts the Thursday brief using the partner playbooks and Control Centers; the brief is the full message of partner activity, not only a nudge when cadence is missed.
Rico can synthesize the digest in a reasonable time (target: under 45 min) by reading Control Centers and (optionally) running a small script or git log for knowledge/sales/partners/ for the last 7 days.
Blanks are explicit — “No recorded movement” and “Overdue” are visible so the team knows what to update.
Thursday brief goes out every Thursday to the agreed channel (e.g. gtm or partnerships).
Single owner: Only Rico is responsible for producing the digest and sending the Thursday brief.

7. SOP for Rico: Synthesize Digest from Repo + Thursday Nudge

Cadence: Weekly. Thursday = day Rico sends the cadence message to everybody if we weren’t hitting cadence. Digest can be produced Thursday (before the message) or Friday; the nudge is Thursday.

Rico is the only owner. No one else is required to “run” this.

Step 1: List active partners from repo (5 min)

In the repo, list directories under knowledge/sales/partners/ that contain a PARTNER_CONTROL_CENTER.md (e.g. OpenBB, Snowflake, Omni, Talisma, …). Exclude template/draft folders if any.
Optionally read each Control Center §1 to exclude “Deprioritize” so only active partners are in the digest.

Step 2: Pull current state from each Control Center (15–20 min)

For each active partner, open knowledge/sales/partners/[PartnerName]/PARTNER_CONTROL_CENTER.md.
Copy or summarize into the digest draft:
- 90D STATUS (Section 4)
- LAST ACTION DATE and LAST ACTION NOTES (Section 2)
- NEXT ACTION DATE and NEXT ACTION NOTES (Section 2)
- BLOCKERS (Section 2)
- Optionally: rep/deal counts from Section 6.

All of this is from the repo only.

Step 3: Detect “movement” and “no movement” from git (10 min)

In the repo, run something like: git log --since="7 days ago" --name-only -- knowledge/sales/partners/ (or use GitHub UI / script). See which partner folders (or files) were touched in the last 7 days.
In the digest:
- Movement this week: List partners that had commits touching their folder/files.
- No recorded movement: Partners that (a) have NEXT ACTION DATE in the past or due this week, and (b) had no commits in their folder in the last 7 days. These are the blanks — Rico fills these in so the team (and Thursday message) can act.

Step 4: Build rollup (5 min)

Partners needing action: From Step 2, list every partner where NEXT ACTION DATE is today or in the past.
90-day status summary: Count 90D STATUS values from Step 2.
Housekeeping: List overdue next actions and “no update this week” for partners that should have moved (from Step 3).

Step 5: Publish digest (5 min)

Save the digest to: knowledge/sales/partners/ops/digests/YYYY-MM-DD-weekly-partnerships-digest.md (use the Thursday or Friday date for that week).
Commit and push, or paste into shared doc if the team uses one. Share link in Slack (e.g. gtm or partnerships) so the team can read it.

Step 6: Draft and send the full Thursday brief (every partner, with assignments)

On Thursday, Rico drafts the full partnerships brief using the Partner Playbook and Control Centers (see THURSDAY-BRIEF-SAMPLE.md for structure and §5.4 for content).
Include every partner, sorted Gold → Silver → Bronze → Calibration → Deprioritize. For each non-Deprioritize partner: movement this week (from repo), next action, blockers, and assigned owner (tag @Robert or @Uttam as appropriate; default @Robert when unclear).
Cadence reminder at top: Gold = weekly, Silver = biweekly, Bronze = monthly, Calibration = calibrating.
Ask: If you’re tagged, take the next action and update the Control Center so next week’s brief is accurate.
Rico sends this full brief every Thursday to the agreed channel (e.g. gtm or partnerships). It is the weekly full message of partner activity, not only a nudge when cadence is missed.
Thursday is the day the brief goes out. Not “by end of week” — Thursday.

Step 7: Fill in blanks in the digest (ongoing)

Whenever Rico sees that a partner should have had movement (e.g. next action was due, or a standing cadence like “weekly check-in”) but there’s no update in the repo, that goes in:
- The digest under No recorded movement and Housekeeping, and
- The Thursday message if it’s Thursday.

Rico does not have to chase individuals for updates; the process is: synthesize from repo → show gaps → Thursday message to everybody when there are gaps.

8. Single Owner: Rico

Rico is the only person in charge of:
- Synthesizing the weekly digest from the repo.
- Filling in blanks (no movement, overdue).
- Sending the Thursday message to everybody when cadence wasn’t hit.
The team is responsible for:
- Using the partnerships framework and updating the repo (Control Centers, meeting notes, etc.) as they work.
- Reacting to the digest and the Thursday message by updating Control Centers or taking next actions.
No shared “GTM or AI team” execution of this process. One owner: Rico.

9. Template: Digest document

Use this structure each week. All per-partner content comes from Control Centers (repo).

# Weekly Partnerships Digest — Week of [YYYY-MM-DD]
 
*Synthesized from repo: knowledge/sales/partners/*
 
## Rollup
 
- **Partners needing action:** [Names where NEXT ACTION DATE is past or this week]
- **No recorded movement this week:** [Partners with overdue/due next action but no repo updates in last 7 days]
- **90-day status:** On Track [n], At Risk [n], Delivered [n], Failed [n], Not Started [n]
- **Movement this week (from repo):** [Which partner folders/files had commits in last 7 days]
- **Focus this week (optional):** [One line if known]
 
---
 
## Per-partner updates
 
### [Partner 1 name]
 
- **90D status:** [from Control Center §4]
- **Last action:** [§2 LAST ACTION DATE + NOTES]
- **Next action:** [§2 NEXT ACTION DATE + NOTES]
- **Blockers:** [§2 BLOCKERS]
- **Rep / deal momentum (optional):** [§6]
 
---
 
### [Partner 2 name]
 
[Same structure — all from Control Center]
 
---
 
## Housekeeping
 
- **Overdue next actions:** [List]
- **No update where expected:** [List]
 
---
 
## Links
 
- [Partner A Control Center](path in repo)
- [Partner B Control Center](path in repo)

10. Dependencies & optional automation

Repo access: Rico has read access to the GitHub repo (or a copy of knowledge/sales/partners/) so they can read Control Centers and run git log (or use GitHub “commits” for that path).
Thursday: Calendar reminder or recurring task for Rico: “Thursday — partnerships cadence check; send message if gaps.”
Optional script: A small script (e.g. in repo or Cursor) that (1) reads all PARTNER_CONTROL_CENTER.md under knowledge/sales/partners/*/, (2) parses NEXT ACTION DATE, LAST ACTION DATE, 90D STATUS, (3) runs git log --since="7 days ago" --name-only -- knowledge/sales/partners/, and (4) outputs a draft rollup + “no movement” list. Rico can then add the per-partner blocks and publish. This keeps the process less human-reliant and still repo-driven.

Partner Playbook
90-Day Activation Playbook
Partner Tracking System
Tracker Final Structure
Partner Folder Structure — Control Center location per partner

Document owner: GTM / Partnerships lead
Sole execution owner: Rico (EA)
Last updated: 2026-03-05

Brainforge Knowledge

Explorer

weekly-partnerships-digest-PRD

PRD: Weekly Partnerships Digest

1. Problem & Goals

Problem

Goals

2. User Stories

3. Scope

In scope

Out of scope (for v1)

4. Data Source: Repo (knowledge/sales/partners)

5. Digest Structure

5.0 Tier order and cadence (every partner, sorted)

5.1 Rollup

5.2 Per-partner block (from Control Centers)

5.3 Housekeeping (blanks)

5.4 Thursday brief: full message, assignments (no generic nudge)

6. Success Criteria

7. SOP for Rico: Synthesize Digest from Repo + Thursday Nudge

Step 1: List active partners from repo (5 min)

Step 2: Pull current state from each Control Center (15–20 min)

Step 3: Detect “movement” and “no movement” from git (10 min)

Step 4: Build rollup (5 min)

Step 5: Publish digest (5 min)

Step 6: Draft and send the full Thursday brief (every partner, with assignments)

Step 7: Fill in blanks in the digest (ongoing)

8. Single Owner: Rico

9. Template: Digest document

10. Dependencies & optional automation

Graph View

Table of Contents

Brainforge Knowledge

Explorer

weekly-partnerships-digest-PRD

PRD: Weekly Partnerships Digest

1. Problem & Goals

Problem

Goals

2. User Stories

3. Scope

In scope

Out of scope (for v1)

4. Data Source: Repo (knowledge/sales/partners)

5. Digest Structure

5.0 Tier order and cadence (every partner, sorted)

5.1 Rollup

5.2 Per-partner block (from Control Centers)

5.3 Housekeeping (blanks)

5.4 Thursday brief: full message, assignments (no generic nudge)

6. Success Criteria

7. SOP for Rico: Synthesize Digest from Repo + Thursday Nudge

Step 1: List active partners from repo (5 min)

Step 2: Pull current state from each Control Center (15–20 min)

Step 3: Detect “movement” and “no movement” from git (10 min)

Step 4: Build rollup (5 min)

Step 5: Publish digest (5 min)

Step 6: Draft and send the full Thursday brief (every partner, with assignments)

Step 7: Fill in blanks in the digest (ongoing)

8. Single Owner: Rico

9. Template: Digest document

10. Dependencies & optional automation

11. Related documentation

Graph View

Table of Contents