02 · Custom software
Custom operational software built around how the work actually runs.
Internal software, field applications, portals, and evidence systems for work that generic products do not fit.
The problem
What this engagement needs to resolve.
A collection of tools no longer supports the operation, while a generic platform would force the process around the software.
Deliverable
A tested, documented system with a defined ownership and handover model, from data and integrations to daily workflows.
Client input
A decision-maker who can set priorities, access to subject-matter experts, and timely scope and acceptance decisions.
Commercial shape
A clear starting point, then a responsible scope.
- Commercial starting point
- Substantial bespoke software engagements typically start around £25,000.
- Duration
- Confirmed after the workflow, integrations, and acceptance criteria are scoped.
What is covered
The practical shape of the engagement.
The exact scope is agreed around the operational outcome, the systems involved, and the evidence needed to accept the work.
- 01
Operational web applications
- 02
Field and mobile workflows
- 03
Portals and evidence systems
- 04
API and system integrations
- 05
Data migration
- 06
Testing, training, and handover
Scoping questions
Questions before assumptions.
- Who owns the decision at each step?
- What needs to work offline?
- Which systems must remain the source of truth?
- How will success be measured after rollout?
What changes the scope
- Integrations and data migration
- Roles, users, and environments
- Offline requirements and assurance burden
- Deployment and support model
Related routes