Walnut Insurance

Overview

A post-Seed insurtech with product-market signal and an engineering practice that had not caught up to it. We took product leadership, professionalised how the team shipped, and built the digital-broker foundation the next raise depended on.

The problem

The company could sell faster than it could build. Each new distribution partner was integrated bespoke, which meant partner count and engineering cost grew together — precisely the curve a Series A story cannot have. Delivery was reactive, estimates were unreliable, and the platform's shape was set by whichever integration came last.

What we built

B2B2C API platform

One integration surface partners build against, so onboarding a distributor stopped being a bespoke engineering project.

Carrier and broker rails

The connective layer between carriers, brokers, and end customers, with each tier's obligations modelled explicitly.

Underwriting and claims workflows

Digital broker workflows built to carry real policy volume rather than to demonstrate the concept.

Engineering cadence

Planning, review, and release practice put in place so the roadmap became a forecast rather than an aspiration.

How we approached it

• Integrate once, onboard many — partner count must not drive engineering cost
• Model each tier's obligations explicitly; insurance is where ambiguity becomes liability
• Professionalise delivery before scaling headcount
• Build the platform the funding story describes, not a demo of it

Outcome

A scalable digital-broker foundation and a delivery practice to match it, positioning the company for Series A on the strength of the platform rather than the pitch.