Vertically integrated vs a point-solution insurtech
One structure owns every step from the first lead to the reinsured policy and pays for all of them. The other builds one layer extremely well and sells it to everybody, including the integrated group. Both are coherent, and the honest answer depends on what compounding you are trying to buy.
Quick verdict
Build or buy a point solution when one layer is the whole opportunity: focus is worth more than breadth, the capital requirement is a fraction of the integrated one, and a single metric tells you whether it is working. Build vertically integrated when the advantages only compound if you hold them together, so owned demand makes selective underwriting affordable and selective underwriting lets a proprietary product be priced honestly.
Everything below about the point-solution category is described at the level of what such companies publicly document, rather than as a claim about any one product. No company is named.
Choose a point solution
One layer is your business, focus beats breadth, and you would rather have a smaller capital requirement and a clearer story.
Choose vertical integration
The advantage you want dies at a handoff, and you can afford the capital and the years it takes to own both sides of it.
Capability by capability
Structural categories rather than feature counts. Where a capability is simply not part of a category, that is what the cell says, and where we are relying on public materials the cell says that too.
| Capability | Solved VenturesVertically integratedsix operating companies | Point-solution insurtechOne layerpublicly documented category |
|---|---|---|
| Where the demand comes from | Generated in houseSolved Marketing produces Medicare, life, and final expense demand and sells each lead once. | Typically the customer's problemSoftware is sold to whoever has the demand, which keeps the category out of the acquisition business entirely. |
| Depth in one capability | Good across several, best at fewSix operating rhythms means the risk is breadth at the cost of depth. | The category's central advantageOne product, one roadmap, one metric. Genuinely hard to beat on its own layer. |
| Capital requirement | High, and slow to returnSix sets of fixed costs, plus a product company that moves at the speed of regulators. | Materially lowerThe clearest structural advantage of the category, and the reason most of it exists. |
| Control of the handoffs | Owned end to endA reference plus a scoped grant crosses each boundary rather than a copy of the record. | Not part of the modelBy definition a single layer integrates with parties it does not control on either side. |
| Feedback from placed business to acquisition | Direct and fastPlacement, decline reasons, and persistency return at the program and filter level. | Depends on the customer sharing outcomesA vendor can only learn what its customer chooses to send back. |
| Underwriting method | Comparative, across carriers and products at oncePatented method; powers the AI Plan Recommender in Solved Enroll today. | Category includes strong underwriting and quoting productsSeveral publicly documented offerings address this layer directly. |
| Explainable recommendations | Profile version and rule set version on the recordA ranking can be reconstructed and defended a year later. | Varies by product; some document it explicitly |
| Distribution | Contracted directlySolved Solutions holds appointments, hierarchy, and licensing records. | Not part of the modelSoftware is sold to distributors rather than replacing them. |
| Proprietary product and risk structuring | In development, pending state approvalSolved Insurance with Solved Re. Nothing is on sale. | Not part of the modelA software company does not carry insurance risk. |
| Speed to a first customer | Layer by layer, over yearsTwo platforms took years to reach production before the product company started. | Much fasterOne product, one buyer, no regulatory approval in the critical path. |
| External validation of the software | Sold outside the groupAgentTech Dialer and Solved Telephony have customers with no other relationship to us. | The entire businessEvery customer is external, which is the cleanest discipline available. |
| Risk of subsidizing a weak layer | Real and permanentA layer whose only customer is you can stop being competitive invisibly. | Structurally absentThere is no internal customer to hide behind. |
| Buyer's integration burden | Fewer boundaries to ownShared conventions across the surfaces, and one group to call when something spans two. | One clean integration, and the rest is yoursOften preferable if you already have the other layers working. |
| Clarity of the story | Requires a diagramA holding company thesis takes longer to explain than a product. | One sentenceEasier to sell, easier to fund, easier to benchmark. |
Comparisons describe the common shape of each category rather than any one product, and are based on publicly published materials.
Which model is right for you?
Both structures work. The question is whether the advantage you are chasing survives being split across two companies.
Choose the point-solution model when
- One layer is genuinely the opportunity, and being the best at it is a defensible position on its own
- Capital is the binding constraint, and a fraction of the requirement is worth more than control of the chain
- You want one metric that tells you whether the company is working, rather than six
- Your customers already have demand, distribution, and a product, and need a tool rather than a chain
- You have no appetite for insurance risk or for a regulatory approval timeline you cannot influence
Choose the integrated model when
- The advantage you want dies at a handoff, so partnering the step away leaks the thing you were buying
- You need the counterfactual: what every carrier would have said, not only the one you submitted to
- Persistency on placed business has to reach acquisition quickly enough to change a filter, not a quarter later
- You intend to carry risk eventually, which makes cheap and disciplined evaluation a requirement rather than a feature
- You can fund years of building and are prepared to sell each layer externally to keep it honest
What is still pre-launch on our side
A structural comparison is meaningless without this, so it appears on every comparison page rather than in a footnote.
FAQs
Integrated versus point solution: common questions
Is Solved Ventures an insurtech?
Partly, and that is the point of the comparison. Two of the six operating companies are software businesses with paying external customers, so on that layer we are directly comparable. The difference is that the software exists to make the acquisition, underwriting, and product layers work rather than being the whole business. A point-solution insurtech is a software company. We are a holding company that happens to own software companies.
Is focus not a real advantage?
It is one of the largest advantages in this comparison. A point-solution company gets to be excellent at one thing and have a single number that tells it whether that is working. We have six operating rhythms and the failure mode is six things that are each almost good enough. Anyone evaluating the integrated model should weigh that seriously rather than treating breadth as automatically better.
Why not just license the best software for each layer?
For most companies that is the right answer, and the cost of the licenses is the fair price of not having to build. It stops being right when the advantage you are chasing depends on controlling the handoffs rather than the tools. Owned demand is what makes selective underwriting affordable, and selective underwriting is what lets a proprietary product be priced honestly. A license does not give you either of those.
Do your platforms have to compete with point solutions?
Yes, and on purpose. AgentTech Dialer and Solved Telephony sell to customers with no other relationship to the group, which means they are judged by buyers who can leave. A layer that could only survive on internal revenue would be a subsidy rather than an advantage, and that is the specific failure we are trying to avoid.
Which parts of your stack are pre-launch?
AgentTech Dialer and Solved Telephony are in production. Solved Marketing and Solved Solutions are operating. Solved Enroll is in private beta with a public rollout planned for 2027. Solved Insurance and Solved Re are in development, pending state approval, and nothing is on sale.
If I am building a single insurance product, what should I take from this page?
Probably that the point-solution structure fits you. It needs less capital, it lets you be excellent at one thing, and it is far easier to explain to a customer and to an investor. The integrated case only holds when the advantages you want only compound if you control them together, and when you can afford the years that takes.
Something else? Contact us
Ask us the version of this about your company.
Describe what you are building and we will tell you which structure we think fits, including when the answer is one layer rather than six.