ITC Vegas 2026 field guide

Embedded Insurance at ITC Vegas 2026: Who to Talk To and What to Ask

ITC Vegas puts infrastructure providers, program administrators, MGAs, carriers, data companies, and licensing specialists in the same building. That is useful only if you arrive with a clear decision to make.

By Ty Clark · Updated for ITC Vegas 2026

Embedded insurance teams often arrive at a large conference with a meeting list but no decision framework. They see polished platform demonstrations, hear similar claims from ten vendors, and leave with more information but less clarity. The better approach is to define the operating question first. Are you choosing a provider, deciding who should hold the insurance relationship, entering the United States, or trying to fix an existing program that is not producing the expected economics?

ITC matters because the people needed to answer those questions are available in one place. You can compare technology with technology, but you can also test whether the carrier, licensing, servicing, claims, and data arrangements behind the technology will work. A vendor can have an excellent interface and still be the wrong fit because its paper does not cover your target states, its commercial model does not fit your customer journey, or its implementation assumes resources your team does not have.

The vendor categories you will meet

Infrastructure and orchestration platforms

These companies provide APIs, policy administration capabilities, quoting flows, payment connections, reporting, or a combination of those functions. The central question is not how quickly a demo can be configured. Ask which parts of the stack the vendor owns, which parts are licensed from another provider, and which operational responsibilities remain with your team. Confirm how product changes move from request to approval and production.

Program administrators and MGAs

A program administrator or MGA may bring underwriting authority, carrier relationships, product expertise, and operating staff. Some also bring technology. Ask where authority begins and ends, who controls underwriting changes, and what happens when results miss plan. If your business depends on a specific customer journey, confirm that the program administrator can support it without creating manual work behind the scenes.

Carriers and capacity providers

The carrier relationship defines more than the name on the policy. It can determine available states, product filing timelines, underwriting constraints, data requirements, and the durability of the program. Ask whether the carrier has supported a comparable distribution model and who owns the relationship if an intermediary is bringing the paper.

Data, pricing, and rating providers

Data can reduce questions, improve risk selection, and make an embedded flow feel native. It can also add cost and operational dependencies. Ask what data is sourced at quote time, what permissions support its use, how often the source fails, and what the fallback journey looks like. A useful data source must improve a decision enough to justify its cost and complexity.

Licensing and compliance specialists

For non-US entrants, licensing is not an administrative task to leave until the end. Your legal entity, resident state, designated responsible licensed producer, product structure, and carrier arrangement affect the path. A specialist should be able to explain the sequence, dependencies, realistic timing, and what your team must own after launch.

Ten questions to ask any embedded insurance provider

1. Who holds the paper? Get the carrier name, target states, authority structure, and the conditions that could cause capacity to change.
2. Who owns the customer data? Clarify permitted use, portability, retention, security obligations, and access if the relationship ends.
3. Who is the licensed seller? Do not accept a general answer about compliance. Map each step in the journey to the entity and license supporting it.
4. What happens to policyholders if you shut down? Ask how servicing, renewals, claims, notices, and data transfer continue if the vendor exits.
5. What does implementation require from us? Get named roles, technical work, content approvals, legal reviews, and expected weekly effort from your team.
6. How are product changes governed? Understand who can change rates, rules, forms, questions, eligibility, and the customer experience.
7. How are claims handled? Confirm the claims administrator, intake journey, service levels, escalation path, and data you receive.
8. How do the economics work at scale? Model fees, commissions, minimums, data costs, chargebacks, premium taxes, and support costs at several volumes.
9. What proof can you show? Ask for a comparable live program and speak with the operator, not only the executive sponsor.
10. What breaks most often? Strong operators can name failure points and explain how they are managed. Vague answers are useful information.

Eight points that stall non-US insurtechs entering the US

The United States is not one insurance market. State rules, entity choices, license types, and carrier appointments create a sequence that must match the commercial model. Teams lose time when they start several workstreams without resolving their dependencies.

1. Entity type. The entity must fit the activity it will perform, the ownership structure, and the states where it will operate.
2. State selection. Filing everywhere can waste time. Start with the states that matter commercially and make sense for the licensing path.
3. DRLP. The designated responsible licensed producer must hold the right authority and accept a real compliance responsibility.
4. Resident and non-resident licenses. The resident license usually comes first. Non-resident applications follow, with state-specific requirements.
5. Carrier appointments. A producer license does not automatically provide authority to sell for a carrier. Appointment timing must match launch planning.
6. Surplus lines. Programs using surplus lines capacity need a clear view of broker roles, diligent search rules, taxes, and filings.
7. E&O and bonding. Coverage and bond requirements can become application blockers if they are addressed late.
8. Timeline. Licensing, product, carrier, compliance, banking, tax, and technical work must be planned as one launch path.

A productive ITC meeting should help you remove one of these uncertainties. If a provider cannot explain how its model changes your licensing or carrier path, the discussion is not complete. Bring a simple summary of your product, customer journey, target states, expected premium, and which party you expect to own the insurance relationship.

Directory providers to check against the ITC exhibitor list

The companies below come from the Embedded Insurance Directory. Exhibitor status is intentionally marked as awaiting confirmation. The final ITC shortlist will be updated after the exhibitor list is confirmed.

Leave ITC with a decision, not a collection of demos

Choose the question you need to answer before building your calendar. Then schedule a small set of meetings that test different operating models. Use the same questions with each provider and write down the answers in a comparable format. Pay attention to who can explain the hard parts clearly, including licensing, paper, claims, customer ownership, and failure scenarios.

If you are entering the US, map the licensing and carrier sequence before promising a launch date. If you are building an embedded program, decide what your team should own before selecting the platform that will support it. Those two steps will remove many attractive but unsuitable options.