Delivery — one-stop shop
Purpose: Single source of truth for Brainforge delivery operations: roles (Head of Delivery, CSO, Service Lead, ICs), cadence and meetings, project lifecycle (SOW → project plan → execution), standards, and links to tools/skills.
Who uses this: Everyone on delivery; leadership sets standards here; CSOs and SLs execute against it.
Navigation
| Section | What it is |
|---|---|
| INDEX.md | Quick links by role and topic |
| 00-head-of-delivery | Head of Delivery: role, cadence, standards, escalation |
| 01-roles-and-responsibilities | CSO, Service Lead, Individual Contributor |
| 02-meetings-and-cadence | Meeting catalog, Project Review Meeting, templates |
| 03-project-lifecycle | SOW → project plan → Linear → execution |
| 04-standards-and-sops | Linear hygiene, comms, PM, escalation |
| 05-tools-and-skills | Cursor skills, workflows, playbook SOP links; Linear Day 1 guide |
| operating-tool | Operating.app for delivery: agent MCP/API workflow, audit trail pointers |
| 06-reference | Archives, redirects, source material pointers |
Relationship to other repos
- Playbook (
standards/): Canonical templates and SOPs (SOW template, ticket format, weekly update SOPs). This knowledge section references playbook; it does not duplicate restricted playbook content. - Sales services (
knowledge/sales/services/): Service catalog (offer, SOP, demo per offering). Per-client planning uses sow-project-plan-template.md. - Operating model + roster (platform): delivery-operating-model.html — coverage by client/service and lifecycle explainer; see delivery README to update
client-coverage.json. - Client folders (
knowledge/clients/{client}/): Transcripts, SOW copies, client-specific resources.
Q2 delivery KPI (example)
Escalations: Fewer client- and leadership-level escalations when ownership is clear, plans are reviewed early, and standards are visible. Project Review Meetings and Linear hygiene directly support this.
Last updated: 2026-04-06