SOW Framework

This folder defines how Brainforge positions, structures, and prices SOWs for sales motions.


Renewal Path Taxonomy (canonical)

Use one of these two paths for renewal-oriented SOWs and label it explicitly in the document:

  1. Fractional Data Team-as-a-Service (FDTaaS)

    • Best for ongoing data operations, embedded support, evolving backlog, and quarterly reprioritization.
    • Commercial shape: monthly retainer (often annual term, rolling workstreams).
    • Operating model: fixed workstreams + flexible sequencing.
    • Reference example: knowledge/clients/cta/sows/SOW_CTA_2026_Q2_Data_Operations_Options.md.
  2. Data Foundations Sprint (DFS)

    • Best for bounded foundation buildouts with milestone-driven outcomes and explicit handoff.
    • Commercial shape: sprint-based or fixed-fee phase package.
    • Operating model: tighter scope control and completion-oriented sequencing.
    • Reference example: knowledge/standards/02-writing/SOWs/examples/sow-data-etl-LMNT.md.

Required Metadata in New SOWs

Every proposal/SOW should include an explicit line near the top:

  • Engagement Path: Fractional Data Team-as-a-Service or
  • Engagement Path: Data Foundations Sprint

If omitted, reviewers should treat the SOW as incomplete.


  • Sales hub: knowledge/sales/README.md
  • Lead scoping template: knowledge/sales/leads/_templates/lead-spine-template.md
  • SOW template: knowledge/standards/02-writing/SOWs/sow-template.md
  • SOW quality checklist: knowledge/standards/02-writing/SOWs/sow-checklist.md