The Seven Flows
Problem: Department maps hide the movement of value, decisions, and evidence across boundaries.
Question: Which business flow owns the event, where is it constrained, and what should improve first?
Decision: Choose one flow, then redesign one decision loop inside it.
A business is the data that moves through it. Seven flows carry that data. Six are commercial. The seventh — analytics and feedback — is the brain stem that makes the other six self-correcting.
The Seven Flows of a Business
Six commercial flows. One meta-flow wraps them. Click any flow for depth.
- Customer Intent & DemandWhat the market wants and how it is changing.Data sources:Ad impressions, clicks, form fills, telemetry, NPS, churn reasons.
- Order-to-CashFrom quote to money in the bank.Data sources:Quotes, contracts, orders, fulfilment status, invoices, payments, refunds.
- Procure-to-Pay & SupplyDeliver consistently and profitably.Data sources:Forecasts, POs, supplier confirmations, receipts, payables, payment runs.
- Operational ExecutionPromises become reality — production, service, logistics.Data sources:Work orders, capacity, utilization, delivery performance, downtime, rework.
- Financial PerformanceThe truth ledger that integrates all other flows.Data sources:Revenue, margin, costs, cash position, covenants, FX, credit exposure.
- People, Capability & GovernanceHow fast the organisation learns, adapts, and stays safe.Data sources:Hiring pipeline, onboarding, role changes, skills, performance, retention, access logs, audits.
Source: 7-flow framework (banthamtechnologies) + three-flows + data-value-flow. SaaS-first lens — physical/manufacturing variant deferred.
Start Here
Choose the flow whose constraint most limits value. Then run the AI-Native Flow Assessment to turn one slow, fragile, or opaque decision into a bounded before-and-after proof.
When incremental correction cannot make the chosen flow reach its setpoint, use Business Process Re-engineering to redesign the process from the intended outcome backward.
Why Flows, Not Departments
A traditional org chart shows what people report to. A flow map shows what data moves through. The two answer different questions. Reporting lines are a side-effect of legal accounting; flows are how value actually moves. Cross-functional dysfunction is almost always a flow that no department owns.
The seven flows below are designed so that every operational event in a running business lands in exactly one of them. If you cannot place an event in a flow, you are either looking at strategy (which is a separate arc) or at noise (which should be filtered).
The Frame for Every Flow Page
Each flow page below is built the same way. The template is the contract — read one flow and you know how to read all of them.
- What this flow tells you — the question the flow answers
- Data sources — events, transactions, telemetry to instrument
- Decision gates — where choices are made and ownership transfers
- AI capabilities — perception, decision, action, memory, escalation
- Crypto-rail instruments — what settles, attests, or verifies on-chain
- Gauge — the one metric that matters (per the single-metric-per-loop rule)
- Kill signal — the condition under which the flow is broken
- Skill coverage — which skills run this flow today, which are green-field
- Upstream / downstream — what feeds in and what flows out
The Seven
- Customer Intent & Demand — what the market wants and how it is changing
- Order-to-Cash — from quote to money in the bank
- Procure-to-Pay & Supply — deliver consistently and profitably
- Operational Execution — production, service, logistics — where promises become reality
- Financial Performance — the truth ledger that integrates all other flows
- People, Capability & Governance — how fast the organisation learns, adapts, and stays safe
- Meta-Flow: Analytics & Feedback — events → insight → changed behaviour
Skill Coverage
Each flow page names the skills that can operate it today and the missing capabilities that still need proof. Treat a green-field capability as demand to validate, not permission to build.
Archetype
The pages below use a SaaS-first lens — subscription billing, self-serve checkout, web telemetry, AP2 mandates, x402 micropayments, stablecoin payroll. The same seven flows exist in physical/manufacturing businesses with different dominant data objects (POs, BOL, WIP, plant capacity). A physical variant is a deliberate follow-up, not an oversight.
Upstream
- Three Flows — Messages / Value / Data, the five-stage spine the seven business flows project onto.
- Data-Value-Flow — the four parallel data streams (Expectations, Transactions, System of Record, Aggregated) that cross-cut all seven flows.
- A&ID — agents (Yang) operate the flows; instruments (Yin) measure and reward.
When A Flow Breaks
The common failure mode is a flow no department owns: events pile up between reporting lines and no gauge catches the drift. The risk shows up as cross-functional dysfunction that no org-chart fix resolves — only naming the flow and its owner does.
Changes my mind: a business whose every operational event already lands cleanly in one owned department, with no cross-functional gaps, would not need the flow lens at all. Next question: which of the seven flows is currently unowned, and what gauge would make its drift visible first?
Version delta: the map now routes from flow selection into one bounded AI-native assessment, and skill coverage stays with the flow page that owns the evidence.
Context
- proved-by Work Chart Metrics — flow claims need gauges, saturation signals, and loop-level throughput evidence.
- depends-on Data-Value-Flow — each business flow is measured through the data that crosses it.
- applies-to Function Catalog — the seven flows become useful when mapped to repeatable business functions.
- pairs-with AI-Native Flow Assessment — redesign one constrained decision loop inside the chosen flow.