Entries
05
Public routes in this family.
Modalities
Delivery modalities for different levels of speed, control, and internal involvement.
The same mandate can run as an audit, a shared implementation, or an external build. These routes explain the tradeoffs clearly.
Modality routes let buyers see how collaboration, ownership, and rollout differ before a mandate is scoped privately.
Capabilities
11
Capability domains connected to the family.
Operators
07
Operator families reused across the routes.
Proof systems
07
Proof pages tied into the narrative.
Inside this family
- Ownership model
- Execution speed
- Adoption posture
Cross-surface map
Move between operators, solutions, industries, and projects.
Use this family page as a clean bridge into the surrounding public product surfaces.
Keep exploring
Move from this family into the routes that explain, prove, and operationalize it.
The same mandate can run as an audit, a shared implementation, or an external build. These routes explain the tradeoffs clearly.
Recommended next
Offers
Move back up the stack into commercial packaging.
Recommended next
Implementations
See the build families that each delivery posture can support.
Recommended next
Services
Compare the delivery posture against the active service tracks.
Recommended next
Frameworks
Use the strategy layer to choose the right collaboration model.
Modality
Audit-Led
Start with diagnosis, not deliverables, when the real bottleneck is still unclear.
This path is strongest when the team needs clarity, prioritization, and proof before deciding what to build.
Unclear constraintsCompeting priorities
Modality
Done-With-You
Collaborative design and implementation with more internal buy-in and more shared context.
Useful when the client team has strategic context or operators who need to stay close to the build.
Internal team availableNeed for adoption
Modality
Done-For-You
End-to-end build ownership when the business needs speed and a stronger external operator.
Best when the client wants a result without building an internal program around it first.
Need for speedLimited internal bandwidth
Modality
Retained
Continuous evolution for teams that need a compounding system, not a one-time deliverable.
Strong where authority, optimization, and operator improvement need to keep evolving after launch.
Ongoing optimization needsContent or proof program required
Modality
Proof-First
Lead with diagnostics, frameworks, and visible systems before a full commercial rebuild.
Useful when trust has to be earned by showing competence in a very concrete way.
Skeptical marketComplex capability