Establish the foundations.
The applicant and staff journeys. Required forms, document lists and approval rules. Roles, access requirements and source-system interfaces.
Strategy & discovery ↗Service 02 / Build
Turn complex processes into clear, usable software for the people doing the work and the people accessing the service.

The commission / an interactive walkthrough
Explore how this service moves from your starting information through a scoped build to testable acceptance and handover.
Your starting material
We start with the users, records, constraints and decisions that the commission must respect.
Share a representative example with private records removed; detailed access follows an agreed secure process.
Specific deliverables, assurance and acceptance depend on the agreed brief.
Explore our delivery process ↗Make the process work for everyone using it.
Where it fits
Account opening, applications, employee services, claims and institutional operations.
What we can deliver
System sketch / Illustrative service-portal workflow
Collect the information needed for the specific service. Show requirements, field errors and a clear next step.
Illustrative service architecture. Detailed rules and responsibilities are agreed for each commission.
A useful starting point
Acceptance & handover
HandoverWorking software, documented workflows and agreed acceptance evidence.
From requirements to operation
The applicant and staff journeys. Required forms, document lists and approval rules. Roles, access requirements and source-system interfaces.
Strategy & discovery ↗Implement the agreed scope in reviewable increments. Check user journeys, integration boundaries and failure conditions against the requirements, with unresolved decisions kept visible.
Review the delivery stages ↗Complete journeys, including rejected or incomplete applications. Permissions across applicant, reviewer and administrator roles. Document handling, status changes and acceptance scenarios.
Working software, documented workflows and agreed acceptance evidence.
Working examples and archive captures show their stated maturity. The service scope is a commissioning capability, not a claim that every listed system has been deployed for a client.
A related working example
A connected journey for personal and business account documents, shared details and a downloadable application pack. Bank review and activation remain separate.
Working application-preparation portal
Explore the project ↗We establish the authoritative sources, mapping rules and access boundaries first. Migration and integration scope includes reconciliation, error handling and recovery responsibilities; production writes and cutover require an agreed review.
Yes, where access and integration are authorised. We first establish ownership, documentation, dependencies and the boundaries of any replacement or connection. A commission does not require abandoning a system that already works.
We prioritise complete user tasks rather than an arbitrary feature count. Scope, exclusions, dependencies and acceptance scenarios are agreed before implementation, with review points for changes.
We identify data owners, information categories and permitted actions during discovery. Controls, retention, specialist assurance and any data-processing responsibilities are scoped against the actual service. A studio credential does not certify your future system.
Documentation, access ownership, training and operating responsibilities are agreed before release. Maintenance, incident coverage and further development have an explicit scope; they are not assumed to be unlimited.
Scope, assumptions, dependencies and changes recorded against the brief.
User journeys, permissions, failure conditions and operating requirements reviewed before release.
Source, documentation, training and recovery responsibilities agreed as part of handover.
Start a conversation
Bring the brief, the source material and the constraints. We will help define the scope and the right next step.