The most revealing thing about One Inc is the number of people who may need to touch one payment. A wrecked car can produce a claimant, an adjuster, a repair shop and a lienholder. A damaged house can add a mortgage bank, whose approval may hold up the money for weeks. The insurer must know who gets what, prevent fraud, satisfy card and state rules, update its claims ledger and explain the whole thing to a customer having a spectacularly bad Tuesday.
Stripe made online checkout feel universal. Insurance is the rebuttal in the footnotes. It has premiums coming in, claims going out, refunds, commissions, subrogation and multi-party settlements. One Inc built its business in those footnotes. The private company, founded in Folsom, California, says it now serves more than 320 insurance carriers, connects 1.3 million vendors and providers, and handles more than $140 billion in annual payment volume.
The first draftThe feature that ate the suite
One Inc did not begin as a pure payments company. In 2012, co-founders Christopher Ewing and Tim Tyannikov set out to build cloud software for policy and agency management. The early catalog was almost comic in its completeness: PolicyOne, ProcessOne, PortalOne, ContactOne, AppOne, SalesOne and DataOne. It was an operating system pitch for smaller property and casualty insurers.
The useful discovery came from non-standard auto insurance, a corner of the market serving drivers with limited credit or difficult records. Payments there were frequent, sensitive and full of exceptions. Generic processors could move the dollars, but they did not understand cancellation notices, policy records, convenience fees, reconciliation or why a card token had to survive a change in systems.
By 2018-19, management had changed its mind. The company moved payments-first, concentrating on money coming in through premium collections and money going out through claims. This was not a cinematic failure followed by a whiteboard epiphany. It was the more common enterprise lesson: the broad platform contained one module with a clearer buyer, a more urgent job and usage that could compound.
“Insurance payments have always been a network problem approached as a platform problem.”Ian Drysdale, chief executive
The old suite did not instantly disappear. PolicyOne continued serving customers and was acquired by Aspire in 2026. The telling detail is that Aspire kept using One Inc’s PremiumPay and ClaimsPay. Core administration moved in-house; the payment network stayed outside. That is the pivot rendered as a customer architecture diagram.
The productTwo directions, one ledger
PremiumPay handles the inbound side. An insurer can accept cards or ACH through a hosted portal, an embedded payment modal, a call center, IVR, text or a mobile app. One Inc tokenizes sensitive data so less of it sits inside the carrier’s environment, then returns transaction information to the insurer’s billing and policy systems. The important work happens after the cheerful “approved” message: matching money to policies, reconciling batches and preserving the record an auditor expects.
ClaimsPay handles the outbound side. A carrier can send money to a policyholder, claimant, body shop, contractor, mortgage company or lienholder. Recipients choose among supported methods, while the software manages notifications and the strange choreography of single- and multi-party payments. One Inc strengthened this side in 2020 by acquiring Invenger Technologies and its InsurPay disbursement product. The deal’s price was not disclosed. The operational logic was obvious: combine premium collection and claim disbursement in one insurance-specific layer.
A claim payment, simplified
The mortgagee example shows why the vertical detail matters. When a home with a mortgage is badly damaged, the lender may need to approve release of claim funds. Chief executive Ian Drysdale has said the conventional process can take four to eight weeks; One Inc designed a workflow that can reduce it to as little as a day. A universal processor sees a payout. An insurance network sees the necessary signatures, the parties, the system updates and the clock ticking on temporary housing.
The moatIntegration is distribution wearing work clothes
One Inc’s competitive pitch has three layers. First is specialization: insurance payment rules and workflows are the product, not customization after the sale. Second is integration. The company reports more than 55 system integrations and works with core providers including Guidewire, Sapiens, OneShield, Majesco and Origami Risk. A carrier can keep the system of record it already depends on and add a payment layer beside it.
Third is the network. A processor completes a transaction. A network remembers the participants. If a repair shop, mortgagee or service provider has enrolled and stated how it wants to receive funds, that connection can make a later payment from another carrier easier. More participating insurers attract more payees; more enrolled payees improve the carrier proposition. It is not an impenetrable moat - banks, core vendors, horizontal processors and insurance specialists all compete - but it is more durable than a branded payment page.
Horizontal processor
- Optimizes the transaction
- Serves many industries
- Carrier builds exceptions
- Connections often restart
Insurance network
- Optimizes the workflow
- Models claims and premiums
- Connects core records
- Reuses payee preferences
This is enterprise software sold as reduced friction. Carriers buy platform access, implementation and payment processing; revenue rises with transaction activity. One Inc does not publish a menu of prices, which is normal for a negotiated product touching core systems and regulated money movement. The buyer’s calculation includes fewer checks, less manual reconciliation, a smaller PCI compliance surface, faster claim cycles and fewer policyholders abandoning a payment.
The customer list includes Amica, MAPFRE, SageSure, Tower Hill and Wawanesa, alongside regional and specialty carriers. Case studies describe Buckeye automating daily cash reconciliation, The General reducing claim-payment cost and cycle time, and Carnegie replacing separate card and eCheck vendors with a mobile-friendly, embedded flow. These are vendor-reported outcomes rather than controlled experiments, but they reveal what buyers actually purchase: fewer handoffs and fewer reasons for finance, claims and customer service to argue over the same transaction.
The capitalPrivate equity buys the narrow story
Great Hill Partners recapitalized One Inc in February 2020, just as the payments focus hardened. Months later came Invenger. Nordic Capital joined Great Hill as an equal investor in 2024, with management retaining a meaningful stake. Terms were not made public. At that announcement, One Inc had roughly 240 customers, 700,000 vendors and $70 billion in annual payments. Great Hill said processed volume had grown thirteenfold during its ownership.
The company has continued to widen the edges without reopening the old “everything suite” ambition. Partnerships with J.P. Morgan Payments and U.S. Bank add banking reach. Equisoft helps carry PremiumPay into life insurance. Copart and Verisk bring specialized participants and data. In 2025, One Inc said it signed 112 agreements and 11 strategic partnerships. It also launched an MCP server so carriers could connect payment workflows and data to corporate AI environments, initially for integration code, testing and natural-language analysis.
That expansion can work as long as each new feature reinforces the payments network. It breaks when adjacency becomes distraction. The company’s own history supplies the warning: owning the core system is a different business from integrating with many core systems. The latter makes One Inc a partner to Guidewire and Sapiens; the former makes it their competitor.
What a founder can steal
- Audit the broad product for the workflow customers use most urgently.
- Choose a vertical where exceptions repeat across many buyers.
- Integrate with systems of record instead of demanding replacement.
- Save preferences or connections that improve the next transaction.
- Add adjacencies only when they make the core network more useful.
The limitsWhen the playbook stops working
Vertical depth is expensive. It requires engineers who understand old carrier systems, payment operations that can satisfy banks and card networks, compliance teams, implementation staff and support for the moment a claimant cannot access funds. One Inc says it now has more than 1,180 employees. This is not a tiny SaaS team adding an industry dropdown.
The model is less compelling when payments are simple, volumes are small or existing core modules already do the job. It also depends on carriers trusting an outside company with a critical customer touchpoint. Network effects weaken if payee identities and preferences cannot be reused safely, or if every carrier insists on a bespoke flow. And faster digital money does not fix a slow claim decision; One Inc can accelerate the payment after approval, not make the insurer approve it.
Still, the company occupies a useful place in the market. It is narrower than an insurance core platform and deeper than a generic gateway. The product is the connective tissue between them. That position lets One Inc sell to insurers without asking them to modernize everything at once - a merciful proposition in an industry where “legacy” can mean software that still works, employees who know its quirks and a replacement project nobody wants to sponsor.
One Inc’s best idea was not invented in a new market. It emerged by watching which part of an ambitious old product kept causing pain. The company followed the payment, learned every awkward exception around it, and eventually found that the checkout lane could become the road system.