Quote and claims flows that survive an interruption
Insurance software is a long form and a complicated rulebook meeting a customer who mainly wants to be finished. We build quote and claims flows that stay accurate without punishing the person filling them in, plus the internal tooling that handles everything after the sale.
What makes insurance software hard
Before anything about us. These are the constraints that shape every insurance build, and the reason generic delivery comes unstuck here.
Every field costs completions
Quote and claims forms are long by nature, and each question that cannot justify itself takes a share of the people who started.
Rules change on a business timetable
Eligibility and pricing move when underwriting decides they move, which is never aligned with an engineering release cycle.
Evidence arrives as phone photos
Claims come in as blurred images and PDFs attached to an email, and somebody sorts them by hand into the right file.
Insurance capabilities
Four areas we take on in this sector. Each one is work we do rather than a category we list.
Long forms that survive an interruption
Nobody fills in an insurance quote in one sitting. They start on a laptop at work, get interrupted, and finish on a phone that evening if the form let them. Designing as though they will not is why these flows leak.
- Multi-step quote flows
- Save and resume across devices
- Validation in place, not on submit
- Conditional questions that skip cleanly
- Document and evidence upload
- Payment and policy issue
Where these projects actually go wrong
The recurring failure patterns in this sector, what we do differently, and what that changes. You will not find a claimed figure here. Those belong to engagements we can name, and we do not name what we cannot evidence.
The quote form assumes one uninterrupted sitting, so anyone who gets interrupted starts again or does not come back.
Save and resume across devices, conditional questions that skip cleanly, and progress indication that reflects the work genuinely remaining.
An interruption stops being the end of the application.
Eligibility and pricing rules live in application code, so an underwriting change waits for a release slot.
Rules moved into a versioned, auditable configuration layer that business owners can change, with the full history retained.
Rule changes move at business speed, with a record of what changed, when, and by whom.
Customers cannot see where their claim has reached, so they ring to ask, then ring again two days later.
Customer-visible claim status with stages that mean something, evidence requests surfaced in the interface, and a notification when the state moves.
The most common support call has an answer the customer can reach without making it.
Claims evidence arrives as phone photos and PDFs by email and gets filed by hand against the right claim.
Upload pipelines with validation and scanning, capture designed for a phone camera, and storage linked to the claim record on arrival.
Evidence lands attached to the claim instead of sitting in an inbox waiting to be sorted.
Commitments, not promises
How we build for insurance clients. Each one is checkable in the work itself rather than a claim about results you cannot see.
Save and resume as standard
Long forms persist progress across devices, because designing for one uninterrupted sitting is designing for a customer who does not exist.
Rules live outside the code
Eligibility and pricing sit in a versioned configuration layer, so a business change does not queue behind a deployment.
Status the customer can see
Claim state is visible in the interface, which removes the reason for the most common call your handlers take.
Three ways this usually starts
Prices are not listed because they depend on scope. We quote a range after discovery, along with the specific things that would move it toward each end.
Discovery
Best before you commit
A short paid engagement that ends with a scoped plan you own, whether or not we build it. If the honest answer is that you should not build software at all, that is what the document will say.
- Requirements and constraints captured
- Technical and integration assessment
- Architecture and approach outline
- An estimate as a range, with its drivers
- Risks named rather than implied
Project build
Best for a defined outcome
A scoped build with an agreed deliverable, run in short cycles with something you can review at the end of each one. Suited to work where the shape of the outcome is already clear.
- Fixed scope with a change process
- Something reviewable every cycle
- Design, build, test, and deploy
- Documentation and runbooks
- Handover to your team
Dedicated team
Best for an ongoing roadmap
A small team working continuously against your priorities, with capacity you can plan around. Suited to products that keep changing rather than projects that finish.
- Named engineers, consistent over time
- Priorities you set each cycle
- Direct access to the people building
- Shared repository and tooling
- Exit on notice, with no lock-in
What we tell clients before they add an LLM to their product
Most requests we get for AI features describe a solution rather than a problem. The useful first conversation is about what happens when the model is confidently wrong.
How we scope a project, and why we sometimes say no
A scoping call that ends in an honest no is worth more to both sides than an engagement that starts on a misunderstanding.
Server rendering, and why your SEO still depends on it
Search engines execute JavaScript now. That has not made client-only rendering safe for anything whose discovery matters to the business.
Insurance: what buyers ask us
Including the ones where the answer is no. A limit stated up front is worth more than a capability claimed now and found out later.
Where it exposes an API or a supported exchange format, yes, and that is the normal shape of this work. We build the customer-facing flows and internal tooling around your system of record rather than replacing it, keep it authoritative, and put a stable internal contract in front of it so product work is not tied to its release cycle.
We build the flows and the configuration layer around rating, and integrate with a rating engine or provider APIs where one exists. Actuarial pricing is not our discipline, and we would rather integrate with the people who own it than approximate it badly. Where the rules are simple and business-owned, an externalised rules layer is often enough, and we will tell you which case you are in.
Mostly by removing work rather than adding persuasion. Save and resume as standard, questions that skip cleanly when they do not apply, validation in place rather than on submit, honest progress indication, and a hard justification demanded of every field that stays. Most abandonment is caused by the form, not by the price at the end of it.
Uploads are validated and scanned before they are stored, held encrypted with access scoped by role, and linked to the record they belong to rather than dropped into a general bucket. Retention and deletion rules are configured deliberately, because claims documents are exactly the category where keeping everything forever turns into a liability.
That is the point of moving them out of the code. Eligibility and pricing sit in a versioned configuration layer with an audit history, so a business change does not need a deployment. There are limits. Genuinely structural changes still need engineering, and we are explicit at design time about exactly where that line falls.
Neither. We are a software firm, not an insurer, a broker, or a regulated intermediary. We build to the controls and disclosure requirements your compliance function defines, produce the audit evidence, and document the architecture for assessment. Regulatory responsibility stays with you, and a vendor claiming otherwise deserves a much closer look.
Industries we work in
Healthcare
Patient portals and clinical tooling, built to be audited
Fintech & Banking
Payment flows and the ops tooling behind them
E-commerce & Retail
Storefronts that load, checkouts that finish
Education
Learning platforms built by people who run one
Logistics
Tracking and field apps for teams without a signal
Real Estate
Listing platforms that are fast and findable
Manufacturing
Production visibility for the floor and the office
Let's talk about your insurance project
A scoping conversation costs nothing. You leave with a clear view of the approach, a budget range, and the main risks named out loud, including an honest no if we are not the right firm for this.