For CTOs at P&C raters and carriers

Carrier integrations in weeks. Every price proven against the filing.

Tensyl reads the carrier’s mapping document and rate manual, flags what’s unclear, builds the integration, and checks every price against the filed rules before a customer sees it.

What Tensyl isAn integration engine built for insurance formats, that proves its own output against the carrier’s documents.

  • Not a generic integration platform
  • Not a coding agent
  • Not billed by the hour

Integration report

Cascade Mutual · personal auto · rater API

Sample
  • 412 fields mapped from the carrier’s spreadsheet

    ReadEach with a confidence score

    Done
  • 3 missing fields, 2 conflicting rules

    FlagEach sent to a named owner

    Resolved
  • Request, response mapping and error handling

    BuildGenerated, not hand-written

    Done
  • Multi-policy discount skipped on 144 quotes

    VerifyFiled $2,513 · charged $2,856

    +$343
  • Fixed and re-run before launch

    No correct price flagged

Go-live gates

  • Mappedpassed
  • Verifiedpassed
  • Livepending
Sample report. The carrier and figures are illustrative.

Already in production: a public P&C rating platform pays us on outcomes.

The problem

Every carrier you add is a months-long build, and the errors stay silent.

A carrier sends a mapping spreadsheet, a rate manual and an API spec. Your engineers turn them into code by hand, test what they thought to test, and ship. Every step can pass its own checks while the price that comes out the end is wrong.

237
decision steps we mapped across 9 regulated use cases. The outcome was set by a rule, a table or a hand-off.
24.9%
over-charge on one car insurance quote when a single field is lost on the way to the insurer.
21 months
that Sompo kept charging its old rates after an approved 28.8% cut. A check against the filing catches that on day one.

Built by hand from spreadsheets

Hundreds of cryptic field codes, notes in the margins and rules that contradict each other.

Errors stay silent

A skipped discount doesn’t crash anything. It misprices every quote that passes through it.

The backlog caps your growth

A handful of new carriers a year, while partners, products and AI agents keep adding to the queue.

One quote, six steps: every step passed, the price was still wrong

PERSONShopperHas been insuredfor five years✓ entered correctlySYSTEMQuote siteCollects the formand maps fields✓ passes its testsHAND-OFFData hand-offPrior insurancesent as unknown✕ nobody tests thisRULERate tableFactors and capsset the price✓ matches its specMODELRisk modelPicks the tierfrom the inputs✓ passes its testsPERSONUnderwriterReviews flaggedquotes only✓ follows the guideOUTCOMEPrice charged $391.96 (24.9%) too high on one auto quoteEvery step passed. The decision was wrong.TENSYL RE-CHECKS THE CHAIN AND NAMES THE STEP
One auto quote, a composite from our research across 9 regulated use cases. Figures are illustrative.

How it works

Four steps, from spreadsheet to verified integration.

The engine does the work. Your people only make the calls the carrier’s documents leave open, and every step leaves a record your team can inspect.

  1. 01

    Read

    Map every field in the carrier’s mapping document, each with a confidence score.

  2. 02

    Flag

    Send missing fields and conflicting rules to a named person instead of guessing.

  3. 03

    Build

    Generate the request, response mapping and error handling from 20 years of insurance integration patterns.

  4. 04

    Verify

    Test every price against checks built from the carrier’s own documents, not from the code.

How an integration runs

  1. Send

    The carrier’s documents

    Mapping spreadsheet, rate manual, API spec and test access.

  2. Days 1–2

    Read and flag

    Every field mapped; every gap and conflict listed with an owner.

  3. One call

    Resolve

    Your team and the carrier answer the flagged questions together, instead of weeks of email.

  4. Build

    The engine writes it

    Request, response mapping and error handling, generated.

  5. Verify

    Every price checked

    Checks from the rate manual run before any customer sees a price.

  6. Go live

    Licensed to you

    Re-verified every time the engine changes.

An example · adding one auto carrier

The discount nobody would have noticed.

  1. Day 1

    The engine reads Cascade Mutual’s spreadsheet and maps 412 fields.

  2. Day 2

    It flags 3 missing fields and 2 conflicting rules, each sent to a named person.

  3. Verify

    Checks from the rate manual catch a skipped multi-policy discount on 144 quotes. Fixed and re-run.

  4. Go live

    Cascade goes live, with every price checked before a customer sees it.

$2,856

charged where the carrier’s manual requires $2,513: a $343 overcharge on each affected quote, caught before launch. The next carrier with a stacked-discount rule starts with that check already in the suite.

Illustrative example: the carrier and figures are fictional.

Proof

Paid on results today. Checked against real filings.

In production

A public P&C rating platform pays us on outcomes.

~80×
more integrations per engineer
~2
engineer-weeks per integration
5
integrations delivered, 5 more by year-end
2028
contract extended a year early

How we know it’s right

  • Every shipped integration is regenerated and byte-compared on every engine change.
  • Checks come from the carrier’s rate manual, not from the code they are checking.
  • In our prototype, those checks found 7 of 7 planted pricing errors on MGT Insurance’s filed small-business manual. A typical hand-built check found 2.
  • Your team can plant known errors to test the checks before trusting them.

Production figures from one customer, a public P&C rating platform, Feb–Oct 2026; customer name withheld under NDA. Prototype errors were planted in mock systems modeled on real enforcement cases, not found in any company’s live system.

Your options

Only one knows insurance formats and proves the price.

OptionWhat you getWhat’s missing
Your own teamFull controlMonths per carrier; a handful a year
Systems integratorExtra handsThe same hand-built process, billed by the hour
Integration platformFast for modern, clean APIsNot built for legacy insurance formats
AI coding agentCode from instructionsNo insurance know-how; no proof a price is right
Tensyl~2 engineer-weeks per carrierEvery price verified against the carrier’s rules

Security and ownership

Your data stays yours. Every integration is licensed to you for life.

Runs read-only inside your cloud

A pilot runs read-only inside your cloud. The carrier documents and test access you share stay under your control.

We never train on your data

Your systems, data and carrier documents are used only for your integrations. None of it is reused for anyone else.

A record of every step

Every mapped field, flagged question, generated change and verification run is logged, so your team can inspect how a price was produced.

Open format, no lock-in

Leave with every check and every record. Your engineers can re-run the verification suite without us.

You own and keep

  • Your systems, data and carrier documents.
  • A license to every integration built for you, for the life of the software.
  • The savings and revenue those integrations produce.

Tensyl maintains

  • The engine, its methods and the integration logic it produces.
  • The verification suite that re-checks your integrations on every engine change.
  • Improvements that make your next carrier faster than the last.

Beyond integrations

The same engine checks the prices you already charge.

Tensyl re-runs your live quotes and decisions against what you filed and approved, finds the premium lost between systems, and gives the people who sign off a record an examiner can re-run.

See independent assurance →

Built for the people who sign off

  • Chief underwriting officer
  • Pricing actuary
  • Model risk
  • Compliance

Who builds it

Operators who have shipped AI inside regulated workflows.

Shamit Patel

Shamit Patel

Co-Founder & CEO

Product head, Uber Infrastructure and Director at Twitter Growth; product leader for Bing Ads API & platform. VP Product leadership at Instawork (Series D, Benchmark-backed). Rebuilt an operating model around AI and decoupled revenue from headcount.

LinkedIn ↗
Debarshi Kar

Debarshi Kar

Co-Founder & CTO

CTO at Instawork (Series D, Benchmark-backed), from Series A through Series D. Two-time founder with multiple exits; an early pioneer in social and mobile gaming, later CTO of a multibillion-dollar global gaming business. Turned a ten-million-professional labor marketplace into a training ground for real-world robotics.

LinkedIn ↗

Start with one carrier

Pick the carrier stuck longest in your queue.

Book a technical deep dive. We’ll walk your engineers through the engine on a real mapping document and scope a first integration.

By submitting, you agree to be contacted about Tensyl. We won’t share your details. See our Privacy Policy.

Please don’t attach carrier documents here. We’ll send a secure way to share them.

  1. 01

    You bring

    One carrier’s mapping document and rate manual, test access to its quoting system, and one person to answer flagged questions.

  2. 02

    You get

    A live integration licensed to you, a verification report on every price path, and a plan for the rest of your queue.

  3. 03

    Terms

    Priced per verified integration, or outcome-based on a share of the savings. Design-partner pricing for early customers.