ENGAGEMENT MODELS
Pick the model that puts the risk in the right place.
Products, software delivery and talent services all contract differently. Here is every model we offer, what each one suits, and what you are on the hook for in each — so the commercial conversation starts somewhere sensible.
MODEL COMPARISON
Who carries scope risk, and who carries delivery risk.
Almost every dispute we have seen starts with a mismatch here. Fixed scope moves risk onto us and takes flexibility away from you. Capacity models do the reverse. Neither is better — they just suit different work.
MODEL
BEST WHEN
YOU ARE ACCOUNTABLE FOR
Product licence
You want the software and your own team will run it.
Configuration, getting people to use it, and designing your own process.
Fixed-scope project
The requirements hold still long enough to write down what done means.
Deciding things on time, giving us access, and controlling scope change.
Outcome-based pod
You can measure the outcome, but nobody knows the exact path yet.
Prioritising the outcome, and a product owner we can actually reach.
Capacity pod / augmentation
You already have the roadmap and just need more hands.
Direction, prioritisation, and managing the delivery.
RPO / managed program
You want the hiring function run, not just staffed.
The hiring decisions, showing up to interviews, and giving us baseline data.
Hire-Train-Deploy
The same role keeps coming up and nobody can find those people.
Defining the role standard and the readiness bar, with us.
CONTRACTING ROUTES
How the agreement itself gets signed.
ROUTE 01
Direct master agreement
A master service agreement with your entity, with regional schedules and rate cards under it.
Rate card by role family
Regional legal schedules
Direct escalation path
ROUTE 02
MSP / VMS program
We deliver inside your managed service program, submitting and reporting through the VMS.
VMS-native submission
Program SLA compliance
Consolidated invoicing
ROUTE 03
Framework or subcontract
Vendor-of-record and supply-arrangement channels, or delivering alongside the integrator you already have.
Framework-compliant pricing
Defined scope split
Joint governance cadence
COMMERCIAL QUESTIONS
What we will and will not agree to.
Saying this early saves a month of legal review later. It occasionally loses us a deal, which is the point.
Will you sign an SLA with penalties?
Yes — on managed support and RPO, where the measures are things we control and the baseline data exists. We will not take penalties on outcomes we cannot influence. Your internal interview turnaround is the usual example.
Can pricing be outcome-based?
Partly, on pods and RPO — a component can ride on agreed measures. Fully outcome-priced engineering only works when the outcome, the measures and every dependency are written down. That is rarer than people think.
How do rate cards change over time?
Fixed for the initial term, then adjusted on an index or a schedule we agreed. It goes in the agreement rather than being reopened every year.
What are the exit terms?
Notice, knowledge transfer, data export and how long we support you afterwards — all settled before signature, not while you are trying to leave.
Bring your procurement constraints early.
Tell us the route and the risk posture you need. We will tell you straight whether we can work that way.