A Letter from Our Founder
When people ask me why I decided to build Force, I usually give a simple answer:
“Insurance quietly holds together an enormous part of modern life, and the systems that run it are decades behind what they should be.”
Insurance is not a glamorous industry. It does not attract headlines the way consumer technology does. But it sits underneath almost everything that allows society to function, including homes, businesses, hospitals, logistics networks, cities, infrastructure, and families planning their future. When insurance works well, people rarely notice. When it fails, the consequences are deeply personal.
For a long time, I felt there was a disconnect between how important insurance is and how outdated the software powering it has become. That disconnect is what led to Force.
My background spans finance, real estate, and enterprise software. I’ve spent over a decade working around complex systems, capital structures, and operations. From 2017 to 2022, I served on the board of a property and casualty insurance company. I had a front-row seat to how carriers actually operate day to day.
I remember sitting in a board meeting reviewing quarterly results when a simple operational question came up: “Why did loss development move this way in this segment? What followed was not an analysis. It was archaeology. Data pulled from multiple systems. Spreadsheets reconciled manually. Teams emailing CSV exports back and forth. It took weeks to answer a question that should have taken minutes. That was the moment I realized the constraint was not talent. It was infrastructure.
Not the pitch-deck version. Not the vendor demo version. The real version.
What I saw was not a lack of smart people. It was not a lack of care. It was not a lack of ambition. It was a lack of good tools.
Teams were forced to operate across a patchwork of legacy systems. Underwriting lived in one place. Claims in another. Billing in another. Reporting in another. Customer service in another. Data rarely lined up cleanly. Simple changes took months. Meaningful automation was nearly impossible.
The people inside these organizations were spending enormous amounts of time working around software instead of with it. That experience changed my view of what “modernization” should actually mean.
Most enterprise software has been built as layers on top of older layers. New tools bolted onto old foundations.
Modernization efforts have often meant moving the same fragmented systems to the cloud, or stitching together more vendors with better interfaces. That improves usability, but it does not solve fragmentation.
Force starts from a different premise: a single system of record, a single workflow engine, and a single source of truth across the organization.
More vendors. More middleware. More integrations. More fragility.
Very little of it was designed from the ground up for the world we now live in.
Force is built on a unified data model and workflow engine designed specifically for insurance. AI agents operate within clearly defined decision boundaries, with full audit trails, explainability layers, and human override controls. Every automated action is logged, traceable, and configurable to carrier-specific underwriting guidelines and regulatory requirements.
This is not AI layered on top of legacy systems. It is AI embedded into the core architecture.
For decades, the idea of running an entire enterprise on one unified system was mostly theoretical. Limitations in infrastructure, databases, compute, and software architecture made it unrealistic.
Recent advances in cloud infrastructure, distributed systems, and AI model frameworks make something new possible:
A single, connected platform that can run an entire organization. A system that is not just a database of record, but an active participant in the work itself.
This shift is bigger than any one product category. It is a transition from software that stores information to software that helps execute work.
That is the foundation Force is built on.
Force is the operating system for modern insurance carriers.
It is a connected, AI-native platform that brings underwriting, claims, billing, policy management, reporting, and customer service into one system.
Not as loosely stitched modules. Not as a collection of third-party add-ons. But as one coherent platform designed to work together.
Force does two core things:
- It unifies the systems carriers rely on into a single connected platform.
- It embeds automation and AI directly into everyday workflows.
The result is simpler operations, clearer data, faster execution, and less manual work across the organization. We think about Force less as “software you log into” and more as infrastructure your business runs on.
A lot of AI tools look impressive in isolation. Very few of them actually do useful work inside real organizations.
Every carrier has its own rules, manuals, appetite, processes, edge cases, and regulatory environment. AI only becomes valuable when it is deeply connected to those realities.
Force takes a different approach.
We design, build, and implement custom automations and AI agents around the actual work each carrier does. You show us the workflow you want to automate. We build it. We test it. We integrate it. We make sure it works. Then we hand it over with full visibility and control.
This is what we mean by white-glove automation.
- It is not about selling generic tools.
- It is about delivering working systems.
Force is not built to replace people. It is built to remove the work that keeps good people from doing their best work.
Underwriters should spend time making difficult judgment calls, not copying data between screens. Claims professionals should focus on complex cases, not chasing documents. Service teams should solve real problems, not answer the same simple questions all day.
When routine work is automated, people get to operate at a higher level. They become more productive, more engaged, and more valuable. That is better for employees. Better for carriers. Better for policyholders.
We believe the future insurance carrier is a focused team of highly capable professionals supported by systems that handle routine intake, document processing, data reconciliation, and reporting automatically.
Underwriters will operate with real-time portfolio visibility.
Claims teams will resolve straightforward cases autonomously and escalate only when judgment is required.
Leadership will see operational and risk data instantly, not weeks later.
The organization becomes faster, leaner, and more resilient.
- Insurance pricing, availability, and reliability ultimately affect the cost of living for everyone.
- Inefficient operations drive higher expenses.
- Higher expenses become higher premiums.
Operational inefficiency directly impacts expense ratios.
Slower underwriting delays revenue recognition.
Fragmented data increases loss volatility
Over time, those factors compound into higher combined ratios and higher premiums.
Better infrastructure does not just improve workflows. It improves financial performance. - Higher premiums make coverage less accessible.
- Better infrastructure lowers costs. Lower costs make insurance more affordable, more stable, and more widely available.
- Improving insurance software is not just a technical problem. It is a societal one. That belief shapes how we build.
If you are an insurance carrier wrestling with legacy systems, you are not behind, and you are not alone.
You are operating inside constraints created by decades of technical limitations. Those constraints no longer have to exist.
We built Force for teams who want a better foundation.
The constraints are optional now.
If you are ready to build on a better foundation, we are ready to help.