A steady development team alongside a financial services provider's own team
A financial services provider with its own platform and its own development team works with us for maintenance, support and building along on the roadmap.
- Sector
- Financial services
- Solution
- Maintenance, support and development
- Built on
- .NET, Azure
- Collaboration
- Ongoing, alongside the in-house team
A platform that has to keep growing, with a team that is full
This financial services provider has its own platform, running at customers with high demands on availability, security and diligence. The in-house development team knows the platform inside out.
The combination of maintenance, incidents, customer questions and a full roadmap asked for more capacity than there was. Every new customer meant set-up work, every outage pulled developers away from what they were building.
The customer was looking for a partner who could support the maintenance and at the same time build new features, at the same level and in the same way of working as the in-house team. Not a supplier at arm's length, a partner who thinks along and works along.
A second team that knows the code and thinks along about what comes next.
Maintenance, support and building the roadmap
The collaboration is set up broadly: from monitoring and incidents to new features and customer implementations. We work in the same codebase, with the same agreements on quality and releases as the in-house team.
Maintenance and monitoring
Monitoring of availability and errors, security updates and keeping the cloud environment up to date. We see an outage before the customer calls.
Support for team and customers
Second-line support for incidents and questions, with agreed response times and reporting.
Building the roadmap together
New features and integrations are planned and built together with the in-house team. We take on whole parts of the roadmap.
Customer implementations
For new customers of the provider we help build the set-up and the integrations, so the in-house team can focus on the platform.
The same way of working
Code review, acceptance environment and releases in consultation. What we deliver cannot be told apart from what the in-house team makes.
Capacity that moves along
Maintenance covered, roadmap moving
The in-house team no longer has to choose between fixing outages and building new features. Both happen, in a steady rhythm.
One team, two companies
Working in the same codebase and the same way, there is no handover between 'their' work and 'ours'.
Capacity to measure
Busy periods, such as several customer implementations at once, we absorb without the customer having to recruit.
A collaboration that continues
The collaboration is not tied to a project. Maintenance, support and roadmap work continue in a steady monthly rhythm, with periodic consultation on priorities and capacity.
A process outgrowing its spreadsheets too?
Tell us where it hurts, and we will tell you how we would approach it.
Book an intro callCurious what this means for your business?
A first conversation. You tell us where it hurts, we tell you how we would approach it.