You pay for completed work.
Not seats, not hours.
Every workflow we automate gets a defined billing unit: a finished piece of work your team would otherwise push through by hand. Before anything ships, you see what counts as billable, what does not, and how exceptions or human review are handled.
30 minutes · Read-only · No obligation
Finished work that matches the approved scope and completion rules.
Exception handling, retry rules, human approvals, minimums, and pause terms.
Scope changes are re-quoted before the automation takes on more responsibility.
Three steps to scoped pricing
A 30-minute working session to see how one workflow really moves: inputs, outputs, tools, handoffs, and edge cases. The audit is currently offered at no charge, and you leave with a workflow economics map you can use internally whether or not you move forward.
From the audit we scope a pilot, define what finished work means, and quote a per-unit price. You see what would count as billable before anything ships.
Before launch, we document what counts as completed work, how billing works for that workflow, and how scope changes are handled. Many engagements are priced against the agreed unit of work rather than seats or broad software access.
Six inputs we use to quote, all visible before you commit.
We don't post a per-unit price here because no two workflows are the same. These are the inputs we use to build the quote after the audit — so when you see the number, you know exactly what moved it.
How many units the workflow processes per month. Higher volume typically means a lower per-unit price because fixed costs amortize across more work.
How many systems the workflow touches and whether they have clean APIs, legacy portals, or a mix. More integration surface area means more work per unit.
The share of work that needs human review. Higher exception rates mean more review cost baked into the per-unit price — which is why the audit matters.
What the workflow writes back and to which systems. Read-only workflows price differently than ones that post to the ERP or billing system.
Same-day review is different from minutes-to-completion. Tight SLAs and peak-hour coverage affect the quote.
What counts as one completed outcome. A narrow unit (one invoice posted) prices differently than a broader one (one customer onboarded end-to-end).
The quote lands after the audit, before anything ships. If the pilot scope changes later, we re-quote before the automation expands.
- Initial audit currently offered at no charge - workflow economics map is yours to keep
- Workflow scope and billing trigger defined before any production work starts
- Workflow design, build, and deployment for the pilot scope are covered in the proposal for that engagement
- Integration into your existing tools and systems
- Ongoing monitoring and alerting
- Maintenance — we fix what breaks
- Iteration — we improve what ships
- Usually no per-seat or per-user software license
- Workflow-specific pricing rather than broad platform access
- Billing tied to the agreed finished unit of work
- Human-review, exception, and retry handling stated before launch
- Any minimums, pause terms, or change-of-scope rules stated in the proposal
- Commercial terms reviewed before the workflow goes live
Common questions about how we price
Commitment length, any minimums, and pause mechanics are defined in the proposal for the scoped workflow. Many pilots start narrow so the economics are easy to evaluate before anything expands.
An outcome is a successfully finished unit of work: an invoice prepared, a customer setup path completed, or a payer-status check documented. We define it together during the audit so there are no surprises.
The per-outcome price for the approved scope is documented before launch. If scope changes significantly, such as adding new workflow steps or systems, we re-quote before making changes.
Volume mechanics are stated in the proposal. In a per-outcome model, billing follows completed work rather than seat count, subject to any agreed minimums or pause terms.
No. We build inside the tools you already use. If new infrastructure is needed, we'll discuss it during the audit — but most workflows run on your existing stack.
Many first workflows can move quickly after the audit, but timing depends on workflow complexity, system access, data readiness, and security review.
See what pricing would look like for one workflow.
Book a 30-minute audit. We'll map the process, identify the billing unit, and show what would need to be true before a pilot makes commercial sense.
Book a workflow auditNot ready to book? Leave your email and we'll follow up.