Skip to main content

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.

Capability Intersection

This layer owns valuable operational outcomes. Human capabilities govern judgment; agent skills carry repeatable methods and receipts; business capabilities consume both and return evidence.

The Capability System connects every business capability to the human capability that governs it and the agent skill that can amplify its repeatable work.

Review the intersection before buying tools or automating workflow:

  1. name the valued business outcome and accountable owner;
  2. identify the human judgment, character, relationship, or presence required;
  3. delegate repeatable work to an agent with a boundary and receipt;
  4. prove the combination changes the outcome;
  5. cultivate, redesign, automate, or retire from evidence.

Business activity without this chain can look productive while capability remains unchanged.

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?

Business First Principles

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.

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

FunctionPlatform (Shared)Venture (Unique)Status
FinanceBanking, invoicing, compliancePricing, unit economicsPlanning
Customer SuccessOutcome proof, onboarding, retentionCustomer progress, trust repair, expansionActive
Human ResourcesContracts, payrollRole definition, hiringPlanning
PropertyLease portfolio, AI tools, buyer-side player networkPer-location decision flow, fit-out, densityActive
Product InnovationResearch, experiments, evidence standardsImportant problems, demand, urgency, and validated opportunitiesActive
ProductionDelivery methods, quality controls, operating evidenceProduct- and service-specific creation and operationActive
Tech SystemsTooling, CI/CD, monitoringDomain workflowsPlanning
LegalEntity formation, IP, CLM, compliance calendar, AI clause analysisIndustry-specific compliance, jurisdiction strategy, token classificationActive

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?