Extend
Improve an existing system when it already holds reliable records and supports client access.
Check: licensing limits and the changes required.
Our approach
A clear process.
Shared responsibility.
Understand the problem. Choose the priorities. Deliver the work. Check the results. We agree the scope and responsibilities with you before work begins.
From understanding to action
Four stages, shaped around your scope.
A focused assessment may stop at recommendations. Delivery engagements continue through the stages agreed in your scope.
Assess
Understand the business need, review existing systems, and compare practical options.
What you receiveAn assessment of needs, options and risks.
Prioritize
Agree what comes first based on cost, dependencies, and the capacity to deliver.
What you receiveA phased plan explaining priorities, costs, and who is responsible.
Design & deliver
Define the solution, guide the agreed build, and check it against agreed requirements.
What you receiveA verified pilot or implementation with handover documentation.
Adopt & measure
Support handover and training, then review use and performance to identify improvements.
What you receiveAn adoption and performance review with recommended next steps.
What working together involves.
Our role: investigate the need, make recommendations understandable and coordinate the technical work within the agreed scope.
Your role: nominate a decision owner, involve the people affected, provide relevant information and review the work at agreed approval points.
When a check reveals a problem
We record the issue and explain its effect on the agreed requirements, cost, or timing. Together, we decide whether to revise and retest, reduce the scope, or pause before committing further. The decision owner approves the next step based on the evidence available.
Illustrative example
A client portal, built in the right order.
A professional services firm wants clients to track onboarding. First, it needs consistent records and clear responsibility for updates. This scenario illustrates the approach; it is not a completed client engagement.
Agree the process→Prepare records & access→Pilot the portal→Review adoption
See responsibilities and approval checks
| Step | People involved | Evidence to proceed |
|---|---|---|
| Agree the process | The business owner and onboarding staff. | Agreed statuses, handoffs and responsibility for each update. |
| Prepare records & access | Record owners and the technical team. | Usable sample records and tests showing each user can access only the right information. |
| Pilot the portal | Representative clients, staff and the delivery team. | Users can complete the intended tasks; errors and support needs are recorded. |
| Review adoption | The service owner and leadership sponsor. | Actual use, support effort and operating costs inform whether to expand or refine. |
Extend, buy or build?
Choose around the workflow, operating costs, and the resources available to maintain it.
If a key assumption is uncertain, such as a supplier’s integration capability, test it before making the larger commitment.
Explore technology strategy & roadmapping →What to bring to the first conversation.
You do not need a finished specification. A brief outline of these four things gives us a useful starting point:
- Your priorities: what you want to improve and what a useful result would look like.
- Existing systems: the tools, suppliers, and workflows involved.
- Constraints: key dates, budget expectations, and the capacity available for change.
- A decision owner: who can agree priorities and involve the people affected.
We can help clarify any gaps during the discussion.