What PolDex is
PolDex is the callable insurance extraction layer. It takes insurance documents and returns evidence-backed JSON, CSV, XLSX, signed artifacts, and webhooks that downstream systems can trust.
Investor Diligence
Investor Diligence
The vertical API for entire insurance extraction.
PolDex turns insurance documents into structured, evidence-backed JSON, CSV, and XLSX through a self-serve API, processor, and agent interfaces. Commercial P&C is the first live wedge; the company ambition is the insurance extraction layer for every line of insurance.
Thesis
The layer every insurance workflow needs.
Insurance is not short of dashboards. It is short of reliable document-to-truth infrastructure that brokers, carriers, MGAs, claims teams, software companies, and agents can call programmatically.
What PolDex is not
PolDex is not a broker, carrier, agency management system, claims platform, or horizontal OCR wrapper. It sits underneath those systems as infrastructure.
Why the wedge is commercial
Commercial P&C has painful document density: COIs, policies, endorsements, schedules, submissions, loss runs, SOVs, and broker packets. That wedge proves the control layer before expansion.
Why the company can be huge
Every insurance line eventually needs the same primitive: turn messy documents into machine-readable truth. The API can expand across the whole insurance universe without becoming a workflow suite.
Expansion Path
Commercial first. Insurance-wide by design.
The product does not need a new company or new workflow for every line. Each expansion adds schema contracts, document profiles, evidence rules, and benchmarks on the same API rail.
01
Commercial P&C core
The live wedge: Commercial GL, Commercial Auto, Workers Comp, Umbrella/Excess, Commercial Property, and Professional Lines.
02
Commercial depth
Cyber, E&O, D&O, EPLI, Inland Marine, Cargo, Builders Risk, Surety, Bonds, Loss Runs, SOVs, ACORD forms, schedules, and endorsements.
03
Consumer P&C
Personal auto, homeowners, renters, flood, pet, travel, umbrella, and personal liability documents.
04
Claims
FNOL packets, loss notices, repair estimates, invoices, medical bills, adjuster notes, police reports, receipts, and claim correspondence.
05
Life, health, and benefits
Life policies, annuities, disability, dental, vision, group benefits, EOBs, enrollment forms, and benefits summaries.
06
Reinsurance and specialty
Bordereaux, treaties, facultative placements, captives, program business, parametric, trade credit, political risk, crop, aviation, marine, and energy documents.
Scale Path
Why this can become the insurance extraction layer.
The valuable surface is not a single dashboard. The valuable surface is the API standard every insurance workflow can call when it needs trusted data from messy documents.
Developer API
The API becomes the primitive other insurance software calls when a document appears anywhere in a workflow.
Agent infrastructure
MCP, CLI, OpenAPI, and schema discovery make PolDex callable by AI agents without a human clicking through a UI.
Embedded distribution
Broker tools, carrier systems, claims platforms, procurement products, and vertical AI companies can embed the same extraction rail.
Insurance-wide schemas
Every new line adds data contracts and benchmarks to the same platform, increasing coverage without forcing customers onto a new workflow.
Product Demo
The product is live enough to click through.
This is not a pitch-only product. The demo path starts on the public site, runs live proof, opens the playground, shows the no-code processor, and points to the production API/admin rails.
What the demo proves
Live product surface, not slideware.
API and no-code processor serve different technical levels.
Proof and playground are testable without buying credits.
Outputs are built for existing systems: JSON, CSV, XLSX, webhooks, and signed links.
The wedge is mid-size MGAs, brokers, and insurance ops teams before enterprise expansion.
Snapshot
The one-screen version.
The vertical API for entire insurance extraction, starting with commercial P&C.
Cloudflare Worker, Pages, D1, Queues, and production admin control plane.
Olamilekan Akinuli, solo founder based in Lagos, Nigeria.
Pre-revenue, product live, pre-seed fundraising.
Self-serve for anyone manually turning insurance documents into structured records.
MCP, CLI, OpenAPI, discovery files, and safe confirmation flow for agent workflows.
Commercial depth, consumer P&C, claims, life/health/benefits, reinsurance, specialty, and global variants.
Problem
Insurance operations still convert PDFs into systems by hand.
Manual bottleneck
MGAs, wholesale brokers, carriers, and compliance teams receive long policies, COIs, endorsements, schedules, and submission packets. The operational bottleneck is not reading one field. It is turning the whole document set into trustworthy structured data without hallucination.
Deterministic extraction rail
PolDex uses FastScript as the insurance control layer around extraction. Customer-facing output is stable: schema-constrained JSON, citations, truth states, confidence tiers, conflicts, unresolved items, exports, and webhooks.
No workflow lock-in
Developers integrate the API. Non-developers use the processor. Workflow connectors are the next adapter layer over the same rails.
Live Product
Do not take the pitch on faith. Click the product.
These are public product surfaces investors can inspect directly. No founder walkthrough is required.
Product Demo
Short product workflow video showing the live public surface and proof loop.
Open Product Demo ->Live Proof
Run real extraction on public insurance documents without an API key.
Open Live Proof ->Playground
Upload, paste, or link a document and inspect the structured output path.
Open Playground ->Processor
No-code processing surface for teams that need JSON, CSV, or XLSX without engineering work.
Open Processor ->Agent
MCP, CLI, OpenAPI, and discovery files for agents that need to call PolDex without a human browser workflow.
Open Agent ->Benchmark
Published benchmark surface for schema-aware proof and corpus readiness.
Open Benchmark ->API Docs
Public endpoint contracts, webhook behavior, schema discovery, and examples.
Open API Docs ->Status
Live health and readiness surface for the Cloudflare production path.
Open Status ->What Exists Today
Built, not just planned.
Self-serve API access and API-key based credit ledger.
No-code processor for file, URL, and pasted-text processing.
Six live commercial insurance schema families as the first wedge.
Evidence-backed JSON output with truth states, conflicts, unresolved items, and abstention.
Named JSON, CSV, and XLSX result paths.
HMAC-signed webhook delivery and delivery failure handling.
Admin control plane with audit, investor-safe mode, jobs, billing, benchmarks, trust, and operations views.
Public proof, playground, benchmark, docs, changelog, status, pricing, credits, and security pages.
Agent surface with MCP server, CLI, OpenAPI, discovery files, and client templates.
Business Model
Prepaid compute for insurance extraction.
How revenue works
Customers buy prepaid credits tied to an API key. Credits are estimated before processing, held on accepted jobs, captured on success, and released on system-side failure.
Why it is simple
No seats, no per-user pricing, no dashboard subscription, and no forced implementation services. Usage maps to extraction work.
Scale estimate
At 100 MGA or broker customers averaging $500-$1,000 per month, PolDex would reach roughly $600k-$1.2M ARR before enterprise contracts.
Market Size
Start self-serve. Expand into enterprise.
PolDex starts with everyone who manually handles insurance documents: agents, brokers, MGAs, procurement teams, property managers, construction operators, risk teams, claims teams, and compliance teams. Enterprise is the expansion path when larger buyers need procurement, SOC 2 readiness, custom retention, and contract preload.
568,800
US insurance sales agents in 2024
Source: BLS62%of insurance sales agents employed by agencies and brokerages
Source: BLS605,700US purchasing managers, buyers, and purchasing agents in 2024
Source: BLS466,100US property, real estate, and community association managers in 2024
Source: BLS$974.9BP&C direct written premiums reported with 84.41% of companies reporting 2024 data
Source: NAIC87.2%US commercial lines written premium placed by independent agents in 2024
Source: Big I via Insurance JournalProcessor Revenue Model
Assumptions, not claimed revenue.
This bottom-up model covers only no-code processor usage. It excludes developer API usage, enterprise preload contracts, embedded partner integrations, and future extension products built on PolDex core rails.
| Scenario | Processor users | Avg pages / month | Price / page | MRR | ARR |
|---|---|---|---|---|---|
| Early | 3,000 | 200 | $0.07 | $42,000 | $504,000 |
| Base | 10,000 | 250 | $0.06 | $150,000 | $1.8M |
| Scale | 30,000 | 300 | $0.05 | $450,000 | $5.4M |
| Large | 100,000 | 350 | $0.04 | $1.4M | $16.8M |
Competition
The market is crowded. The layer is different.
We are not claiming no one extracts insurance documents. Horizontal document AI APIs parse many document types, and workflow competitors extract as one feature inside broader products. PolDex makes insurance extraction the product, the way Stripe made payments programmable instead of becoming a bank dashboard.
| Category | Examples | Why PolDex is different |
|---|---|---|
| Horizontal document intelligence APIs | Reducto, LlamaParse, Unstructured, LandingAI, Extend | They are broad document parsing/extraction infrastructure across many industries. PolDex is vertical and insurance-native: line-specific schemas, policy/COI/endorsement logic, evidence, truth states, conflicts, exports, and ledgered delivery. |
| Workflow AI | Adaptional, FurtherAI, Pibit, Tesora, Mulligan, Stream | They extract as part of underwriting, intake, audits, or operations. PolDex sells extraction itself: API, processor, evidence, exports, webhooks, and ledger. |
| AI-native brokerages | Harper, Casey | They sell or intermediate insurance. PolDex does not compete with brokers; it gives brokers and insurance software companies structured data. |
| Cloud OCR and IDP platforms | AWS Textract, Google Document AI, Azure Document Intelligence, Instabase, Hyperscience, Rossum, ABBYY, Nanonets, Docsumo | They are broad enterprise document primitives or platforms. PolDex is focused on insurance truth, outputs, delivery, credits, and no-code/API operation. |
| Manual BPO | Operations teams and outsourced data-entry vendors | They re-key insurance data by hand. PolDex makes the extraction repeatable, auditable, and API-addressable. |
Go To Market
Start with buyers who feel manual ops immediately.
The first target is mid-size MGAs and wholesale brokers with recurring document intake volume but limited engineering capacity. Developers can use the API. Operators can use the processor.
The selling motion is proof-led: run documents, inspect output, validate evidence, then load credits.
Why Capital
Founder runway to keep product velocity high.
Founder-led customer discovery before any full-time sales hire.
Security, compliance, retention, and procurement readiness.
Benchmark corpus expansion and extraction quality work.
Cloud, model, and infrastructure credits for live customer workloads.
Agent Economy
Agents still hit the same insurance-document wall.
Why agents matter
AI agents can browse, research, and operate software, but insurance documents still arrive as messy PDFs with policy-specific language, endorsements, schedules, claim details, and evidence requirements.
Where PolDex fits
PolDex gives those agents a machine-readable extraction layer: MCP tools, CLI commands, OpenAPI, discovery files, schemas, estimates, and deterministic artifacts.
Positioning
PolDex remains insurance extraction infrastructure first. The agent surface expands who can call it without changing the core buyer, schemas, ledger, or evidence contract.
Risks
The honest risks and how PolDex is designed around them.
Accuracy risk
Use proof sets, benchmark gates, evidence citations, confidence tiers, abstention, and conflict surfacing instead of pretending every field is certain.
Distribution risk
Serve both developers and non-developers through the same infrastructure: API for technical teams, processor for operations teams.
Compliance risk
Keep SOC 2 preparation honest, add retention controls, deletion/legal-hold flows, audit logs, security docs, and procurement materials.
Model dependency risk
Keep provider names hidden and route customer-facing output through the FastScript abstraction so models can change without changing the product contract.
Investor FAQ
Questions an investor should ask before taking the meeting.
What does PolDex do?
PolDex ingests insurance documents such as policies, COIs, endorsements, schedules, claims packets, and submissions, then returns structured, evidence-backed JSON plus CSV and XLSX exports. Commercial P&C is the first live wedge.
Who feels the pain first?
The first buyer wedge is mid-size MGAs, wholesale brokers, and insurance operations teams that process hundreds of submissions or certificate packets every month but do not want another workflow platform. Technical teams use the API; operations teams use the processor.
Why is this not just another AI wrapper?
The model is not the product. The product is the control layer: schema enforcement, insurance-specific validation, confidence tiers, evidence, truth states, conflicts, abstentions, credit ledger, and delivery infrastructure.
Why no customer dashboard?
Insurance teams already have systems of record. PolDex is meant to feed those systems through API, webhook, exports, and a narrow processor, not replace their workflow with another portal.
How does PolDex connect to existing workflows?
PolDex connects to existing workflows without replacing them: API for developers, webhooks for systems, processor for ops teams, email intake for inbox workflows, signed links for third-party submissions, and CSV/XLSX exports for legacy systems.
Can non-developers use it?
Yes. The processor lets an operations person paste an API key, upload or link documents, approve an estimate, and download named JSON, CSV, or XLSX outputs.
How does PolDex make money?
Customers buy prepaid credits tied to an API key. Short/simple documents start at 1 credit, and larger work is estimated before credits are held. No seats, no overages, no hidden implementation fees.
What is the wedge?
Start with extraction infrastructure for commercial insurance documents, win mid-size operators that need immediate automation, then expand line by line into the default data layer for insurance workflows.
What is the Stripe analogy?
Banks and processors could move money before Stripe. Stripe made payments programmable. Horizontal document AI can parse files, and insurance AI platforms can extract inside workflows. PolDex makes insurance extraction programmable.
How is PolDex different from Reducto?
Reducto is a strong horizontal document intelligence API. PolDex is the vertical insurance truth layer: line-specific schemas, endorsement-aware fields, evidence citations, conflict surfacing, abstention, signed delivery, exports, credits, and admin rails for insurance operations.
What is proprietary?
FastScript, the extraction control layer: insurance schema contracts, deterministic validation, conflict handling, evidence scoring, adjudication rules, and provider abstraction around the extraction path.
What if a competitor adds an API?
An API added to a workflow product is still shaped by that workflow. PolDex is API-native from the root: no workflow lock-in, no brokerage conflict, and no requirement to move operations into our UI.
Why is Olamilekan the right founder?
He designed and shipped the full product end-to-end as a solo founder: API, processor, credit ledger, admin control plane, proof, benchmarks, docs, Cloudflare production deployment, and investor materials. The advantage is infrastructure focus and low burn, not another services-heavy workflow app.
What proof works live?
The live proof page runs public insurance documents without an API key, the playground accepts user-provided inputs, the processor supports API-key based no-code processing, and the status/docs pages expose the production path.
What has to be proven next?
Paid usage, repeatable extraction quality across more customer document families, distribution into MGAs and brokers, and continued compliance readiness for larger buyers.
PolDex is currently raising a pre-seed round.
For diligence, start with live proof and docs. For a conversation, email Olamilekan directly.