Clear
responsibility.
Establish the facts. Define ownership. Focus on the priorities that matter. Adjust the level of involvement when the need changes.
How an engagement is run
Start with what is already known
Each service needs a reliable baseline. If useful recent evidence exists, I validate and use it. Where a genuine baseline is missing, the relevant assessment establishes what needs attention first.
Make ownership explicit
We agree what I own, what stays with your team or existing suppliers, and where decisions need coordination. That clarity is often the difference between several capable people being involved and an outcome actually moving.
Work on fewer, more important priorities
The service is managed around a small number of active workstreams. New requests are weighed against impact, urgency, risk and current commitments. The goal is useful progress, not visible busyness.
Keep project-scale work visible
A recurring service should not quietly absorb a rebuild, major migration or substantial application. When work becomes project-scale, I identify it and scope it separately.
Keep good suppliers
I can work alongside your existing agency, developer, IT provider or internal team. If a supplier is doing good work there is no reason to replace them.
Change the level when the need changes
An organisation may need more involvement during recovery, growth or transition, and less once the environment is stable.
Not a bank
of hours.
The fee reserves an agreed level of specialist responsibility and capacity. You are paying for continuity, context, judgement and the ability to keep the agreed responsibility moving without restarting a project every time attention is needed.
One service may be enough
Most organisations should use only the service they genuinely need. There is no advantage in activating all three simply because they exist. If one area requires ownership, start there.
Services can be combined where the responsibilities are genuinely different. Overlapping meetings, reporting and coordination are consolidated, and duplicated work is not charged twice.
Some organisations need involvement mainly while stabilising suppliers, recovering from technical debt or bringing an unmanaged website under control. The service can reduce or end when the responsibility no longer justifies it.
Start with the problem.
Tell me what needs ownership. I will recommend the most sensible next step and the level of involvement that fits.