Trusted by teams turning documents into production data
Insurance
Insurance quotes outline coverage offered, at what price, and under what terms. Formats vary by carrier, line of business, and distribution channel. Sensible turns quote documents into structured JSON for comparative rating, quote-to-bind workflows, and proposal management.
Validated JSON
Schema-enforced output; every field matches your contract
Source coordinates
Every value links back to page + bounding box for audit
Per-document pricing
Predictable cost. No token-volatility surprises
Trusted by teams turning documents into production data
Quotes follow no standard format, mixing narrative with multi-line coverage tables. We read both, tell proposals from system output, and return coverage detail as one consistent schema.
01
Every carrier and broker formats quotes their own way: table-heavy system outputs, narrative proposals, or PDF exports from rating engines. LLM parsing handles the variation; SenseML rules guarantee your output schema stays consistent.
02
Commercial package quotes list coverages across multiple lines, each with sub-limits, SIRs, deductibles, and endorsements. The extraction config captures the full hierarchical structure with line-level premiums.
03
Broker proposals bury premium data in narrative paragraphs. Carrier system outputs present it in tables. Sensible processes both formats and normalizes them into the same JSON structure for downstream comparison.
Managed services
Solutions engineers handle plan, build, deploy, and adjust on your behalf. You see clean JSON in your API response. Same engine as self-serve, just with the configuration work outsourced.
What's included
01Plan.Engineers review your samples and pick the right method
02Build.SenseML configs written from your samples
03Deploy.Same engine as self-serve, ready for production
04Adjust.We update configs when formats shift or new edge cases appear
05Integrate.Help with custom integration into your downstream systems
We configure every insurance quote extraction to your exact schema, not a fixed field list. The fields below are the ones insurance teams pull most often — tell us what your comparative-rating system needs and we map the rest.
01
Quote summary
Named insured, effective/expiration dates, quoting carrier, producer, quote number, total premium, payment plan options
02
Coverage lines
Coverage type, limit, deductible, premium, included endorsements, optional coverages, exclusions
03
Conditions and terms
Binding requirements, subjectivities, loss control recommendations, minimum premium, cancellation provisions, audit provisions
config.json
SenseML
{ /* SenseML: insurance quote extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "carrier", "description": "carrier name, quoting carrier, insurance company" },
{ "id": "total_premium", "description": "total premium, quoted premium, annual premium" },
{ "id": "each_occurrence_limit", "description": "each occurrence limit, per occurrence, occurrence limit" },
{ "id": "effective_date", "description": "effective date, proposed effective date" }
// + more fields, mapped to your schema
]
}
}
]
}Pre-built configurations cover common quote formats. New carrier or broker layouts map to your schema quickly. SenseML extraction logic is explicit and version-controlled.
Commercial package, general liability, workers compensation, commercial auto, cyber, professional liability, property, umbrella
Carrier system output, broker proposals, indication letters, binder quotes, renewal quotes
Answers about quote format support and comparative rating integration.
By default Sensible captures total premium, per-coverage premium, payment plans, installment amounts, taxes and fees, and any discounts or surcharges. Because the fields are set in configuration, you decide what to pull and how it's structured to match how your team prices or compares quotes.
Yes. Sensible outputs quotes in a consistent JSON schema regardless of carrier. You can programmatically compare coverages, limits, deductibles, and premiums across multiple quotes.
Yes. Quotes vary by carrier and line of business, and Sensible reads premium breakdowns, coverage terms, and conditions across those formats. A carrier or layout you haven't run before gets a config built to fit, so new sources don't mean a hard stop.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
Start free
Free 14-day trial. No credit card required. Start extracting in minutes.