DataKnobs can enter through a proven solution, a focused capability, a shared platform, or strategic delivery. Packaging defines what you are buying; the pricing pages separately define subscription, activation, infrastructure, and consumption.
Engagement ladder
Four commercial motions
The older Starter/Growth taxonomy overlapped with DataKnobs' Launch/Business/Scale pricing plans. These four packages instead describe the scope and responsibility of the engagement.
Use when the business workflow is already clear and a known DataKnobs pattern can shorten discovery and implementation.
Use when the organization already has a product or platform and needs one missing capability rather than a full replacement.
Use when several teams need common patterns for building, governing, evaluating, and continuously improving AI-enabled products.
Use when the customer needs architecture, implementation, governance, integration, or fractional AI/technology leadership in addition to software.
How to choose
The best entry point depends on whether you already know the workflow, the capability gap, or the operating model you want to standardize.
Start with a Proven Solution when the business process and desired outcome are already clear.
Start with KREATE, KONTROLS, or KNOBS when an existing stack needs a focused capability.
Use the Platform when common context, evaluation, governance, and controls need to be reusable.
Use Strategic Delivery when success depends on architecture, integrations, organizational alignment, or executive ownership.
Move from one outcome to shared capabilities only when reuse creates measurable value.
Packaging vs pricing
A package describes what DataKnobs is responsible for. The pricing model then determines activation, platform subscription, infrastructure ownership, managed operations, and provider consumption.
| Package | Primary question | Typical scope | Commercial path |
|---|---|---|---|
| Proven Solution | Can we solve this workflow quickly? | One defined use case with configured integrations and controls. | Activation + applicable platform subscription. |
| Focused Capability | Which platform gap should we close? | One or more KREATE / KONTROLS / KNOBS capabilities. | Capability scope + activation + support as required. |
| Platform | How do we standardize across teams? | Shared Data Products, controls, evaluation, runtime knobs, and operating patterns. | Annual platform plan + activation; deployment choice priced separately. |
| Strategic Delivery | Who will design and drive the transformation? | Custom architecture, implementation, integration, governance, or fractional leadership. | Scoped services plus any software/platform subscription. |
Expansion model
The goal is not to force every customer into the full platform. The goal is to make the second useful AI capability faster, safer, and less expensive than the first.
Define the decision, data, controls, and business acceptance criteria.
Reuse context, connectors, evaluations, policies, and adjustable knobs across adjacent workflows.
Move toward platform adoption when multiple teams benefit from the same reusable operating layer.
FAQ
No. Packaging defines the scope of what a customer is buying. Pricing separately defines activation, platform subscription, deployment ownership, managed operations, and variable provider consumption.
Yes. That is often the preferred path. Start with a measurable business outcome, then expand when the resulting data, controls, evaluations, and workflows can be reused.
No. The same commercial package can be delivered in customer-owned infrastructure or, for qualified workloads, DataKnobs-managed infrastructure.
Tell us the workflow, decision, data sources, risk constraints, and timeline. DataKnobs can recommend the smallest package and deployment model that makes sense.