Our approach
A clear process from first conversation to next step
You should understand the purpose of a piece of work before committing to it. Our approach starts with your priorities and turns them into an agreed scope, a practical delivery plan and a clear handover.
How an engagement progresses
-
Step 1: Understand the starting point
We discuss your business, the people who rely on your systems and the issues you want to resolve. Where a technical assessment is needed, we agree the access, depth and scope separately. An initial conversation is not a substitute for a full audit.
-
Step 2: Agree priorities and scope
We identify the desired outcomes, responsibilities, dependencies and exclusions. Your proposal should distinguish professional service fees from licences and other third-party costs, and explain any assumptions that affect delivery.
-
Step 3: Plan and deliver the work
For projects, we agree the sequence, change windows and acceptance criteria before implementation. For ongoing support, we define the supported environment and the process for requesting help. Existing supplier handovers need explicit coordination.
-
Step 4: Validate and hand over
Completed work is checked against the agreed criteria. Relevant documentation and ownership are handed over, with any remaining actions made clear. Support arrangements after a project depend on the agreement.
-
Step 5: Review what comes next
Your business changes. A review helps identify which improvements should be prioritised and which can wait. The frequency and scope of ongoing reviews are agreed with you.
Everyday care or a separate project?
Routine support helps maintain an agreed environment. Migrations, major security rollouts, new offices, substantial website changes and new integrations usually need their own scope. Onsite work, out-of-hours work and third-party costs must be agreed rather than assumed to be included.
-
Ongoing care
Routine care maintains an agreed existing environment. Support hours, onsite coverage and how urgent issues are handled depend on your agreement.
-
Scoped projects
Material changes, such as migrations, security rollouts, new offices or a new website, are scoped separately with their own plan, acceptance criteria and handover.
-
Third-party costs
Licences, cloud consumption, third-party products, advertising spend and hosting costs are identified in the relevant proposal rather than assumed to be included.
Start with the problems you want to solve
Tell us what is getting in the way and we can agree a sensible next step together.