Could a new team learn the business while delivering?
The team began learning the business and system from the start and continued that work over the first two years.
← Back to Case Studies
Case study · Financial Services
Modernising a Financial SaaS Platform and Building a Dedicated Delivery Team
An Australian financial insurance company approached Shinetech to rebuild an ageing SaaS platform. The engagement began with fixed-price projects and developed into a dedicated team supporting the core product.
- Client
- Australian financial insurance company
- Markets served
- Australia, New Zealand and Canada
- Initial constraint
- Three-month deadline
- Team
- Grew from 2 to 8 people
The situation
The business need and starting point
The client’s SaaS management platform had an outdated interface and slow response times that were limiting growth. In 2018, the company approached Shinetech to rebuild and upgrade it.
The initial deadline was three months. The team also had limited knowledge of the client’s business and existing system, so learning the product and maintaining delivery quality were important parts of the engagement.
The project questions
Key Questions
How would a project engagement become ongoing capacity?
After four fixed-price projects over seven months, the client chose an Offshore Development Center model.
What needed to improve beyond the interface?
The work included performance, cloud security and ongoing core-platform development.
The solution
What the implementation covered
The programme covered interface and functionality improvements, platform upgrades and stronger cloud-server security. The source identifies AWS, ASP.NET Core, microservices and Redis within the technical context.
Security work included auditing, reinforcement and scanning.
The team became responsible for core-platform development. Its cross-functional capability included UX/UI design, .NET development and testing, with automated testing contributing to iteration quality.
How the work unfolded
From requirements to delivery and support
01 · Initial projects
Deliver within a constrained starting engagement
The collaboration began with fixed-price work and an initial three-month deadline. Four fixed-price projects were completed over seven months before the client moved to a dedicated-team model.
02 · Platform improvement
Address performance, usability and security
Upgrade the platform, improve its interface and functionality, and carry out cloud-server auditing, reinforcement and scanning. The source reports performance improvement without specifying the measurement method.
03 · Dedicated delivery
Build business knowledge and a broader team
The team grew from two engineers into a cross-functional group of eight. Continuous learning of the client’s product and business supported communication and subsequent development decisions.
Technology and delivery context
The tools and working practices used in this project
AWSASP.NET CoreMicroservicesRedisUX/UI designAutomated testing
The result
What changed for the client
From projects to a dedicated team
The client continued with an ODC engagement after the initial four fixed-price projects.
Reported performance improvement
The source reports a 30–40% improvement. It does not define the benchmark, so this is presented as a source-reported result.
Broader product responsibility
The source describes improved platform stability and an integrated team handling core-platform development.
Is an ageing SaaS platform holding back your product?
Tell us about your existing system, business workflows and delivery requirements.
Discuss Your Project