Skip to content

Industries · Insurance

Insurance software built for how policies really move

We build quoting and application flows, policy and claims portals, and the integrations that keep your broker management system in step. Clear scope, a working demo every week, and code your brokerage owns outright.

You own the code and IP Weekly demos Reply within one business day

Agent running - queue empty

Flow 04

01

Trigger

Webhook

02

Enrich

Normalise

03

Decide

Policy

04

Act

Resolve

Run log

> Matched 42 records

> Routed 7 exceptions to a human

> Closed 35 tickets automatically

35

Auto-resolved today

6h

Engineer time saved daily

Insurance, in short

OlDevs is a full-stack technology studio in Vancouver that builds software for brokerages, MGAs and carriers.The work covers quoting and application flows, policy and claims portals, broker management system integrations, document automation and AI assistance for policy questions. Every build is designed around privacy duties, record keeping and WCAG 2.2 AA accessibility, and clients own all code, designs and accounts. Request a quote to scope your project.

Key facts

01term
value
02term
value
03term
value
04term
value
05term
value
06term
value

Insurance

What insurance teams bring us

The problems we are asked to solve most often — and how.

01

Quoting flows that lose people midway

Applications ask for everything up front, so applicants abandon them. We rebuild the flow in stages, save progress between sessions, prefill what you already know, and show a clear quote before anyone is asked to sign anything.

Quoting · Conversion · Forms

02

Policy data trapped in the broker system

Your broker management system holds the record of truth, but the website cannot reach it. We build an integration layer with mapped fields, retries and audit logging so the portal and the policy system stay in agreement instead of drifting apart.

Integrations · Data quality · BMS

03

Claims that go quiet after submission

A claim is filed and then the client hears nothing, so they phone. We add status tracking, document upload with clear file rules, adjuster notes the client can actually see, and notifications that fire on real events rather than a fixed schedule.

Claims · Client portal · Notifications

04

Renewals and documents handled by hand

Renewal letters, certificates, pink slips and endorsements get assembled one at a time in email. We automate generation, versioning and delivery, with templates your compliance lead approves and a durable record of what went to whom and when.

Documents · Automation · Renewals

05

Policy questions that never scale

Staff answer the same coverage and eligibility questions all day. We build AI assistance grounded in your own wordings and manuals, with citations back to the source document and a clear handoff to a licensed person for anything close to advice.

AI assistance · Service load · Guardrails

06

Privacy and record keeping under pressure

Personal and sometimes health information sits in every application, and provincial rules add duties on top. We design for PIPEDA and provincial privacy law with role based access, retention rules, encryption in transit and at rest, and logs an auditor can read.

Privacy · Record keeping · Security

Process

How a build runs

  1. Discovery

    We sit with underwriting, service and claims people to map the lifecycle, the systems in play, the documents produced and the rules that constrain all of it. You get a written scope with assumptions stated plainly.

  2. Architecture and integration plan

    We confirm what your broker management system, rating service and payment provider can actually do, then design the data model, access rules and integration layer around those facts rather than around hope.

  3. Weekly build

    One accountable team builds in short cycles with a working demo every week. You review real screens with real data flowing, so changes land while they are still inexpensive.

  4. Compliance and accessibility review

    Before launch we run WCAG 2.2 AA checks, security review, retention and access testing, and a document trail walkthrough with your compliance lead. Findings are fixed and re-tested, not filed away.

  5. Launch and support

    We deploy into your own accounts and repositories, hand over documentation and runbooks, train your staff, then stay on for monitoring and iteration for as long as you want us there.

How we work

How we work with insurance teams

01

We start with the policy lifecycle

Before any screens, we map how a risk moves from enquiry to quote, bind, endorsement, renewal and claim in your business. The software follows that map instead of forcing your team into a generic template.

02

Integration first, interface second

We prove the connection to your broker management system, rating service or carrier feed early, because that is where projects usually stall. Once data moves reliably, the interface work becomes predictable.

03

Forms built for real applicants

Long applications are where accessibility and drop off problems live. We stage questions, validate inline, keep progress saved, and test with keyboard and screen reader use so the flow works for everyone who needs cover.

04

Documents treated as a system

Certificates, wordings, endorsements and renewal packages get templates, version history and an approval path. Generation and delivery are automated, and every produced document is traceable back to the data that made it.

05

AI with a visible source

Assistance is grounded in your own documents, answers cite the wording they came from, and anything resembling advice or a coverage decision routes to a licensed person. Conversations are logged for review.

06

Compliance built in, not bolted on

Access control, retention, consent capture and audit trails are part of the architecture from day one. Your compliance lead and counsel review the approach while it is still cheap to change.

Weekly

Working demo cadence

One business day

Reply to every enquiry

Since 2014

Building software from Vancouver

FAQ

Insurance — questions we hear first.

Usually yes. If it exposes an API, we map the fields we need and build a sync layer with retries, conflict rules and audit logging. If it does not, we work with scheduled exports, secure file transfer or a middleware layer. We confirm what is genuinely possible during discovery, before anything is committed to a plan.

All three, though the work looks different in each. Brokerages usually need quoting, client portals and broker system integration. MGAs need submission intake, binding workflows and carrier reporting. Carriers tend to need claims portals, self serve policy changes and document automation at higher volume. Request a quote and we will scope yours.

We design to the privacy rules that apply to you, which for most Canadian insurance work means PIPEDA plus provincial law such as Quebec Law 25, and health information rules where benefits data is involved. In practice that is role based access, retention and deletion rules, encryption, and readable audit logs. We are not lawyers, so your counsel signs off on the policy positions.

Yes, if the line is drawn clearly. We ground the assistant in your own wordings, manuals and underwriting guidelines, show citations to the source document, and restrict it to explaining what a document says. Anything that looks like a recommendation or a coverage decision routes to a licensed person, and every conversation is logged for review.

We build to WCAG 2.2 AA, which matters in insurance because long applications are exactly where keyboard and screen reader problems surface. We also have bilingual English and French capability, so quoting flows, policy documents and notifications can be delivered in both languages from a single content model.

It depends on scope and on how ready your integrations are. A quoting flow or a single portal is a much shorter piece of work than a full policy servicing and claims platform. Either way you see a working demo every week, so you judge progress yourself instead of waiting for one reveal at the end. Request a quote for a timeline against your scope.

You do. Clients own all code, designs, accounts and intellectual property from the first commit, held in their own repositories and cloud accounts. That matters in insurance because regulators and carrier partners ask about vendor dependency. If you ever move on from us, nothing has to be rebuilt or re-licensed to keep running.

Still have a question? Ask us when you request a quote

Let’s connect

Tell us about your project.

We’ll reply within one business day with next steps and a tailored quote — no obligation.

We’ll only use your details to prepare your quote. No lists, no spam.

Call us Request a quote