Public-sector modernization

Client

A Dutch national administrative programme operating at national scale, handling personal-budget payments to a nationwide beneficiary base in the hundreds of thousands. The platform is integrated with multiple adjacent national systems covering identity, healthcare administration, payments, and audit.

The programme had been built up over more than a decade across multiple delivery partners and political cycles. By the time Lemraj engaged, it was running with a steadily increasing operational risk profile, fragmented ownership, and a critical dependency on end-of-month and end-of-year processing windows that had become a recurring source of operational concern.

The constraints that shaped the work

This was a regulated environment with hard constraints on how a modernization could be designed and delivered. The architecture choices on this engagement were driven less by technical preference and more by what the programme could absorb without breaking.

The change-control regime was appropriate to the risk class of the programme but expensive to operate against the existing architecture. A multi-year rebuild was politically and operationally untenable — the programme had to keep running through any modernization. Adjacent national systems imposed integration contracts that were not negotiable. And the supplier landscape — multiple delivery partners, layered contractual responsibilities — meant any new architecture had to be readable and operable across organisational boundaries, not only within Lemraj's reach.

These constraints were the design environment, not obstacles to it.

What we did

Lemraj engaged across architectural assessment and modernization delivery, working alongside the client's in-house engineering team and adjacent delivery partners. The contributions were:

A full architecture and dependency assessment of the platform and its integrations with adjacent national systems. A target architecture designed against the constraints above — change-control regime, supplier landscape, in-house operating capacity — rather than a reference architecture applied as a template. A phased delivery plan that allowed each subsystem to be replaced or replatformed under the existing change regime, without a single-step cutover. Implementation of selected subsystems and integrations, in collaboration with the in-house team and other delivery partners. And operational design — observability, exception handling, replay, and runbooks — built in as part of the modernization rather than added afterwards.

Outcome

A documented target architecture and phased delivery plan, owned by the client and shared with adjacent delivery partners. Replacement of selected subsystems running in production, with reduced operational risk and clearer ownership of integration boundaries. A reduction in the volume of operational reconciliation work absorbed by the support team, freeing capacity for the next modernization phase.

Specific scale and complexity outcomes — transaction footprint, processing-window changes, reconciliation volume changes — are subject to programme confidentiality and available on request.

Stack and approach

Pattern: Strangler-pattern modernization, phased subsystem replacement.
Languages and platforms: .NET, integration via message-based and API-led patterns.
Cloud / hosting: A mixed estate of on-premises and Azure components, modernized progressively rather than rehosted in a single move.
Integration: Replacement of file-based and direct-database integrations with explicit, contract-versioned message and API integrations.
Operational design: Observability and exception management designed as a first-class deliverable.

Engagement model

Duration: Multi-phase engagement spanning multiple delivery cycles.
Team shape: Lead architect plus senior associates engaged for specific phases. No junior pyramid.
Contracting: Time and materials with defined scope per phase, milestone reviews, and a written off-ramp at the end of each phase.
Working model: Embedded with the client's in-house engineering team and adjacent delivery partners. Public-sector change-control and procurement constraints respected throughout.