The Outcome Contract: the terms, in full.
Every promise on this site rests on one clause structure. It is written here in plain English so you can read what we commit to, and what we don't, before you ever speak to us.
- Outcome measured on the agreed date, by the same method as the baseline.
- Criteria met: the engagement completes and moves to Run. Defect support continues for the window in your SOW.
- Criteria not met and attributable to our delivery: remediated at our cost, up to the bound in the SOW.
- Not met and not attributable: remediation does not apply. Excluded causes are stated up front: an unmet client dependency, a scope change not agreed in writing, or a cause outside our reasonable control.
Who carries which risk
| Price certainty | Delivery overrun | Result shortfall | Access and decisions | |
|---|---|---|---|---|
| Hourly consulting | Youyou carry it | Youyou carry it | Youyou carry it | Youyou carry it |
| The Outcome Contract | UsVRdigital carries it | UsVRdigital carries it | Usattributable to us, bounded | Youaccess and decisions |
The ten clauses
01Before any work starts
We agree, in writing, all four of these — or we don't start:
- Success criteria, each with a stated measurement method, in your numbers.
- A baseline for each criterion, measured with that same method before work begins.
- A fixed price. We do not bill by the hour.
- An outcome measurement date, on or after go-live, when each criterion is re-measured the same way.
02Fixed price and change control
The price is the price. Any change to scope, success criteria, timeline or price is documented as a written change order and takes effect only once both sides sign it. Neither side performs, or is billed for, work outside the signed scope without one — in either direction.
03After go-live: defect support
For a support window stated in your SOW, we fix at no charge any deliverable that doesn't conform to the agreed specification. This is ordinary warranty support — separate from, and in addition to, outcome remediation below.
04Outcome remediation — the promise, precisely
If, at the outcome measurement date, a success criterion is not met, and the shortfall is attributable to our delivery, we remediate it at our own cost, up to a bound stated in your signed SOW. That bound is agreed before any work starts and before any fee is paid, so there is no gap between what we say publicly and what you can hold us to. It is a genuine remedy, not a token one.
05What remediation does not cover
A shortfall is not attributable to our delivery, and remediation does not apply, where it results from causes including:
- a client dependency listed in the SOW (access, data, approvals, named people) that was not met;
- a scope change that was not agreed in writing under change control;
- data below the readiness standard stated in the SOW, or changes to the environment made by others after handover;
- a cause outside our reasonable control — including a failure or outage of a third-party platform such as SAP or BTP that we did not cause, or of your own infrastructure.
We say this up front because a remediation promise with no exclusions would be either dishonest or unaffordable. This one is neither.
06If dependencies stall
If a client dependency remains unmet for the period stated in the SOW, the engagement pauses rather than drifting. If it stays unmet, the SOW sets out restart terms — including how long the original price holds — and either side's right to end the engagement. Milestone invoices already due remain payable.
07Leaving
Either side can end an engagement on the notice and exit terms stated in the SOW, or immediately for a material breach that isn't remedied when asked, or on insolvency. On exit we hand over every deliverable you've paid for in a usable format, return or securely delete your data on your instruction, and provide the transition assistance set out in the SOW. Deliverables you have paid for are yours.
08Liability
Each side's total liability to the other under a SOW is capped, at a level tied to the fees paid and stated in that SOW. The cap is mutual — it limits our liability to you and yours to us equally. Nothing excludes or limits rights that cannot lawfully be excluded, including under the Australian Consumer Law, and we do not attempt to cap liability for fraud, wilful misconduct, or death or personal injury caused by negligence — the law doesn't allow it, and a clause that tried would itself be at risk of being unfair.
09Data, privacy and AI
Client data is handled on a minimum-necessary basis, never used to train models for other clients, never sold. Any AI we deliver that touches a consequential decision keeps a human in the loop by design and identifies itself as AI. The full commitments are on our Responsible AI and Privacy pages, and the contract can never promise less than they do.
10When this isn't the right model
The Outcome Contract applies to delivery, and only when a genuine outcome can be defined and measured. Where it can't yet be — exploratory or advisory work, an estate nobody has mapped — we run a paid Discovery phase first, as a fixed fee or on time-and-materials, which produces the success criteria, baseline and fixed price for the delivery phase. Blended engagements of that shape are common and are stated as such in the SOW. How the two models compare, dimension by dimension.
Proposed addition, drawn from the existing FAQ answer. Founder to approve. Price intentionally redacted.