RocketMGA and RocketFlood

# the-problem

RocketFlood is a family of flood and property insurance products: a consumer quote engine, an agent portal, and RocketMGA, a multi-tenant MGA and agency platform. Agents use these products to compare options across carrier programs, so a slow quote is a direct business problem.

The core quote path took 8–10 seconds. Each quote depended on several property-data and carrier calls, made one after another, so every slow dependency added to the wait.

# my-role

I've been the primary contributor to RocketMGA and the RocketFlood agent portal since 2020, as part of the NBTHub team. My work runs across architecture, implementation, carrier integrations, performance, and release practices. I've kept delivering on these products as they moved through several generations of frameworks and infrastructure.

# cutting-quote-time

I started by instrumenting the flow to see where the time actually went. Most of it came from repeated work and from calls that had no reason to wait for each other.

The changes were straightforward once that was clear:

• Redis caching for repeatable property and address data.
• Parallel calls to carriers that didn't depend on each other.
• Request batching to reduce unnecessary round trips.
• Timeouts and fallbacks, so one slow provider couldn't block the others.
• Asynchronous delivery, so partial results reached the screen as they arrived.

The core path went from 8–10 seconds to under 1 second.

# keeping-many-carriers-manageable

Carriers expose different APIs, fields, timing, and errors. A canonical application model keeps the product consistent, with each carrier handled behind its own adapter. Statuses, results, and errors are normalized before the rest of the product sees them, and integration calls are recorded for audit.

# long-term-ownership

Long-lived insurance software has to keep working while it changes. These products evolved across Laravel, Vue, Nuxt, authentication, and infrastructure generations while features kept shipping. That meant modularizing integrations, improving caching and queues, and updating frontend foundations in steps, with code review alongside.

I've also led security hardening and audit remediation.