Operations Process Map

Purpose: Single map of how operations flows work—from request intake through delivery and feedback. Use for onboarding, handoffs, and process design.
Status: Active
Last Updated: 2026-02-19

---

Overview

Operations at Brainforge connects request intake → work tracking (Linear) → delivery (SOP/Offer/Demo) → feedback and improvement. This document maps those flows and where they live in the vault.

---

High-Level Flow

flowchart LR
    subgraph Intake
        A[Request] --> B[Ticket Creation]
    end
    subgraph Track
        B --> C[Linear]
    end
    subgraph Deliver
        C --> D[Offer / SOP / Demo]
    end
    subgraph Learn
        D --> E[Feedback Loop]
        E --> F[Patterns → PRD/SOP updates]
    end

Stage	What happens	Where it lives
Intake	Requests from Slack, meetings, one-liners	Input to Ticket Creation worker
Track	Structured tickets (title, criteria, points, owner)	Linear + clients/[client]/linear_tickets/
Deliver	Service defined and run per SOP; pitched via Offer; shown via Demo	services, Notion Offers/SOP/Demos
Learn	Run logged → patterns reviewed → agent/SOP improved	Feedback Loop Process, RUN_LOG

---

1. Request → Ticket (Operations Worker)

Trigger: Unstructured request (meeting transcript, Slack thread, one-line ask).

Process:

1. Extract requirements from input.
2. Search Linear for duplicates (dedupe).
3. Create structured ticket file (title, description, success criteria, points, priority, labels, owner).
4. Optionally prompt for feedback (feedback loop).

Worker: Ticket Creation
Output: Linear ticket + file under clients/[client]/linear_tickets/[ticket-name].md

sequenceDiagram
    participant Request
    participant TicketCreation
    participant Linear
    participant Feedback

    Request->>TicketCreation: Transcript / Slack / one-liner
    TicketCreation->>TicketCreation: Extract requirements, dedupe
    TicketCreation->>Linear: Create/update ticket
    TicketCreation->>TicketCreation: Write ticket file to vault
    TicketCreation->>Feedback: Prompt for run feedback (optional)

---

2. Ticket → Delivery (Service Definition)

Once work is scoped and approved, delivery follows the Offer | SOP | Demo model:

Artifact	Purpose	Audience	Vault / Notion
Offer	How we pitch (value, outcome, price, proof)	Sales, marketing	services, Notion Offers
SOP	How we run it (phases, checklists, DRIs, handoffs)	Delivery, PM, ops	sop-template, Notion SOP
Demo	How we show it (examples, talk tracks)	Sales, enablement	demos, Notion Demos

Flow: Ticket (or SOW) references an Offer and SOP → delivery team runs phases per SOP → Demo supports sales and campaigns.

flowchart TB
    Ticket[Linear / SOW] --> Offer[Offer: what we sell]
    Ticket --> SOP[SOP: how we deliver]
    SOP --> Phase0[Phase 0: Pre-]
    SOP --> Phase1[Phase 1: Live]
    SOP --> Phase2[Phase 2: Post-]
    Offer --> Demo[Demo: how we show it]
    Demo --> Sales[Sales / campaigns]

---

3. Delivery → Feedback → Improvement

Every agent run (and key ops actions) can feed the feedback loop:

1. Log run → RUN_LOG.md (run ID, context, input, output, outcome).
2. Review patterns → After 5–10 runs or monthly; document in PATTERNS.md or RUN_LOG.
3. Update agents/SOP → When a pattern is clear (e.g. 80%+), PR to update PRD, taxonomy, or SOP.
4. Next run → Uses updated rules automatically.

Detail: Feedback Loop Process

flowchart LR
    Run[Agent / Ops Run] --> Log[RUN_LOG]
    Log --> Review[Pattern Review]
    Review --> PR[PR: PRD / SOP update]
    PR --> Next[Next run uses new rules]

---

4. Cross-Functional Touchpoints

Area	Ops role	Links
GTM–Delivery	Handoffs from sales (SOW) to delivery (SOP); campaign demos	sow-framework, services README
Integrations	HubSpot (logging, activities), Linear (tickets)	HubSpot integration; CRM property audits — operations/sales/
Founding Ops	Leadership enablement, priorities, blockers	Founding Ops meeting log

---

5. Where to Go for What

You need…	Go to
Create a ticket from a request	Ticket Creation worker
Define or update a service (pitch vs delivery vs demo)	services, sop-template
Log a run and improve from it	Feedback Loop Process, RUN_LOG
See all GTM workers and workflows	Agent Registry, Architecture
Ops leadership cadence and notes	Founding Ops meeting log

---

Summary Diagram (All Flows)

flowchart TB
    subgraph Intake
        R[Request]
        TC[Ticket Creation Worker]
        R --> TC
    end

    subgraph Track
        L[Linear]
        TC --> L
    end

    subgraph Deliver
        O[Offer]
        S[SOP]
        D[Demo]
        L --> O
        L --> S
        S --> O
        O --> D
    end

    subgraph Learn
        FL[Feedback Loop]
        PAT[Patterns]
        PRU[PRD / SOP Updates]
        Deliver --> FL
        FL --> PAT
        PAT --> PRU
        PRU -.-> TC
        PRU -.-> S
    end

---

Maintained by: Ops
Review: When adding a new operations flow, worker, or changing request → delivery → feedback handoffs.