Client work, published with permission.
The story separates what can be stated publicly from what must stay confidential, and links outcomes to approved evidence.
The problem being explored
Buying a first home involves many steps and many parties. The bank's mortgage journey for first-time buyers ran across several internal systems and outside services, from the moment an offer was accepted to the day the buyer collected their keys.
What made delivery difficult
The bank wanted one platform for the whole journey. The hard part was not the screens. It was everything that had to connect to them.
- Many systems. The platform had to work with a range of internal systems and outside services.
- Information that must not go missing. Requests, responses and notifications had to flow reliably at every stage.
- Visibility. The bank needed to see what was happening at each step and recover quickly when something failed.
- First-time buyers. People new to buying a home needed a journey that was clear and easy to follow.
Connect product thinking to implementable decisions
We led the design and delivery of the platform with a cross-functional engineering team.
- Solution architecture and technical leadership
- Integrations
- End-to-end data handling
- Delivery automation
- Running it well
- Acceptance testing
How the work was shaped
The work maps to seven stages of our delivery lifecycle, from Discovery to Closure & Handover.
- Discovery. Mapped the end-to-end process, the people, every system and what success would look like.
- Delivery Planning. Turned an unclear, multi-system problem into a phased roadmap of testable deliverables.
- Build & Test. Used clear contracts between systems, retry rules and traceable messages, with pipelines for releases and testing.
- UAT & Launch Readiness. Added regular demos and agreed acceptance criteria.
- Operational Readiness. Put monitoring, logging and incident playbooks in place before go-live.
- Hypercare. Kept close watch on the live service after launch.
- Closure & Handover. Passed day-to-day running to the bank's teams.
Technology and structure
The platform sits at the centre of the journey, with a reliable layer of integrations around it.
- One journey platform. Manages each mortgage case from accepted offer to key collection.
- An integration layer. Connects the platform to the bank's own systems and to outside services, using agreed contracts between them.
- Data handling. Checks, transforms and routes data at each step.
- Notification orchestration. Sends the right message at the right time, in a predictable order.
- Monitoring and logging. Shows how each part is running and where a case is at any moment.
Risk, assurance and release boundaries
Reliability was designed in, not added at the end.
- Safe retries. Requests that are repeated never create a duplicate action.
- Clear transaction boundaries. Each step either completes fully or not at all.
- Traceable messages. Every event and message can be followed from start to finish.
- Automated testing. Every release checked before it reached users.
- Incident playbooks. Agreed steps for spotting and fixing problems fast.
- Staged releases. New versions went to groups of users in turn, after acceptance testing.
What can be stated publicly
The bank got a production-ready platform for the full first-time buyer journey.
- Ahead of schedule. Short feedback cycles and automation meant deadlines were met, and the project finished early, which gave the bank extra time for wider user testing.
- A smoother rollout. The early launch increased satisfaction among stakeholders and users, made the journey easier for first-time buyers and reduced the workload on the bank's teams.
- Fewer repeat defects. The integration design and monitoring cut repeat integration defects.
- Easier to grow. Adding new partners and features became faster and safer.
What transfers to the next programme
What we carry into similar work.
- Map before you build. Time spent mapping the whole journey up front turned an unclear, multi-system problem into a plan everyone could follow.
- Integrations are the product. In a journey like this, how systems talk to each other matters as much as what users see.
- Phase it so people can test it. Small, testable releases gave the business real feedback early and made the deadline achievable.