Outcome
We write down what the service has to do for the person using it before anyone names a product. If that sentence cannot be written, the requirement is not ready and we will say so.
FOR ESTABLISHED, COMPLEX AND PUBLIC-SECTOR UK ORGANISATIONS
Give your team a clearer view. And fewer workarounds.
When information sits across departments and ageing systems, everyday work slows down. We scope integrations, migrations, portals and reporting around the services you need to keep running, with clear responsibilities and review points.
01 · Four delivery principles
Control
Your team gets a written list of what personal data the system touches, where it goes, who can see it and how long it is kept, in the format your assurance process asks for.
Adoption
We sit with the people who will use it and watch them do the job as it stands. What they work around tells us more than a requirements workshop does.
Continuity
Before release, we agree the continuity plan, acceptance checks and recovery options your systems support. Any downtime, rollback limits or supplier dependencies are identified before a switchover is approved.
02 · Visible delivery
Complex does not have to mean opaque.
We break larger change into controlled stages with working demonstrations, clear decisions and named ownership throughout.
- 01Platform modernisation and migration
- 02Department and supplier integration
- 03Data quality, reporting and role-based access
- 04Accessible customer and staff services
- 05Governance and assurance evidence
- 06Monitoring, support and continuity planning
03 · Ways we engage
Three ways to engage us and what each one does not cover
Discovery and options appraisal
A fixed piece of work that maps the systems in use, the data held in each one, the manual steps people have built around the gaps and the realistic options for change with costs and risks written against them. Scope and price are agreed before it starts. It suits a team that has to put something in front of a board, a committee or a procurement route and needs the detail on paper first. It builds nothing. If the decision is already made and funded, skip it and go straight to a delivered stage.
One delivered stage
One defined part of the estate taken from agreed scope to live use: a public-facing form and the case record behind it, an integration between two systems that currently exchange data by spreadsheet or a reporting view a service manager can open without asking anyone to run a query. Scope, acceptance criteria and the handover pack are settled before work starts. It suits a first engagement where you want to watch how we behave under your process. It does not reorganise anything around it.
Multi-stage programme
A larger project can be divided into separately agreed stages, each with its own deliverables, review and release decision. We confirm the capacity, specialist input and supplier responsibilities each stage needs before committing. Your organisation retains a named decision-maker for scope and acceptance.
04 · Working inside an operation that cannot stop
Plan around the service. Make each change reviewable.
We agree release windows, testing and recovery around the service you need to maintain. Where systems allow parallel running, it can be part of the plan. Where they do not, dependencies and any interruption need to be understood before a release is approved.
Your team needs to know what will change and how to use it. Training, documentation, access and support responsibilities are scoped alongside the build, so the handover has a clear owner on each side.
05 · Questions procurement teams ask
Before you start. Practical questions, answered.
Useful details to help you decide on the next step.
Do you hold Cyber Essentials or ISO 27001?
We do not hold these certifications. We agree the security requirements and identify which controls, hosting locations and supplier evidence a proposed solution can provide before work starts. Any mandatory certification requirements need to be established during scoping.
Can you work inside our supplier assurance and DPIA process?
Yes. We complete your questionnaire in your format rather than sending a generic pack, and we supply the data-flow detail a DPIA needs: what personal data the system touches, where it moves, who can see it, how long it is kept and how it is deleted. If a control is missing, that is written into the answer rather than left blank. How engagements run
Where will our data physically sit, and who else can reach it?
Hosting and processing locations depend on the proposed architecture and suppliers. We identify those locations and the parties involved before you approve the design. If UK-only processing is required, that becomes a constraint to check across the full service, including any external tools.
We are mid-contract with an incumbent supplier. Can you work alongside them?
Yes. The usual arrangement is that the incumbent keeps the system of record and we build the layer around it, working against their published interface or an agreed export rather than reaching into their database. Boundaries are written down before anything starts, including who is called first when something fails, so neither side can blame the other later.
If we end the engagement, can we take everything with us?
The scope records ownership of custom work, your business accounts and data, and any third-party licences or managed services. We agree the access, documentation and export arrangements needed for handover before building, so you understand what can move and any dependencies that remain.
How do you handle WCAG 2.2 AA accessibility on public-facing services?
Usually by building to the standard and testing rather than claiming a pass. Templates are checked with keyboard-only navigation, a screen reader and automated contrast testing, and the accessibility statement records what still fails and when it will be fixed. Where your organisation already pays for an accessible design system, we build to that instead of charging you for another one. Websites and platforms
06 · Where to go next
The next useful pages depending on which pressure is nearest
FOR PRIVATE HEALTHCARE AND CARE PROVIDERS
Make the admin easier
Clearer websites and booking journeys help people find the right service.
EXPLORE → FOR INSURANCE BROKERS AND MGASLess rekeying
Explore document handling, enquiry workflows and connections between policy, CRM and finance systems.
EXPLORE → SCOPE · BUILD · REVIEW · HANDOVERKnow what you are buying
We agree the deliverables, price and responsibilities before building.
EXPLORE →NEXT · Tell us what you want to improve
Bring us the difficult change. We will make the next step clear.
Start with the outcome, constraints and what must not be disrupted. We will map a controlled route forward.