Capabilities
What operational execution and enablement does each venture need — and what does the platform provide?
Every venture faces the same mandatory, non-core critical path before it can deliver value. The platform runs that path once. Each venture inherits the deterministic layer and focuses on what's unique.
Capabilities serve Flow 3: Procure-to-Pay, Flow 4: Operational Execution, Flow 5: Financial Performance, and Flow 6: People, Capability & Governance. Agents can route exceptions, reconcile records, prepare checklists, and surface risks; the human judgment gate is reliability under consequence: what promise must be kept, what liability is acceptable, and which exception needs accountable ownership?
Customer Growth
If they flow, you both grow. One family, five capabilities: improve the customer's life and the customer base — your revenue — grows with it.
- Customer Advertising — How do the right strangers discover you?
- Customer Marketing — How does attention become trust before the ask?
- Customer Pricing — What is the value exchange worth?
- Customer Sales — How does trust become commitment?
- Customer Success — How does the promise get kept, expanded, and referred?
The family serves Flow 1: Customer Intent and Flow 2: Order-to-Cash. Agents sense demand, assemble context, draft offers, and monitor conversion. The human judgment gate is the promise itself: who do we serve, what do we promise, what relationship will we maintain? Make customers the heroes of the journey.
Operating Domains
| Function | Platform (Shared) | Venture (Unique) | Status |
|---|---|---|---|
| Finance | Banking, invoicing, compliance | Pricing, unit economics | Planning |
| Customer Success | Outcome proof, onboarding, retention | Customer progress, trust repair, expansion | Active |
| Human Resources | Contracts, payroll | Role definition, hiring | Planning |
| Property | Lease portfolio, AI tools, buyer-side player network | Per-location decision flow, fit-out, density | Active |
| Tech Systems | Tooling, CI/CD, monitoring | Domain workflows | Planning |
| Legal | Entity formation, IP, CLM, compliance calendar, AI clause analysis | Industry-specific compliance, jurisdiction strategy, token classification | Active |
The "Platform" column is deterministic — identical for every venture, verified once. The "Venture" column is where domain intelligence shapes the model. Credibility compounds when the shared layer works reliably enough that ventures can focus entirely on their unique value.
Context
- Business Factory — Principles → Strategy → Innovation → Instruments → Flows → Capabilities → Feedback
- Seven Business Flows — Each operational function below appears in one or more of the seven data flows (finance → flow 5, HR → flow 6, procurement → flow 3, etc.)
- Ventures — The portfolio these operations serve
- Financial Operations — The numbers we need to know and hit
- Credibility — Three loops: inner (tests), story (predictions), market (revenue)
Questions
Which operational function would unlock the most ventures if it moved from "Planning" to "Active"?
- What's the cost of each venture solving legal, banking, and compliance independently vs inheriting it from the platform?
- Which row in the table above has the highest ratio of shared value to unique configuration?