Identify the jobs
Select a manageable group of important customer or member jobs that are difficult or expensive to support today. Include enough variation to test more than a single ideal path.
Proof of Value
Don’t commit to another expensive technology project. Prove the outcome first.
Start with real jobs, relevant systems and agreed success criteria. The purpose is evidence before a wider commitment.
01 / A bounded evaluation
Proof of Value. From £7,500.
A one-off, fixed-scope pilot.
Includes feasibility assessment, agreed customer jobs, relevant configuration, limited integration work within the agreed scope and an evaluation of results.
Final scope and price are agreed before delivery. Feasibility and system complexity determine what can be included. No guaranteed savings, deployment duration or universal compatibility are implied.
02 / The programme
Six stages. One informed decision.
Assess feasibility
Review systems, integrations, available capabilities, data, permissions and policies. Identify dependencies and limitations before agreeing the final fixed scope.
Establish governance
Define permitted actions, user permissions and applicable business rules, including confirmation, approval and escalation requirements.
Configure and demonstrate
Implement the agreed capabilities and demonstrate them against relevant systems and realistic scenarios, including exceptions and failures.
Evaluate results
Assess job completion, reliability, customer effort, human intervention and integration and operational requirements. Examine the potential to reduce existing expenditure and complexity.
Decide whether to expand
Use the evidence to assess what broader deployment would involve, which dependencies remain and whether the value justifies further investment.
03 / Measure the outcome
Agree what success means before delivery.
Define completion for each job, including how it will be confirmed in the relevant systems. Establish a baseline where possible and assess normal cases, variations, incorrect permissions and situations requiring human judgement.
- Job completion: did the agreed outcome occur, within policy?
- Reliability: were failures, partial results and retries handled appropriately?
- Customer effort: was information repeated, and was the result understandable?
- Human intervention: what remained necessary, and what was avoidable rework?
- Operational requirements: what integration, support and maintenance work remains?
- Commercial potential: which existing costs or complexities could realistically be reduced?
Evaluation should identify limits as clearly as successes. Broader deployment may depend on additional integrations, better data or policy clarification. The outcome may be expansion, a revised scope or a decision not to proceed.