No Bandwidth for New Development
The internal PowerBuilder team of three was fully consumed by support tickets and minor enhancements, with no capacity for a multi-week integration project.
Case Study · Development & Enhancements
A New Partner Integration, Sprint by Sprint
A mid-market insurance carrier needed a new claims-partner REST integration fast. An OptiSol ODC squad delivered it in Agile sprints without disrupting the core application.
8 Weeks
From kickoff to production
5 Days
ODC team operational
4 Sprints
To full integration delivery
The Challenge
A Business Deadline the Internal Team Couldn't Meet Alone
A new claims-processing partnership came with a fixed go-live date — and the carrier's small internal PB team was already fully allocated to production support.
A Contractual Go-Live Date
The claims partnership agreement specified a hard launch date, leaving no room for the ramp-up delay typical of a traditional hiring or contracting process.
No Existing REST Layer
The PowerBuilder application had never exposed or consumed REST services — this would be the first API integration built into the application.
The Approach
An ODC Squad, Operational Within Days
Rather than hire or wait, the carrier stood up a dedicated OptiSol Offshore Development Centre team that operated as an extension of its own — running the same sprint cadence from week one.
ODC Team Stand-Up
A dedicated squad of PowerBuilder and integration specialists was assembled and made operational within days, joining the client's existing sprint ceremonies.
2 Integration Design Sprint
The claims partner's API contract was mapped against existing PowerBuilder data structures, and the integration architecture was agreed with the internal team before coding began.
REST Client Development
A REST client layer was built into the PowerBuilder application, with OAuth token-based authentication and structured error handling for partner API failures.
Sprint-Based Delivery & Testing
Functionality shipped incrementally across four two-week sprints, with regression testing after every sprint to protect existing claims workflows.
Controlled Go-Live
The integration launched on schedule, with the ODC team remaining engaged through hypercare to handle early production issues.
A Contractual Deadline Met Without a New Hire
An ODC squad operational within days let the carrier hit a fixed partner go-live date without the weeks of ramp-up typical of hiring or contracting.
Zero Disruption to Production Support
The internal three-person PB team stayed fully focused on support throughout the 8-week build, instead of being pulled off critical duties to chase a deadline.
A Reusable Pattern for Future Partnerships
The first REST integration built into the application became a template — future partner onboarding starts from a proven pattern instead of a blank page.
The Impact
The Business Impact
- Claims-partner integration launched on the contractual go-live date
- Internal PB team stayed fully focused on production support throughout
- First REST integration pattern built — reusable for future partner onboarding
- OAuth-secured API layer replaced what would have been a manual data exchange process
- Zero regressions introduced to existing claims workflows during delivery
- ODC engagement model kept as an on-demand option for future sprint work
"They plugged into our sprints like they'd always been part of the team — and we hit a deadline we genuinely didn't think we'd make." — OptiSol Development & Enhancements Lead
