Brainforge Knowledge

ma-workflow-c-delivery-integration

3 min read

Workflow C — Delivery Integration and Value Realization (Binding Lane)

Purpose: define the mandatory delivery-integration lane for tuck-in deals so acquired books are integrated into Brainforge’s existing delivery structure, not managed as standalone side portfolios.

This workflow is the operating bridge between M&A execution and Delivery operations.

Use with:

  • ma-deal-execution-agent-workflow.md
  • ma-loi-playbook.md
  • ma-sign-off-checklist.md
  • deal-execution-template.md

Delivery structure references:

  • knowledge/plans/delivery/delivery-charter-rubric-operating-model-2026.md
  • apps/platform/public/delivery/delivery-operating-model.html
  • apps/platform/public/delivery/client-coverage.json

1) Why Workflow C exists

For Brainforge, tuck-ins are not financial assets only. They are intended to:

  • extend existing service lines
  • place incoming operators as GM-level leaders inside Brainforge lanes
  • open new vertical access
  • grow existing account books through cross-sell/expansion
  • create new delivery sourcing opportunities for the core delivery team

If this lane is not executed, deal value realization is considered failed regardless of close completion.

2) Entry criteria

Workflow C starts immediately after proceed-to-LOI approval and runs in parallel through Day 100.

Required owners:

  • Integration Lead (primary owner)
  • Delivery/Service Lead (service-line owner)
  • Deal Lead (commercial bridge)
  • Operator/GM designate (target-side owner)

3) Binding LOI hooks (required)

The LOI must include binding or condition-precedent language for Workflow C cooperation (final legal drafting by counsel).

Minimum required LOI hooks:

  • Transition Cooperation Covenant:
    • seller/operator participates in delivery-integration workstreams during agreed transition period
  • Account Transition Data Covenant:
    • account-level data and delivery context shared in agreed format and cadence
  • Relationship Transfer Support:
    • seller/operator participates in named client handoff sequence
  • Integration Milestone Alignment:
    • payout mechanics are linked to retention/integration milestones where applicable

Note:

  • The full acquisition economics may remain non-binding at LOI stage, but Workflow C cooperation and process obligations should be drafted as binding where legally appropriate.

4) Workflow C phase map

C0: Design -> C1: Pre-Close Mapping -> C2: Day 1 Launch -> C3: Day 30 Stabilize -> C4: Day 60 Expand -> C5: Day 100 Realization

C0 — Design (pre-LOI or immediately post-LOI)

Outputs:

  • target service-line mapping
  • operator GM lane definition
  • initial KPI tree for value realization

C1 — Pre-Close Mapping

Outputs:

  • account segmentation (Tier A/B/C)
  • delivery pod and owner mapping
  • handoff calendar by account
  • risk flags (concentration, dependency, complexity)

C2 — Day 1 Launch

Outputs:

  • continuity communication complete for Tier A accounts
  • relationship owners active in client-coverage.json mapping
  • first 2-week operating sprint initiated

C3 — Day 30 Stabilize

Outputs:

  • retention and service continuity baseline
  • unresolved delivery blockers list
  • operator GM role calibration complete

C4 — Day 60 Expand

Outputs:

  • cross-sell and expansion plan launched
  • delivery sourcing opportunities prioritized
  • service-line contribution report v1

C5 — Day 100 Realization

Outputs:

  • value realization report
  • KPI outcomes vs plan
  • playbook updates proposed for next tuck-in

5) Delivery accountability scorecard (required)

Track weekly and report at Day 30/60/100:

  1. Retention and continuity
  • GRR for transferred cohort
  • account continuity completion rate
  1. Service-line extension
  • number of accounts now attached to Brainforge service-line packages
  • GM/operator lane activation status
  1. Book growth
  • expansion pipeline from transferred accounts
  • expansion revenue realized
  1. Delivery sourcing
  • number of new delivery opportunities identified
  • number accepted into delivery planning pipeline
  1. Structural integration
  • accounts correctly represented in delivery operating model/coverage map
  • unresolved ownership conflicts count

6) Non-negotiable close criteria tied to Workflow C

No close-ready approval if:

  • no named GM/operator integration role
  • no account-level handoff map
  • no Day 1 continuity plan
  • no Day 100 KPI plan with owners

7) Required artifacts

Store per deal:

  • workflow-c-service-line-mapping.md
  • workflow-c-account-handoff-plan.md
  • workflow-c-day1-day100-kpi-plan.md
  • workflow-c-day30-report.md
  • workflow-c-day60-report.md
  • workflow-c-day100-value-realization-report.md

8) Escalation

Escalate within 24h to Delivery leadership + Deal Lead if:

  • Tier A client handoff misses planned date
  • retention signal deteriorates materially
  • operator GM scope remains unresolved
  • delivery ownership conflicts persist beyond one weekly cycle

Graph View