Maple Thinks Every App Should Sell Insurance, and the Math Might Work

The Macro: Embedded Finance Ate Payments, Now It’s Coming for Insurance

The embedded finance wave started with payments. Stripe made it possible for any company to accept credit cards with a few lines of code. Plaid opened up banking data. Marqeta enabled card issuing. The pattern was consistent: take a financial service that used to require specialized infrastructure, wrap it in a clean API, and let software companies distribute it inside their own products.

Insurance is the next obvious target, and it’s arguably the biggest one. The global insurance market generated over $7 trillion in premiums in 2024, according to Swiss Re and other industry estimates. The embedded insurance segment specifically is projected to reach $700 billion in gross written premiums by 2030, up from roughly $60 billion today. Those are not modest projections.

The logic for embedded insurance is straightforward. You’re already buying something, whether that’s a car, a flight, a rental, or a piece of electronics. The moment of purchase is when you’re most aware of the risk and most likely to want protection. If the insurance offer is integrated into the checkout flow rather than requiring you to go find a separate insurance provider, conversion rates go up dramatically. Some embedded insurance implementations see attachment rates of 20 to 40 percent, compared to low single digits for standalone insurance sales.

The current competitive field in embedded insurance APIs includes several well-funded players. Cover Genius has built a significant global business in travel and e-commerce protection. Boost Insurance (now Boost) has been working on the program management side. Qover in Europe is making a push. Bolttech in Asia is scaling fast. On the more established end, companies like EverQuote and Policygenius have digital distribution models, though they’re more marketplace than embedded.

What makes this market interesting is that it’s still genuinely early. Most companies that could benefit from offering insurance to their customers have not started doing so. The APIs exist, but adoption is in the first or second inning. The window for a new entrant to establish itself is still open.

The Micro: APIs for an Industry That Runs on PDFs

Maple is building an embedded insurance platform designed to let any company offer insurance products through API integrations. The pitch is the standard infrastructure-layer promise: you don’t need to become a licensed insurance company, you don’t need to build underwriting models, you don’t need to deal with state-by-state regulatory compliance. Maple handles the insurance plumbing, and you just integrate the API into your existing product.

The company is based in San Francisco, which puts it in the center of the fintech infrastructure cluster where most of the embedded finance tooling has been built. The proximity to companies like Stripe, Plaid, and the broader API-first financial infrastructure community is a practical advantage for recruiting and partnerships.

The core technical challenge in embedded insurance is harder than it looks. Insurance is regulated state by state in the US, with different requirements for licensing, product approval, rate filing, and claims handling in each jurisdiction. Any API platform that wants to offer “insurance everywhere” needs to either hold licenses in every state or partner with carriers and MGAs who do. The regulatory surface area is enormous.

The product categories that work best for embedded insurance are ones with a clear, bounded risk profile. Travel insurance at flight booking. Device protection at electronics purchase. Renters insurance in a property management app. Pet insurance at a vet clinic checkout. The further you get from these clean use cases, the more complex the underwriting and the harder the integration becomes.

What Maple needs to prove is not that embedded insurance is a good idea. That’s already established. The question is whether their specific implementation is meaningfully better than what Cover Genius or Boost already offers. In API-layer businesses, the differentiation usually comes from three things: ease of integration (how many lines of code to go live), product breadth (how many types of insurance can you offer), and economics (what cut does the platform take, and how competitive are the premiums).

The “modern” framing in the tagline is doing real work. It implies that existing embedded insurance solutions are outdated or difficult to work with, which is partially true. Many existing platforms were built before the current generation of API design standards, and their integrations reflect that. If Maple can deliver a genuinely Stripe-like developer experience for insurance, that alone could be enough to win market share from incumbents.

The Verdict

Embedded insurance is a real and growing market. The economics work. The timing is right. The open question for Maple is competitive positioning: how do you differentiate against funded competitors who already have carrier relationships, regulatory infrastructure, and live integrations?

At 30 days, I’d want to see the developer documentation and the actual integration experience. In API businesses, the product is the documentation as much as the code. If a developer can get a working insurance offer into their app in an afternoon, that’s compelling. If it takes weeks of back-and-forth, the “modern” claim falls apart.

At 60 days, carrier partnerships matter. Who is underwriting the insurance products that flow through Maple’s APIs? The quality and breadth of the carrier network determines what products can actually be offered and at what price points.

At 90 days, the first live integrations tell the real story. What are the attachment rates? How does claims handling work? What does the customer experience look like when someone actually needs to use the insurance they bought? These are the moments where embedded insurance either builds trust or destroys it.

The API-first approach to insurance distribution is clearly where the industry is heading. Maple is betting they can build a better on-ramp than what exists today. If the developer experience is genuinely clean and the carrier network is robust, they have a real shot at capturing a meaningful piece of this market. If either of those pieces falls short, they’re another insurance API in a field that’s getting more crowded by the quarter.

I’d keep this one on the radar. The market is too large and too early for the winner to already be decided.