Brainforge Knowledge

README

3 min read

Sales Services Planner Agent

Purpose: define a delivery-grade planning system for sales services so service design, packaging, and go-to-market decisions run with the same rigor as Delivery project reviews.

This planner layer also includes an M&A acquisition operating scaffold for sourcing, screening, and progressing tuck-in agency targets under Sales.

This planner is the operating layer between:

  • Notion Services workspace (strategy canvas + databases)
  • knowledge/sales/services/ repo artifacts
  • Linear planning and project-review checkpoints

What this agent owns

The planner agent is accountable for three outcomes:

  1. Service planning quality
  • Turn service ideas into buildable plans with clear outcomes, ICP fit, time-to-value, and implementation shape.
  1. Notion ←> repo alignment
  • Keep service lines, offers, and planning fields synchronized between Notion and the repo with explicit conflict rules.
  1. Governance and change control
  • Prevent structure drift in Notion and repo without deliberate review and sign-off.

Planner system docs

  • notion-repo-sync-contract.md
    • Source-of-truth model, field mapping, and conflict handling.
  • agentic-workflow-and-triggers.md
    • Multi-agent operating model, trigger catalog, and handoff sequence.
  • guardrails-and-change-control.md
    • Structural guardrails, approval gates, and blocked-change policy.
  • planner-sign-off-checklist.md
    • Pre-review and pre-publish checklist for CSO + SL + Head of Delivery.
  • sync_executor.py
    • Runnable executor for audit/apply-repo/link-check.

M&A planner docs

  • ma-planner-overview.md
    • Acquisition strategy narrative, target profile, and operating cadence.
  • ma-target-screening-contract.md
    • Deterministic target scoring, required diligence artifacts, and stage gates.
  • ma-workflow-and-triggers.md
    • Trigger catalog and stage-based deal workflow (source → close).
  • ma-deal-execution-agent-workflow.md
    • Post-approval execution workflow (LOI → close → Day 100).
  • ma-workflow-c-delivery-integration.md
    • Delivery-integration lane tying tuck-in value realization to existing Brainforge delivery structure.
  • deal-execution-template.md
    • Reusable per-deal template for running the post-approval execution workflow.
  • ma-guardrails-and-change-control.md
    • Deal guardrails, approval policy, and blocked-change conditions.
  • ma-sign-off-checklist.md
    • Investment committee style pre-LOI and pre-close checklist.
  • ma-loi-playbook.md
    • Required LOI structure, non-negotiable term set, and first-deal risk controls.
  • ma-agency-investor-checklist.md
    • Required diligence question bank for M&A orchestrator users assessing a deal.
  • ma-zero-cash-offer-structure.md
    • Zero-cash-upfront deal templates tied to retention and growth outcomes.
  • olivo-merge-multiple-case-study-deck-outline.md
    • Slide-by-slide narrative for the “merge for multiple expansion” pilot case study (Olivo).
  • olivo-loi-approval-packet-draft.md
    • One-page internal approval packet template for issuing the Olivo pilot LOI.
  • olivo-indicative-terms-fast-track.md
    • Pilot indicative terms and LOI-readiness tracker for the Olivo transfer.
  • brainforge-should-we-buy-now-decision-memo-2026-03.md
    • Red/yellow/green readiness memo for pilot-vs-programmatic M&A decisioning.
  • olivo-loi-draft-v1.md
    • Non-binding LOI draft with 3-scenario valuation framework for Olivo book transfer.
  • ma-education-deal-construction-from-transcripts.md
    • Education primer explaining practical M&A mechanics from transcript patterns.

Scope hierarchy

The planner uses this hierarchy for all sync and planning decisions:

Service Line -> Subservice -> Offering -> Plan -> Milestone -> Ticket

Linear mapping:

Initiative -> Project -> Milestone -> Issue

Service lines to enforce

From Notion Services page + Services Catalog domain model, current service-line taxonomy to preserve:

  • AI
  • Data
  • Strategy & Analytics

Domain groupings in Notion (for commercial framing) are mapped, not replaced:

  • Data Platform and Analytics
  • AI Automation and Copilots
  • Training and Enablement
  • Weekly: sync and drift check (Notion vs repo)
  • Bi-weekly: service planning review (CSO + relevant SLs)
  • Monthly: taxonomy and pricing guardrail review
  • Quarterly / SOW-aligned: formal sign-off and restructure window

Definition of done

A service planning cycle is complete when:

  • Notion + repo pass sync contract checks.
  • Planned service package is buildable (SL-validated).
  • Commercial story and delivery story match.
  • Sign-offs are recorded using planner-sign-off-checklist.md.

Sync executor quickstart

Run from repo root:

python knowledge/sales/services/planner-agent/sync_executor.py audit
python knowledge/sales/services/planner-agent/sync_executor.py apply-repo --dry-run
python knowledge/sales/services/planner-agent/sync_executor.py check-links

Live Notion API mode (optional):

export NOTION_TOKEN="secret_xxx"
export NOTION_SERVICES_CATALOG_ID="2637908b-1268-802d-bd75-000b2d4adc39"
export NOTION_OFFERS_ID="2637908b-1268-8049-bc1a-000b210a291c"
python knowledge/sales/services/planner-agent/sync_executor.py audit

If API creds are not set, the executor uses notion_service_lines.json as fallback.

Graph View