Brainforge Knowledge

LISA_PARTNERSHIPS_ONBOARDING_ONE_PAGER

8 min read

Lisa Partnerships Onboarding One-Pager

Purpose: Give Lisa a fast, execution-first tour of Brainforge partnerships operations by translating recent partnership transcripts into mini-guides with direct repo resources and agent skills.

Start Here (10 minutes)

  1. Read knowledge/sales/partners/README.md (canonical partner doc index).
  2. Read knowledge/sales/partners/ops/partnership-ops-system.md (how repo + tracker + digest + CRM fit together).
  3. Open knowledge/sales/partners/Snowflake/PARTNER_CONTROL_CENTER.md and knowledge/sales/partners/Omni/PARTNER_CONTROL_CENTER.md first.
  4. Review .cursor/skills/GTM_SALES_PARTNERSHIPS_QUICKSTART.md and .cursor/skills/GTM_PARTNER_AUTOMATION_CATALOG.md.
  5. For partner-facing Slack, read .cursor/skills/partner-outbound-comms/SKILL.md before drafting any outbound post.

Mini-Guide 1: First 30 Days = Own Snowflake + Omni

Transcript signal:

  • knowledge/clients/unassigned/transcripts/2026-04-27_snowflake_and_omni_partnerships_sync_5c866aac.md
  • knowledge/clients/unassigned/transcripts/2026-04-20_gtm_planning_kickoff_d3a23618.md

What this means operationally:

  • Snowflake and Omni are the first partner lanes to fully own.
  • Prioritize deal flow, certification progress, and repeatable activation patterns.
  • Build from existing relationship graph first (Rolodex + current open threads), then expand.

Repo resources:

  • knowledge/sales/partners/Snowflake/PARTNER_CONTROL_CENTER.md
  • knowledge/sales/partners/Omni/PARTNER_CONTROL_CENTER.md
  • knowledge/sales/partners/Snowflake/approach-hyperscaler-partner-ops.md
  • knowledge/sales/partners/ops/weekly-partnerships-digest-PRD.md

Skills to use now:

  • daily-partnership-refresh
  • partnership-orchestrator-marketing-hub
  • partnership-activity-signals

Done looks like:

  • Weekly pulse row is current for Snowflake + Omni.
  • Next action and blockers are explicit in both Control Centers.
  • One owner, one operating rhythm, one update loop.

Mini-Guide 2: Conference-to-Pipeline Motion (Do Not “Walk the Floor”)

Transcript signal:

  • knowledge/clients/unassigned/transcripts/2026-04-27_snowflake_and_omni_partnerships_sync_5c866aac.md
  • knowledge/clients/unassigned/transcripts/2026-04-22_brainforge_go-to-market_team_sync_994aef3a.md

What this means operationally:

  • Conference strategy is meeting-first, follow-up-fast.
  • Pairing model: one person in conversation, one person owning follow-ups and capture.
  • Treat conference lists/signals as campaign input, then convert to SQLs.

Repo resources:

  • knowledge/sales/partners/ops/partnership-manager-playbook-slack.md
  • knowledge/sales/partners/ops/weekly-partnerships-digest-PRD.md
  • knowledge/sales/partners/ops/digests/README.md

Skills to use now:

  • gtm-campaign-brief
  • gtm-message-sequence
  • partnership-activity-signals
  • hubspot-new-opportunity (when a concrete opportunity is identified)

Done looks like:

  • Every event touchpoint has an attributable follow-up.
  • High-signal contacts are converted into explicit next actions and CRM records.
  • “Met at conference” leads do not sit untriaged past the same week.

Mini-Guide 3: Certifications + Credibility = Partner Leverage

Transcript signal:

  • knowledge/clients/unassigned/transcripts/2026-04-27_snowflake_and_omni_partnerships_sync_5c866aac.md

What this means operationally:

  • Certifications are not side work; they are partner leverage and positioning proof.
  • Keep an active snapshot of who is in-progress, passed, and blocked.
  • Use this alongside current deployment proof points and frontier AI capability examples.

Repo resources:

  • knowledge/sales/partners/Snowflake/PARTNER_CONTROL_CENTER.md
  • knowledge/sales/partners/Omni/PARTNER_CONTROL_CENTER.md
  • knowledge/sales/partners/Snowflake/approach-hyperscaler-partner-ops.md

Skills to use now:

  • partnership-orchestrator-marketing-hub (for weekly visibility)
  • partner-hubspot-ops (to keep partner record narrative and CRM aligned)

Done looks like:

  • Certification status is visible in weekly operating output.
  • Partner asks can be answered with current proof, not memory.

Mini-Guide 4: CRM Hygiene Is a Revenue Workflow

Transcript signal:

  • knowledge/clients/unassigned/transcripts/2026-04-20_gtm_planning_kickoff_d3a23618.md
  • knowledge/clients/unassigned/transcripts/2026-04-22_gtmr_sales_team_transition_sync_61e17395.md

What this means operationally:

  • HubSpot cleanliness directly impacts campaign conversion and partner handoffs.
  • Naming conventions, stage hygiene, and same-day logging are baseline requirements.
  • Use approval gates for batch writes and keep an auditable daily payload.

Repo resources:

  • tools/hubspot-api-service/README.md
  • knowledge/sales/partners/ops/partnership-ops-system.md
  • knowledge/sales/partners/ops/partnership-manager-playbook-slack.md

Skills to use now:

  • partner-hubspot-ops
  • partnership-hubspot-eod-payload
  • daily-partnership-refresh

Done looks like:

  • EOD payload prepared once daily, approved, then executed.
  • Notes/tasks and Control Center state do not drift.
  • Priority partner timelines are always review-ready.

Mini-Guide 5: Partner Slack Updates (Skills You Created)

Transcript signal:

  • knowledge/clients/unassigned/transcripts/2026-04-22_brainforge_go-to-market_team_sync_994aef3a.md
  • knowledge/clients/unassigned/transcripts/2026-04-22_gtmr_sales_team_transition_sync_61e17395.md

What this means operationally:

  • We run two distinct Slack flows: internal ops in #sales-partnerships and partner-facing updates in shared #partnership-* channels.
  • Partner-facing comms should be skill-routed, not ad hoc, and should follow draft/approval/send discipline.

Repo resources:

  • .cursor/skills/partner-outbound-comms/SKILL.md (router/index)
  • .cursor/skills/partner-broadcast-refresh/SKILL.md (one update to many partner channels)
  • .cursor/skills/partner-reply-bundled-asks/SKILL.md (structured replies to numbered partner asks)
  • .cursor/skills/partner-outbound-comms/reference-brainforge-partner-slack-channels.md (channel IDs)
  • knowledge/sales/partners/ops/partnership-manager-playbook-slack.md (internal cadence home)

Skills to use now:

  • partner-outbound-comms (route first)
  • partner-broadcast-refresh
  • partner-reply-bundled-asks
  • partner-call-recap-outbound
  • partner-event-ops-update
  • partner-comarketing-cadence
  • partner-poc-transition
  • partner-channel-kickoff

Hard guardrails for these skills:

  • Never blast partner channels without draft + explicit approval (partner-broadcast-refresh is two-phase).
  • Keep internal ops updates in #sales-partnerships; do not mix with partner-facing channels.
  • Log substantive commitments back to Control Center and HubSpot (partner-hubspot-ops).

Done looks like:

  • Partner-facing updates are consistent, skimmable, and channel-appropriate.
  • No outbound goes out without clear owner, ask, and next step.
  • Slack commitments are reflected in Control Center and CRM.

Skill Readiness Map (Use This First)

This is the quick answer to “what can Lisa run now vs what still needs buildout.”

SkillStatusSafe to use now?What still needs development
partner-outbound-commsProductionYesN/A
partner-broadcast-refreshProductionYesN/A
partner-reply-bundled-asksProductionYesN/A
partner-call-recap-outboundProductionYesN/A
partner-event-ops-updateProductionYesN/A
partner-comarketing-cadenceProductionYesN/A
partner-poc-transitionProductionYesN/A
partner-channel-kickoffProductionYesN/A
partner-hubspot-opsProductionYes (with approval gates)N/A
daily-partnership-refreshProductionYes (with approval gates)N/A
partner-tiering-cadence-reviewBeta scaffoldYes, for manual review + doc outputsAdd recurring automation and trend snapshots
partner-account-mapping-qaBeta scaffoldYes, for structured mapping analysisAdd automated ingestion/scoring connectors
partner-asset-production-trackerBeta scaffoldYes, for status consolidation and handoffsAdd auto-sync from Linear/Drive and SLA nudges
partner-outbound-launch-checkBeta scaffoldYes, for preflight go/no-goAdd direct execution hooks into launch tools
partner-enablement-owner-mapBeta scaffoldYes, for owner clarity and handoffsAdd owner-drift alerts and recurring checks

Practical rule:

  • If Lisa needs immediate execution, start with production skills.
  • Use beta scaffolds as decision-support and workflow standardization layers until automation is added.

Mini-Guide 6: Partner Tiering + Cadence Decisions

Channel signal (last 3 months, #sales-partnerships):

  • Repeated “do we attend this call / is this high-priority?” questions (example: Contextual bronze-tier de-prioritization and 3-week cadence shift).
  • Time allocation tradeoffs across Snowflake/Omni/MoEngage vs lower-yield partner motions.

What this means operationally:

  • Partnership time needs an explicit tiering rubric with cadence defaults (weekly, bi-weekly, every 3 weeks).
  • De-prioritization decisions should be logged as operating choices, not buried in thread chat.

Repo resources:

  • knowledge/sales/partners/ops/partnership-ops-system.md
  • knowledge/sales/partners/README.md
  • knowledge/sales/partners/*/PARTNER_CONTROL_CENTER.md

Skills to use now:

  • daily-partnership-refresh (weekly operating view)
  • partnership-orchestrator-marketing-hub (cadence visibility)

Skill to add (recommended):

  • partner-tiering-cadence-review (audit partner tier, cadence, owner, and de-prioritization rationale)

Mini-Guide 7: Snowflake Account Mapping Sprint

Channel signal (last 3 months, #sales-partnerships):

  • Requests for overlap analysis against Snowflake AE account lists (account, industry, similar company, connection overlap).
  • Need for reusable SOP/template and repeatable account-mapping output.

What this means operationally:

  • Account mapping is becoming a core Snowflake motion and needs a standardized output package.
  • This should move from one-off asks to a repeatable weekly artifact.

Repo resources:

  • knowledge/sales/partners/Snowflake/PARTNER_CONTROL_CENTER.md
  • knowledge/sales/partners/Snowflake/partner-mapping/README.md
  • knowledge/sales/partners/ops/partnership-ops-system.md

Skills to use now:

  • partnership-activity-signals (context ingestion)
  • gtm-ticket-creation (turn mapping asks into structured tickets)

Skill to add (recommended):

  • partner-account-mapping-qa (ingest AE list, compute overlap classes, output partner-ready action plan)

Mini-Guide 8: Co-Marketing Asset Pipeline (Decks, Videos, Event Content)

Channel signal (last 3 months, #sales-partnerships):

  • Frequent “where is the latest deck / who owns edits / can we send now?” loops.
  • Repeated handoffs across design, GTM, and partner owners for MoEngage/Mixpanel/Talisma-type assets.

What this means operationally:

  • Asset production needs a single operating path: request → draft → review → partner send → CRM log.
  • “Latest version” and owner/status should always be visible.

Repo resources:

  • knowledge/sales/partners/ops/partnership-manager-playbook-slack.md
  • knowledge/sales/partners/ops/weekly-partnerships-digest-PRD.md
  • knowledge/sales/partners/*/PARTNER_CONTROL_CENTER.md

Skills to use now:

  • partner-comarketing-cadence
  • partner-call-recap-outbound
  • partner-broadcast-refresh (for approved outbound partner updates)

Skill to add (recommended):

  • partner-asset-production-tracker (status board update + owner nudge + send-readiness checklist)

Mini-Guide 9: Outbound Launch QA (HeyReach + Instantly + Sequence Timing)

Channel signal (last 3 months, #sales-partnerships):

  • Questions on launch timing (LI pre-sequence view/like timing, email timing windows).
  • Uncertainty on platform state and “is sequence ready to send now?” handoff moments.

What this means operationally:

  • Outbound launches need a short QA gate before activation (list quality, channel timing, approvals, copy finalization).
  • This is distinct from copy writing; it is an execution readiness check.

Repo resources:

  • .cursor/skills/gtm-message-sequence/SKILL.md
  • .cursor/skills/gtm-campaign-brief/SKILL.md
  • knowledge/sales/partners/ops/partnership-manager-playbook-slack.md

Skills to use now:

  • gtm-message-sequence
  • gtm-campaign-brief
  • partner-outbound-comms (for channel-facing updates)

Skill to add (recommended):

  • partner-outbound-launch-check (preflight for LI/email launch windows, channel sequencing, and go/no-go)

Mini-Guide 10: Partner Enablement Ownership (Certifications + Intros + Ticketing)

Channel signal (last 3 months, #sales-partnerships):

  • Explicit ownership ambiguity: “how is certification process managed? who owns this?”
  • Frequent intro + “who is counterpart/boss/enablement owner?” clarifications.
  • Ad hoc Linear ticket creation requests for partnership operations.

What this means operationally:

  • Partner enablement needs a single owner map per partner: GTM counterpart, exec sponsor, enablement contact, cert owner.
  • Intro, training, and ticket workflows should be bundled into one mini-runbook.

Repo resources:

  • knowledge/sales/partners/Snowflake/approach-hyperscaler-partner-ops.md
  • knowledge/sales/partners/*/PARTNER_CONTROL_CENTER.md
  • knowledge/sales/partners/ops/partnership-ops-system.md

Skills to use now:

  • gtm-ticket-creation
  • partner-poc-transition
  • partnership-orchestrator-marketing-hub

Skill to add (recommended):

  • partner-enablement-owner-map (maintain contact map + certification owner + open enablement actions per partner)

Skills In Development (from transcript asks)

These are recurring asks that surfaced in GTM/partnership transcripts and should be tracked as workflow upgrades:

  1. LinkedIn MCP or equivalent LinkedIn context connector for better lead discovery and message context.
  2. AI-assisted nurture copilot to draft personalized follow-ups from prior message history and campaign context.
  3. Stronger automation bridge from campaign deployment outputs to CRM updates with less manual copying.
  4. HubSpot cleanup helpers for naming/stage normalization and routine hygiene checks.
  5. Partner tiering/cadence reviewer for explicit de-prioritization and meeting frequency changes.
  6. Account-mapping QA runner for Snowflake-style AE list overlap analysis.
  7. Outbound launch preflight checker for HeyReach/Instantly timing and readiness.
  8. Co-marketing asset pipeline tracker for draft/review/send handoffs.
  9. Partner enablement owner-map maintainer (counterparts, cert owners, intros, and training asks).

Lisa Week 1 Execution Plan

Day 1-2:

  • Confirm access and run one dry cycle of daily-partnership-refresh.
  • Validate Snowflake + Omni Control Centers and next actions.

Day 3:

  • Run partnership-activity-signals and draft one conference-to-follow-up sequence.
  • Prepare CRM actions with partnership-hubspot-eod-payload (approval gate before execution).

Day 4-5:

  • Publish weekly partner pulse draft.
  • Close open loops on Snowflake + Omni touchpoints and confirm next-week priorities.

Owner note: keep updates in knowledge/sales/partners/ as canonical. Use knowledge/sales/partnerships/ only when maintaining legacy artifacts still in that path.

Graph View

Backlinks