logo
hamburger-menu-icon
Back to Projects

Insurance Focused Startup Platform

Securing and stabilizing a multi portal insurance platform

An insurance startup under private equity ownership had to be sold within a month after its owner hit unrelated financial trouble, and its dev team wasn't transferring with the sale. Ollon took over the unlaunched platform, stabilized it, secured all three portals, and automated its manual document workflows. The platform launched under new ownership, with Ollon continuing as its development team since.

An insurance focused startup platform was being built under a private equity group's ownership, running three interconnected portals for clients, agents, and employees, with most of its document workflows still handled manually. When the private equity group ran into financial problems unrelated to the platform itself, it needed to divest the platform quickly to help resolve those issues, giving less than a month to complete the handover. The development team working on the platform was part of the private equity group, not the platform itself, so they did not transfer with the sale, and the product had not yet launched publicly. The platform was acquired at a bargain price by a larger insurance company taking it on as its new distribution arm.

Ollon stepped into that short handover window, meeting briefly with the outgoing development team to transfer what knowledge could be captured before they left. Ollon then took over the existing platform, which had not yet launched, working out how the React and Java based system was built and stabilizing it, reorganizing the frontend dependency structure, removing outdated packages, and updating dependencies to current versions. An authorization layer was implemented across all three portals to secure access, and automated document processing was added to replace the manual routing workflows. Ollon brought the platform to launch, including a rebranding to reflect the new ownership.

The platform launched successfully under its new ownership and brand, with Ollon continuing as its development team since. The platform now handles a substantial portion of its policy document workflows automatically, and it is more secure and stable than before. Since the acquisition, Ollon has also worked through revisions required by the new ownership, including reworking the platform's architecture from a design built for multiple clients into one built specifically around the new owner's workflow.

Our Expertise in Action

Application Triage and Rescue

An insurance focused startup was acquired at a bargain price after its private equity owner ran into unrelated financial problems and needed to divest quickly, leaving under a month to complete the handover. The outgoing development team belonged to the private equity group rather than the startup itself, so they did not transfer with the sale, and the product had not yet launched publicly. Ollon met briefly with that outgoing team to capture what knowledge could be transferred, then took over the platform, working out how the React and Java based system was built and reorganizing its dependency structure to stabilize it. That work brought a platform inherited mid build to a successful public launch.

Corporate Rebranding Technology Transition

When an insurance focused startup was acquired by a larger insurance company, its platform needed to launch under the new owner's brand instead of its original identity, and its architecture had been built to serve multiple clients rather than one specific owner. Ollon handled the technical rebrand as part of bringing the platform to launch, then worked through revisions since to rework the platform's architecture from its original multi client design into one built specifically around the new owner's workflow. The platform now reflects its new ownership both in brand and in how it is architected to work.

Java Development

After an insurance startup's platform changed ownership, Ollon inherited a Java backend paired with a React frontend, with no one left who understood how it was built. Working directly in that codebase, the incoming team traced its structure and stabilized it, reorganizing dependencies and removing outdated packages so the backend could reliably support new features. That Java system now runs the platform in production, handling policy document workflows and access control across all three of its portals, with maintenance and extension continuing as the platform's needs evolve.