Pricing

Pricing and Engagement Models

Four ways to work with DPI, each with a defined scope and output. Quotes are written, fixed where the scope is fixed, and given after a short call about your volume, systems, and goals.

Engagement Models

From first assessment to managed operations

Discovery sprint

Two to three weeks, fixed scope. Workflow maps, readiness findings, ranked use cases, architecture, and a first deployment scoped with its metric. The output is yours whether or not you continue with DPI.

30-day pilot

Fixed scope and timeline. One workflow, one channel, or one call type in production on your systems, with success criteria agreed in advance and a go or no-go decision at the end.

Build

Fixed-scope delivery of the full deployment: integrations, evaluation, rollout, training, and documentation. Delivered in increments with working software at each step.

Managed operations

Monthly service sized by volume and integrations: monitoring, quality reviews, tuning, new intents and features, and a monthly report against the original metric.

What Drives Cost

The five factors behind every quote

  1. Scope. How many call types, workflows, document types, or features the first release covers. Smaller first releases cost less and prove more.
  2. Integrations. Each system the AI reads from or writes to adds design, permissions, and testing.
  3. Volume. Calls, conversations, and documents per month drive processing costs and shape the hosted-versus-self-hosted decision.
  4. Hosting and compliance. Private or self-hosted models, HIPAA-aligned architecture with a BAA, and audit requirements add engineering and infrastructure.
  5. Quality bar. The accuracy and containment targets agreed before launch determine how much evaluation and tuning the build includes.

Every Quote Includes

What you always get

Written scope

Workflows, integrations, deliverables, timeline, and the metric that defines success.

Cost breakdown

Build, operations, and pass-through costs such as hosted model usage and carrier minutes, stated separately.

Evaluation

A test set from your real cases and the accuracy bar the system must meet before cut-over.

Ownership

Code, data, and documentation are yours; systems can be run by your team or by DPI.

Security terms

Data handling, hosting, retention, and where required a BAA, agreed before build.

Reporting

A monthly report against the original metric for every managed deployment.

Cost Guides

Read before you ask for a quote

FAQ

Pricing questions

Why are there no prices on this page?

Because scope drives cost more than anything else, and a number without a scope misleads. Every engagement is quoted in writing after a short call about volume, systems, and goals, usually within days.

Do you bill hourly?

Discovery, pilots, and builds are fixed-scope with fixed prices. Managed operations are monthly. Hourly billing is used only for ad-hoc advisory when a client prefers it.

What about model and telephony costs?

Hosted model usage and carrier minutes are passed through or included in the managed fee, stated explicitly in the quote. Self-hosted models replace per-minute fees with fixed infrastructure costs.

Is there a minimum engagement?

The smallest engagement is a fixed-scope audit or discovery for one workflow or business unit. It is designed to end in a decision and a scoped deployment.

Can we pause or stop managed operations?

Yes, with notice as set out in the agreement. Systems are built so you can operate them yourself or hand them to another team; you own the code and data.

Next Step

Bring one workflow. Leave with a production plan.

Tell us where calls, tickets, documents, or approvals pile up. We map the workflow, size the impact, and propose a deployment you can measure.