Engagements
Start with a workflow.
Finish with an assessed result.
Define the decision, evidence and acceptance test together. Expand once the receiving team can use the output.
One workflow.
A defined acceptance test.
- Decision
- Review a monthly transport account
- Evidence
- Signed terms · event records · invoices
- Deliverable
- Reconciled account + exception file
- Acceptance
- Source traceability · calculation checks
The engagement
A clear sequence, with decisions at each stage.
- 01
Frame the decision
Name the owner, workflow and the result that would be useful.
- 02
Check the evidence
Assess a representative sample and resolve access dependencies.
- 03
Deliver and evaluate
Run a paid pilot against agreed acceptance criteria.
- 04
Operate and expand
Define recurring scope once the output has proved useful.
What a pilot includes
A scope your team
can review.
The proposal names the deliverable, dependencies, milestones and commercial terms.
Start the conversationGovernment and public-enterprise engagements
Scope, eligibility and delivery responsibilities follow the institution’s applicable procurement process. Specialist engineering or implementation partners can be included where needed.
Commercial structure for recurring use
Scope may be agreed by workflow, asset or case volume, fleet, site or institution. Integrations, inspections, third-party data and service commitments are specified in the proposal.
The next conversation
Discuss your next programme.
Tell us the decision, the institution and the evidence available. We’ll help define a focused first engagement.
Start a conversationTalk to the desk.
Tell us who you are and the decision you are pricing. The first conversation costs nothing. A reply comes on working days.
Or write to [email protected].