Overview
Built an insurance SaaS platform from scratch over 18 months, taking it from initial concept to a production-ready product with paying US clients. The platform enables insurers to configure and launch new insurance lines through a microservices architecture with 4 core engines.
The Problem
The parent company had deep insurance domain expertise but no technology product. Insurance companies needed configurable platforms to launch new lines quickly, but existing solutions required months of custom development for each line. The challenge: build a product that could be configured (not coded) for any insurance line.
My Role
As Product Manager, I owned the full lifecycle from vision to revenue:
- Defined product vision and target insurance lines
- Hired and onboarded insurance domain Business Analysts
- Studied industry data models and table structures
- Designed microservices architecture with 4 core engines
- Wrote BPMNs and defined stakeholder workflows
- Managed parallel engine development and integration
- Led go-to-market through insurance forums and advisory listings
- Closed first 2 US clients
Stakeholders
Internal
- Engineering Team (.NET + JavaScript)
- Insurance Domain BAs
- UX/UI Designer (Figma)
- Executive Leadership
External
- US Insurance Clients
- Insurance Industry Advisors
- Forum Communities
The 18-Month Journey
Engine Architecture
Results
Key Learnings
- Domain expertise before technology: Hiring insurance BAs and studying industry data models first meant the architecture actually mapped to how insurers think and work.
- Configurability beats custom code: Designing for no-code configuration from day one made each new insurance line 80%+ faster to implement than building from scratch.
- Parallel engine development needs strong integration planning: Building 4 engines simultaneously only works when BPMN workflows and data contracts are defined upfront.