A Swiss digital credit solutions provider: Legacy credit lifecycle platform fully re-architected and FINMA-compliant audit passed without revision in an 8-week engagement.
Snapshot
Client
A Swiss digital credit solutions provider
Industry
Finance & Fintech / DACH
Geography
Switzerland (multiple offices)
Size
80–100 employees; 500+ institutional customers across DACH
Challenge
Legacy system re-architecture + regulatory compliance modernization
Services
System re-architecture, compliance-first development, audit readiness, agile delivery
Duration
Ongoing
Team
1 Technical Advisor, 1 PM/PO, 1 AI Engineer
Download this case study as a PDF
Shareable leave-behind · auto-generated · always up to date
Client Context
This Swiss provider of digital credit solutions has served financial institutions across the DACH region since the mid-1990s. With 80 to 100 specialists and offices across Switzerland, the company delivers modular software spanning credit origination, account management, refinancing, and electronic collateral registry. Its customer base includes banks, insurers, and pension funds, with more than 500 institutional customers. Operating under full FINMA oversight, including Circular 2018/3 on outsourcing, the company’s software underpins daily credit operations for a significant segment of Swiss retail banking. The business was recently acquired by and integrated into a larger Swiss fintech group, signalling active platform consolidation across the sector.
The Challenge
The company’s core credit lifecycle platform had been in production for over a decade. What had once been a reliable workhorse had become a liability: maintenance costs were rising, release cycles were slow, and the architecture was increasingly misaligned with modern software security and scalability expectations. In a FINMA-regulated environment, that misalignment is not merely a technical inconvenience it is a compliance risk. FINMA’s standards for outsourced banking technology are exacting. Any system modification must be auditable, traceable, and demonstrably aligned with the latest security benchmarks. Patching the existing architecture incrementally was not viable; the system required a complete redesign. Yet a full rewrite carried its own risk: disrupting continuity of service to dozens of active institutional customers. Beyond the technical problem, there was an organizational dimension. Modernization required aligning multiple internal stakeholders architecture teams, compliance officers, product owners around a shared blueprint that could survive external scrutiny. Reaching that alignment quickly, without losing momentum, was as difficult as the engineering work itself. The stakes were real. Failing to modernize meant falling behind on compliance readiness, increasing operational risk, and forfeiting the ability to scale the platform to meet the demands of a consolidating Swiss credit software market.
The Approach
Gradion engaged with a lean, senior team: one Technical Advisor, one PM/PO, and one AI Engineer. The scope was fixed at 8 weeks. The objective was not to complete the full rewrite but to define the architecture, validate it under external audit, and establish the delivery framework that would carry the client through the full transformation. Gradion worked directly alongside the client’s internal architecture team. Together, the teams identified the core KPIs for the modernized platform and developed a blueprint grounded in industry best practices and aligned with FINMA’s regulatory requirements from the first day. Rather than treating compliance as a downstream checkpoint, it was built into the architecture design itself. The resulting architecture was submitted to an independent security and compliance audit conducted by a Big Four firm. The design passed without requiring revision an outcome that validated both the technical quality of the blueprint and the rigor of the compliance-first methodology applied throughout. Delivery was structured using agile methodologies, with particular emphasis on Kanban and Flow Metrics. This gave the client’s diverse internal stakeholders clear visibility into progress, enabled precise planning, and prevented the coordination failures that typically slow large-scale transformation programs. The approach also ensured that the client’s own team fully owned the blueprint at the conclusion of the engagement a deliberate knowledge transfer rather than a hand-off.
The Results
Within 8 weeks, the client had in hand a fully re-architected system blueprint, an independently validated compliance posture, and a clear execution path for the full modernization programme. Big Four audit passed without revision the architecture met the latest security benchmarks and FINMA compliance requirements on first submission Modernization roadmap unblocked the client moved from stalled legacy maintenance to an active, sequenced delivery programme Operational efficiency improved the re-architected design addressed the maintainability and performance constraints that had accumulated over a decade Stakeholder alignment achieved agile delivery practices and Kanban-based planning created transparency across architecture, compliance, and product teams Platform positioned for scale the new architecture is designed to accommodate the product consolidation underway as part of the client’s broader group integration The engagement demonstrated that regulatory compliance and technical modernization are not opposing forces. Treated as co-requirements from the outset, they reinforce each other.
Services & Technology
Services delivered
- System re-architecture
- Compliance-first development
- Audit readiness preparation
- Agile delivery (Kanban, Flow Metrics)
- Stakeholder alignment and knowledge transfer
- Technology and methodology stack
- Kanban and Flow Metrics
- FINMA Circular 2018/3 compliance framework
- Big Four external audit process
- Modern software architecture best practices
Technology stack
- Custom technology stack
Engagement model
Fixed-scope advisory and delivery engagement
Discuss how we approached FINMA-compliant modernization, and what that means for your system.
Describe the constraint. We will scope the engagement.