How we work
Delivery certainty, not just software.
Most vendors hand over a platform and disappear. Plugseal ships the change — a new RBI circular, a new product, a new integration — on a named cadence, with the same team that built the thing in the first place.
The delivery model
Five phases, each with an owner on both sides.
01
Discovery
We map your product mix, branch hierarchy and current stack, and agree what the first release has to prove.
02
Configuration
Products, workflows, rules and approval matrices are configured — not coded — against that map.
03
Pre-prod validation
Your team runs real files end to end in a pre-production environment before anything reaches customers.
04
Production release
A scheduled cutover with named ownership at each gate and a documented rollback position.
05
Managed support
Ongoing tickets, enhancements and regulatory changes handled on a published cadence.
Typical duration, artefacts produced and the people involved on each side are documented per engagement — [ ] to be published here.
Cadence and release discipline
How the work actually moves.
Ceremonies and cadence
Sprint rhythm, grooming, planning and review, plus a written weekly summary to your team. Exact cadence: [ ]
Environments
Dev → pre-production validation → production release, with named ownership at each gate.
Release discipline
Every release carries a rollback position agreed before cutover. Release window: [ ]
Escalation
A defined path from ticket to engineering owner, with response and resolution targets per tier: [ ]
Regulatory change handling
A circular becomes a scoped change, an estimate, and a shipped release.
This is the part that separates a delivery partner from a product vendor. When the RBI publishes a change, we scope what it touches in your configuration, estimate it against the current sprint, and ship it on the standard release cadence — rather than opening an unplanned project every time the rules move.
What we don’t do
We don’t rip and replace
Finnova integrates with your core, accounting and reporting systems. Migration off a working system is your decision, not our default.
We don’t take undefined scope
A change gets an estimate and a release slot before it starts. No open-ended retainers.
We don’t hand over and leave
Managed support is part of the engagement, not an upsell after go-live.
Want the delivery detail in writing?
We’ll walk you through the cadence, the environments and the SLA structure against your own product roadmap.