
The delivery model
One process. A fixed scope. A measured result.
We start with a diagnostic. We put one process into production. We expand on the result, not on the promise.
Know what is worth changing.
We map the recurring work: its volume, the systems involved and the time people spend completing and correcting it. We identify a first process and model the cost of changing it. Scope, fee and delivery date are agreed before we start. The findings are yours whether or not G66 implements them.
- Current process map and cost baseline
- Data-access and dependency review
- Recommended first workflow and its boundaries
- Implementation estimate with explicit assumptions
- Measurement and acceptance plan
One workflow. Into production.
We connect the systems, build the workflow and test it against representative cases. Approval rules, exception handling and rollback are part of the agreed design. Acceptance is against the criteria agreed at the start; new requirements are scoped before they are added.

- A working process in the agreed environment
- Documented integrations and access boundaries
- Test cases and recorded evaluation results
- Operating instructions and a rollback plan
- Comparison against the starting baseline
Keep the result working.
We monitor the workflow, review exceptions and maintain its models, prompts and integrations. The service defines coverage, response times and the changes included. If you prefer to operate it yourself, you get the handover and training. You will know every third-party subscription the workflow depends on before you sign.
- Quality and exception reporting
- Model and integration maintenance within scope
- Cost and usage visibility
- Documented changes
- A clear route for the next improvement
The scorecard
A better process has more than one number.
Time
Completion time and the effort people still contribute.
Quality
Accuracy, corrections, reopened work and exceptions.
Cost
Tools, models, support, supervision and implementation.
Capacity
Work completed at the agreed quality level.
What we do not do
- Demos, pilots and innovation theatre.
- Automating a broken process so it breaks faster.
- Removing the roles the law assigns to a named person.
- Promising a return before the diagnostic has your numbers.

Clear from the beginning.
Do we have to replace our software?
Can we start with a single process?
Who makes the final decisions?
What does it cost?
Can you help with an existing implementation?
Start with the work. Change what it costs.
Send us the process that costs you most. We will tell you whether it is a candidate for the diagnostic.
