Pricing
Pay for the platform, implementation and operations you actually need.
DebugInit prices customer-specific systems through transparent components rather than hiding infrastructure and AI costs inside one opaque subscription.
Assessment • implementation • platform • usage • managed operations
Why there is no price on this page
Our pricing is not a subscription. It is scoped to your workload, your demand and the requirements of the specific business solution — how many processes, how much data and inference, which deployment model, what service level. Those differences are larger than any seat-based figure would suggest, so a number here would be a guess.
So the structure is published instead: five components, each priced on something you can inspect and each moving with what the system actually does for you. You get a number after an assessment, with the assumptions written down so you can challenge them.
What you pay for
Five components rather than one opaque subscription, so you can see which part of the cost is which — and drop the parts you do not need.
| Component | Priced on | What it covers |
|---|---|---|
| Assessment | Fixed scope | Operational and technical discovery with defined deliverables: an inventory, a process map, an economic model and a recommendation you can act on elsewhere. |
| Implementation | Milestone or outcome | Configuration, engineering, migration, integration and rollout, priced against agreed milestones rather than an open-ended day rate. |
| Platform | Workload & scale | Sized to the workload you put through it — deployment model, Business Foundations in use, environments, transaction and data volume, and organisational scale. It moves with demand, not a fixed seat count. |
| AI and infrastructure | Metered or direct | Transparently metered, or billed by your provider directly to you where that is feasible. Not folded invisibly into a platform fee. |
| Managed operations | Support tier | Service levels, security operations, upgrades and continuous optimisation, sized to what the system is doing for you. |
Scroll the table sideways to see every column.
What moves the number
The inputs a scoped estimate is built from. Knowing your own answers before the conversation makes it a short one.
Users and roles
How many people, in how many distinct roles with different permissions.
Entities
The business objects you manage, and how much they vary between departments.
Workflows
How many processes, and how much approval and exception logic each carries.
Business Foundations
Which business functions are in scope now, and which follow later.
Integrations
Systems to connect, and whether each has a usable API or needs a workaround.
Data migration
Volume, quality and how much reconciliation the existing records need.
Deployment
Managed, customer cloud, on-premises, hybrid or air-gapped.
Security
Review depth, controls, residency constraints and audit requirements.
AI volume
How much inference the workflows use, and which providers are permitted.
Service level
Cover hours, response targets and who carries the pager.
Ownership and exit
You retain rights to your business data, with export and transition procedures defined per deployment and agreement. Terms vary by deployment and customisation model, and are set contractually rather than by this page.
Ask about exit terms during commercial discussion rather than at renewal. A vendor unwilling to discuss them early is telling you something.
Request a scoped estimate
Bring one process and the constraints around it. You get a fixed-scope assessment price now and a full estimate once there is something real to price.
Frequently asked questions
Why is there no single monthly price?
Customer-specific internal systems vary materially in workflow, integration, migration, deployment and support complexity.
Can we begin with a small pilot?
Yes. The preferred starting point is one bounded process with measurable outcomes.
Are infrastructure and model costs included?
The proposal identifies whether costs are included, metered or paid directly by the customer.