Commercial route

Buy the right to run. Subscribe to stay current and keep improving.

Written for CFOs, CIOs, procurement and private-equity operating partners. Buy + Assure separates two things that subscription software normally bundles: the right to operate the software, and the service that keeps it current, secure and improving.

Discuss Buy + Assure Compare with subscription

The structure

Two components, deliberately separated.

One is capital, one is recurring. Separating them is what makes the fallback position meaningful — you cannot have a continuity right over something you never bought.

Capital — paid once

BetterWrk Operating Licence

A perpetual right to operate the licensed environment at the agreed scope.

Perpetual right to run the licensed applications for your organisation
Scope defined by entities, users and modules
Portfolio licensing where a group or fund holds multiple operating companies
Your data, configuration and customer-specific capability remain yours
Capitalisable in most structures — check with your own advisers

Recurring — paid annually

Assure subscription

What keeps a licence from quietly becoming a liability.

ProcessScout, continuous improvement and included Fit Capacity
Managed Runtime, or support for your own deployment
Security patching, version currency and regulatory updates
Support, incident response and the availability commitment
Assurance: the testing, approval and governance around every change

The honest warning

Perpetual software that nobody maintains does not stay compliant. Tax rules change, statutory filings change, security vulnerabilities are discovered. We will not tell you that an unsupported licence remains fit for payroll or finance indefinitely, because it does not.

Continuity

What happens if BetterWrk is no longer in the picture.

This is the question Buy + Assure exists to answer. Ask it early — it is much harder to negotiate once you depend on the software.

Qualifying fallback release: Where the defined qualifying conditions are met, you receive a release you can continue to operate, together with the documentation needed to run it. The conditions are written into the agreement rather than described in marketing terms.
Self-hosting: Available to qualifying Buy + Assure customers, in your own cloud account or data centre. Support boundaries and shared responsibilities are defined in writing before you commit.
Regulated-module limitations: Some payroll and finance capability depends on jurisdiction content that must be maintained continuously. Where a module cannot responsibly be operated without that maintenance, we say so in the agreement rather than leaving you to discover it.
Source-code escrow: Available where your risk position requires it, with a named agent and defined release conditions.
Data and configuration rights: Your data, your configuration and any customer-specific capability built for you remain yours, exportable in a documented format throughout the relationship.
Transition assistance: Defined exit assistance obligations, priced and scoped in advance rather than negotiated during a dispute.

Which route

How to choose.

Comparison of Adaptive Subscription and Buy + Assure
	Adaptive Subscription	Buy + Assure
Upfront commitment	Low	Operating Licence paid upfront
Recurring cost	Single recurring fee	Assure subscription, typically lower than full subscription
Accounting treatment	Operating expense	Licence often capitalisable; check with your advisers
Deployment	Managed Runtime	Managed Runtime, customer cloud or self-hosted where qualifying
Continuity position	Data and configuration export	Export plus qualifying fallback operating right and escrow options
Portfolio structures	Per company	Portfolio licence across operating companies
Best suited to	Most operating businesses	Larger, regulated, group and portfolio buyers

Nothing on this page is tax, accounting or legal advice, and the definitive terms are the ones in your agreement.

Portfolio licensing

One licence, many operating companies.

For funds and groups, a portfolio Operating Licence turns adding a company into a deployment decision rather than a procurement cycle — while each operating company keeps the configuration and gated capability that makes it itself.

Portfolio operating model

Licence scope defined at fund or group level
New operating companies deployed against the existing template
Capability built for one company can be offered to others, with their agreement
Standard controls and comparable reporting across the portfolio
Continuity position held at portfolio level rather than negotiated per company

Bring procurement into the room early.

We would rather work through licence scope, continuity conditions and self-hosting limitations at evaluation than at contract signature.

Discuss Buy + Assure Start with a Trail Map