Bertie is the company I co-founded to fix how insurance businesses build, run and scale their operations.

Insurance businesses are doing genuinely important work through a patchwork of tools that were never designed to talk to each other.

Quoting, documentation, reporting, reconciliation — they all live in different systems with manual bridges between them. Anyone inside the industry knows what that looks like: re-keying, inconsistency, delay, and hours spent moving information from one place to another.

This goes beyond efficiency. It's a product problem. The shape of the underlying system determines how quickly a business can respond, how confidently it can scale and how much complexity it can actually handle.

Bertie is built around a simple idea: the important workflows should feel like part of one system, not a relay race between disconnected ones.

In practice that means better foundations for structuring and rating risk, moving from quote to bind with less friction, generating documentation as part of the workflow rather than as an afterthought, and keeping reporting clean enough that you can actually trust it.

It also means reducing the manual handling around core insurance activity, and building systems that stay usable even when the real workflow is messy, distributed or time-sensitive — which it usually is.

We're not automating for the sake of it. The goal is clarity, control and speed in the places where they actually count.

One of the reasons insurance is so interesting as a software category is that it sits where judgement, operations and software all meet.

You can't solve it with surface-level UX alone. You need to understand how the workflow actually works, where information changes form, where risk gets introduced and where trust is won or lost.

Building here requires a real respect for operational detail. But it also means you can build products that become deeply embedded in how businesses actually function — and that's a very good place to be.