Brainforge Knowledge

partnership-manager-playbook-slack

6 min read

Partnership manager playbook (Slack reminders)

Purpose: Repeatable activities and Slack-ready reminder copy so the Snowflake relationship keeps moving—consumption story, partner manager + AE enablement, proof artifacts, and champion propagation (aligned with the hyperscaler partner approach discussed with Chris Verner, Apr 2026).
Default owner: Uttam (partnerships + Snowflake account motion). Adjust @mentions if you hand off.
Repo: Snowflake approach · Control Center · AE brief v1 · Consumption snapshot
Last updated: 2026-04-07

1. Slack: internal vs external

ChannelRoleWho’s in it
#sales-partnershipsOnly internal Brainforge channel for partnership ops: Snowflake cadence reminders, checklist threads, and feedback that should flow back into Cursor / repo.Brainforge only
Partner channels (e.g. #snowflake-partners, vendor shared Slack)External-facing — partner AEs, CSMs, etc. Do not use these for internal automation or noisy reminder spam.Brainforge + partner

All scheduled alerts, Workflow Builder posts, and /remind targets for this playbook go to #sales-partnerships.

2. Slack home base (setup)

SettingValue
Internal channel#sales-partnerships
Who runs the playbookUttam (partnerships manager responsibilities for Snowflake first; same pattern for other hyperscalers later)
HubSpotLog notes/tasks via partner-hubspot-ops when activities happen (Cursor agent or manual CLI). Manual: cd tools/hubspot-api-service && npm run partner-hubspot -- …

3. Feedback loop: Slack thread → Cursor → repo → HubSpot

Goal: Snowflake first; then you refine the playbook from real use. Internal process:

  1. Reminder posts land in #sales-partnerships (Monday / Wednesday / monthly / quarterly).
  2. Reply in the thread with what actually happened (e.g. “Connie replied—use template v2”, “EY blocked—new AE”) or paste a summary for the agent.
  3. In Cursor, ask the agent to apply changes to:
  4. HubSpot: When an activity is real (call, email, PM touch), use partner-hubspot-ops to add note or task on the Snowflake company/contact—not a substitute for updating the Control Center.

Partner hub in Cursor = knowledge/sales/partners/ (Control Centers, playbooks, ops). Slack is the nudge + conversation; the repo stays the durable source of truth for Rico’s digest and GTM.

4. Activity list (what “good” looks like)

Use this as the checklist behind every reminder.

#ActivityWhy (Chris-aligned)Typical frequency
A1Champion AE touch — message or call at least one Snowflake AE who already knows us (or should). Ask for one intro to another AE when rapport allows.AE network propagation; not only your current book.Weekly
A2Partner Manager (PM) ping — short note or async: traction, co-sell, account mapping, official AE one-pager template.PM unlocks internal forwarding + template.Weekly (light) + quarterly deep
A3Consumption snapshot — update snowflake-customer-consumption-snapshot.md if any account had a milestone, new numbers, or SPN registration.Hyperscalers optimize on attributed consumption.Monthly or on milestone
A4AE brief — refresh ae-brief-snowflake-v1.md when certs, customers, or rollup consumption changes.One forwardable story for AEs.Monthly or when inputs change
A5Cert / accreditation inventory — update counts on the brief; note gaps.Proof of bench depth.Monthly
A6Proof artifact — progress one case study, ROI one-pager, or post-win write-up for PM/AE distribution.Internal momentum inside Snowflake.Monthly
A7Control Center — update PARTNER_CONTROL_CENTER.md §2 last/next action after material moves.Repo stays source of truth for digest + team.Weekly or after key calls
A8Quarterly PM session — calendar working session (or dinner/lunch): traction, co-sell, template, brown-bag for AEs.Dedicated PM face time.Once per quarter
A9AWS parallel (if in scope) — one line in snapshot / brief if joint AWS + Snowflake customers matter this quarter.Reinforces cloud story.Quarterly or as needed

5. Alert cadence (target: #sales-partnerships)

WhenFocusMaps to
Monday ~9:00 localWeek kickoff: AE + PM + repoA1, A2 (light), A7
Wednesday ~14:00Proof + numbersA3, A4, A5, A6
Last Friday of monthRollup + brief refreshA3, A4, A5, A6
Quarterly (first week of quarter)PM deep dive + schedule A8A8, optional brown-bag follow-up

Tune times to your timezone; keep Monday + monthly as minimum if you need to reduce noise.

6. Copy-paste Slack messages (post to #sales-partnerships)

Replace @uttam with the real Slack mention for Uttam.

6.1 Monday — Snowflake weekly push

:snowflake: *Snowflake partner — weekly checklist* (@uttam)

*AEs*
• Touch ≥1 champion AE; if healthy, ask for *one intro* to another AE in-region or adjacent pod.

*Partner manager*
• One short async ping: traction, co-sell, account mapping — or confirm *official AE one-pager template*.

*Repo*
• If anything moved: update `PARTNER_CONTROL_CENTER.md` §2 (last/next action).

_Thread: what you did + blockers → we’ll fold into Cursor / playbook._

6.2 Wednesday — Numbers & proof

:snowflake: *Snowflake — consumption & brief* (@uttam)

• *Snapshot:* any new metrics or SPN activity? → `snowflake-customer-consumption-snapshot.md`
• *AE brief:* certs / customers / rollup still accurate? → `ae-brief-snowflake-v1.md`
• *Proof:* one step on a case study or ROI blurb for PM/AE send this month.

_No new numbers = reply “no change” in thread so we know someone looked._

6.3 Monthly — Rollup (last Friday)

:snowflake: *Snowflake — monthly rollup* (@uttam)

• Roll up consumption line for the AE brief (even if “TBD” — note status).
• Cert counts on brief current?
• *Next month:* which *one* proof artifact will we finish?

6.4 Quarterly — Partner manager working session

:snowflake: *Snowflake — quarterly PM session* (@uttam)

Book *one* working session with Snowflake Partner Manager this quarter:
• Traction + blockers
• Co-sell & account mapping
• AE one-pager template / feedback on our v1 brief
• Optional: *brown bag* for AEs — topic + date?

Agenda stub: `approach-hyperscaler-partner-ops.md` §3.1

7. Integrating alerts into #sales-partnerships

7.1 Scheduled messages (built-in)

  1. Open #sales-partnerships.
  2. Compose each message from §6 → Schedule for later → Repeat weekly / monthly if your Slack plan supports it.

7.2 Slash reminders (/remind)

GoalExample (adapt channel + time)
Weekly Monday/remind #sales-partnerships every Monday at 9:00am with shortened §6.1
Monthly/remind #sales-partnerships on the last Friday of every month at 3:00pm with §6.3

7.3 Workflow Builder

  1. Create workflow (e.g. Snowflake weekly partnerships checklist).
  2. Trigger: Schedule → weekly Monday 9:00 (separate workflows for Wed / monthly).
  3. Step: Send message to #sales-partnerships with §6.1 body.
  4. Optional: DM @uttam in addition.

7.4 Pin + bookmark

  • Pin the playbook link or a Canvas with paths under knowledge/sales/partners/.
  • Bookmark the GitHub folder for the partner hub in Cursor.

8. Avoid duplicate noise

If you already have…Do this
Rico’s Thursday digest (weekly-partnerships-digest-PRD)Keep Monday/Wednesday Snowflake reminders action-oriented in #sales-partnerships; Thursday stays cross-partner rollup.
HubSpot tasksMirror only material touches via partner-hubspot-ops; Slack is the nudge, CRM is the system of record for customer/partner timelines.

9. One-line link for channel topic / bookmark

Partner hub (Cursor): knowledge/sales/partners/ · Snowflake PM playbook: ops/partnership-manager-playbook-slack.md

10. Change log

DateChange
2026-04-07Initial playbook: Chris-aligned activities, Slack copy, integration options; owner Uttam.
2026-04-07Internal channel = #sales-partnerships only; external partner channels out of scope for alerts. Slack→Cursor→HubSpot loop; HubSpot via partner-hubspot-ops.

Graph View

Backlinks