01 — MAP
Trail Map
A paid diagnostic with a written deliverable. Fixed price, shown and paid at checkout. Typically two weeks.
Yours to keep whatever you decide next. Credited against a launch where one follows.
- Home
- Pricing
Commercial model
Pay for the assessment. Launch the right system. Subscribe to the capacity that keeps it improving.
Three commitments, taken in order, each one informed by the last. You are never asked to sign for a full software replacement on the strength of a demonstration.
The three commitments
02 — LAUNCH
Launch
Scoped from the evidence in your Trail Map, not from a wishlist. Configuration, migration, integration and the initial customer-specific changes.
Priced against an agreed Fit Blueprint, and acceptance-tested against the same document.
03 — RUN AND IMPROVE
Run and improve
Recurring. Applications, ProcessScout, Managed Runtime, support and an included allowance for approved customer-specific improvements.
Priced on your people, entities and modules — not on how many tickets you dare to raise.
Two purchasing routes
Subscribe to the environment — or buy the right to run it.
The software is the same. What differs is how you hold it, what you own outright and what happens in a scenario where BetterWrk is no longer in the picture.
Most customers
Adaptive Subscription
The straightforward route. Lower upfront commitment, everything recurring, one number to plan against.
- Applications, ProcessScout and Managed Runtime on a recurring basis
- Included Fit Capacity for approved customer-specific improvements
- Current releases, security updates and platform maintenance included
- Support and the accountability that goes with it
- Data and configuration exportable throughout
Larger, regulated and portfolio customers
Buy + Assure
Buy the right to run the environment, then subscribe to keep it current and keep it improving.
- Upfront BetterWrk Operating Licence
- Continuing ProcessScout, runtime, assurance and improvement subscription
- Potential qualifying fallback operating rights
- Self-hosting and customer-cloud options where they apply
- Source-code escrow options and portfolio licensing
Fit Capacity
Unlimited feedback. An included allowance for approved improvements.
Continuous improvement needs a commercial model that does not punish people for reporting problems. So telling us something is broken is always free. What consumes capacity is us building something new for you specifically.
Fit Capacity is that allowance, included in your subscription and sized to your environment. Approved customer-specific improvements draw from it. You see what a proposal will consume before you approve it.
Never consumes Fit Capacity
- Giving feedback, however much of it
- Defects in BetterWrk software
- Security fixes and vulnerability remediation
- Platform maintenance and version currency
- Improvements we make to the products generally
- Support, training questions and configuration advice within normal use
Draws from Fit Capacity
- Customer-specific capability built for your organisation
- New integrations to systems outside the suite
- Substantial reconfiguration of a workflow after launch
How the recurring price is built
What actually moves the number.
There is no feature matrix here with forty rows and three ticks. The price is driven by the size and shape of your environment.
Employee count
The main driver for People and Payroll, and the best single proxy for the size of the environment overall.
Legal entities
More entities means more separation, more approval structures and more reporting. Multi-entity operations cost more to run correctly.
Selected modules
You pay for the applications you use. Adding one later is a scope change, not a re-negotiation of everything.
Payroll population
Where payroll is in scope, the number of people paid and the countries they are paid in.
Integration count
Each connection to a system you are keeping is built and then maintained. Maintenance is the part people forget to price.
Expected improvement pace
How much Fit Capacity you want included. Businesses in the middle of a change programme want more than steady-state operations do.
Variable usage
A small number of things are genuinely consumption-based — payroll runs, e-signature volume, document storage beyond the included allowance, and outbound message volume. These are stated in your agreement rather than discovered on an invoice.
Straight answers
Pricing questions we get asked.
The Trail Map has a fixed published price at checkout. Launch and the recurring subscription depend on your entity structure, module selection and integration count, and we would rather give you a defensible range from evidence than a headline number that turns out to be wrong. Ask us and you will get a range, not a false-precision quote.
Usually against three things: the software you stop paying for, the operational time the Trail Map has already sized, and the delay cost in a specific workflow such as contract-to-cash. The Trail Map exists partly so that this business case is built on measured evidence rather than vendor arithmetic.
You either prioritise within the allowance or buy additional capacity. You will know before you approve a change what it consumes, so this is a planning decision rather than an overrun.
No. Product improvements, security fixes and version currency are what the subscription buys. A separate charge for keeping your software working would defeat the point of the model.
Yes, and many customers should. The Trail Map usually identifies one workflow where the return is clearest. Starting there and integrating with what you keep is lower risk than a suite-wide replacement.
Get a range built on evidence.
Start with a Trail Map, or tell us about your operation and we will come back with an indicative range and what would move it.