Brief, diagnose, design, build, hand over.
Every engagement follows the same five steps and ends the same way: your team running the result without us.
What happens, and what you hold at the end of each step.
-
Brief
A conversation about the decision you face, the people involved and the deadline.
You receive
Written scope, fee basis and dates -
Diagnose
We read what exists and walk through real transactions with the people who do the work.
You receive
Findings note: what works, what doesn't, what's missing -
Design
Options, then a recommended design sized to the company, not to a textbook.
You receive
Design paper for a management or board decision -
Build
Documents, templates and calendars built in your systems with your team.
You receive
Working documents, trained owners -
Hand over
Your team runs it. We check in after the first cycles and then step back.
You receive
Handover file and a simple self-check
Nothing starts until this is agreed.
A scope is two or three pages. It protects both sides and it is the first thing the board sees.
- 01
The decision or problem, in one paragraph
- 02
What we will do, step by step
- 03
What the company keeps doing itself
- 04
Who on your side owns each deliverable
- 05
Dates for each stage and for handover
- 06
The fee basis and how changes to scope are agreed
- 07
What we will not do (opinions, certificates, representation)
- 08
How information is handled and returned at the end
Three shapes of work.
Project
A defined piece of work with a start, an end and named deliverables: an options paper, a set of process maps, a project report.
Build and run-in
We build the thing, then run it alongside your team for two or three cycles before handing it over: an MIS pack, a board calendar.
Standing support
A fixed monthly routine for a period agreed in writing, for example board papers and registers, with a review point to end or renew.
How we behave inside your company.
- 01Scope in writing first. What we will do, what you keep, the dates and the fee basis, agreed before work starts.
- 02Your systems, where possible. We build in the tools your people already use, so nothing depends on us.
- 03Handover, not dependency. Every engagement ends with your team running the result.
- 04Plain language. Documents written for the person doing the work, not for a filing cabinet.
Do you work on site or remotely?
Both. Walk-throughs and workshops happen in the room; drafting and reviews can be remote. The scope says which is which.
Who owns the documents you produce?
The company does. Everything is built in your tools and handed over with the working files.
Can the engagement be paused or stopped?
Yes. The written scope sets review points and how either side can end the work.