Platform modernization: one insurance core across 14 partner experiences
Reframed a Drupal-to-Adobe migration as a reusable platform direction with API-owned insurance rules and partner-sized experience tiers.
- My role
- Product direction, platform boundaries, migration roadmap, and business case
- Timeframe
- Multi-site modernization roadmap
- Evidence boundary
- The 14-site direction and roadmap were delivered. $1M is an annual cost-reduction target, not realized savings.
Reframing the work
The initial framing was a migration from Drupal to Adobe. I reframed it as a platform product question: where should eligibility, validation, pricing, product display, content, and partner variation live so that 14 experiences could evolve without creating 14 separate insurance engines?
The platform boundary
The front end could own presentation, content, accessibility, and partner-specific configuration. The shared insurance services remained authoritative for quote, eligibility, and issuance rules. This prevented display logic from becoming a second final insurance answer.
A tiered capability model
Costco became the Tier 1 reference for a large partner requiring stronger accessibility, analytics, monitoring, service, and support. Smaller partners could use a narrower capability package while sharing the same insurance core, requirements patterns, test approach, and launch gates.
Outcome and boundary
I delivered the 14-site modernization direction and supporting business case. The $1M annual cost-reduction figure is a target established by the roadmap, not realized savings. I do not claim that every later partner launched faster because partner scope varied.
What I would measure next
Commercial metrics show value; platform metrics show whether change is becoming easier and safer. I would baseline quote-to-policy mismatch rate, rule-change lead time, regression effort, dependency availability, and recovery time.