Case study
Internet banking at Sage Grey
Leading delivery of an internet banking application, and the design of a NestJS Backend-for-Frontend that sits in front of a core banking service.
- Product Lead
- scope, backlog and release plan
- NestJS BFF
- over Peerless core banking
- Client apps: The internet banking application clients use. They talk to one API, not to the core.
- NestJS BFF: Middleware that gives client apps a single, secure and consistent API layer.
- Peerless: The core banking service the BFF wraps and integrates with.
- Integrations: Third-party integrations, delivered as their own workstream alongside product and backend.
Context
Sage Grey Technologies builds practical digital solutions across sectors. This project is an internet banking application that has to connect to the Peerless core banking service.
Problem
Client applications should not each integrate with a core banking service directly. They need one secure, consistent API, and delivery has to be planned so that product, backend and third-party integration work stay aligned.
My role
I lead product delivery. I translate business requirements into scoped features, a prioritised backlog and a phased release plan, break features into engineering tasks, assign them across the team and track progress.
Approach
A NestJS Backend-for-Frontend wraps and integrates with the core banking service, giving client apps a single API layer. I drove its design, and worked across the product, backend and third-party integration workstreams to unblock developers and keep the build aligned with business requirements.
Outcome
The project is in active delivery. Details are kept general here out of respect for the employer and the client.
Decisions
A BFF instead of direct core access
The BFF isolates client apps from the core banking service, so the front ends depend on one consistent contract.
Phased release plan
Scoping features into a prioritised backlog and phased releases keeps a fully remote team shipping against business requirements.
Stack
NestJS · TypeScript · Node.js · REST APIs
Product leadership and backend design on the same project: scope the work, then design the layer it depends on.