Fixed quote after a free call

Certificate of insurance automation for commercial agencies

Commercial clients need certificates fast, often the same morning a job starts, and each request arrives by email with different wording. We build a COI request form, check each request against the client's active policies, flag anything that asks for additional insured status or wording the policy may not support, prepare the certificate for a CSR to approve and keep a holder list so certificates can be reissued at renewal. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why COI requests swamp commercial CSRs

For contractor-heavy books, certificates of insurance are a daily flood. A general contractor needs one by 8am, a landlord wants specific wording, a client forwards an email chain with three holders buried in it. CSRs retype the same details into the same form all day.

Mistakes are costly. The standard certificate states it is issued as a matter of information only and confers no rights on the holder, and additional insured status needs an endorsement on the policy, not just a line on the certificate. Requests that ask for more than the policy provides must reach a person, not be issued automatically.

What we build

What our certificate of insurance automation includes

COI request form

A simple form for clients and their partners: holder name and address, project, required coverages and any wording requested.

Policy check

The request matched to the client's active policies and limits in the AMS.

Wording flags

Requests for additional insured, waiver of subrogation, primary and non-contributory or unusual limits flagged for CSR review.

Draft for approval

The certificate prepared in your AMS or certificate tool for a CSR to check and issue.

Holder list

Every holder kept against the policy so certificates can be reissued when the policy renews.

Request tracking

Status updates to the requester and a log of what was issued, when and by whom.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Request submitted

    A client or partner submits a COI request through the form or a forwarded email.

  2. 02 Automated

    Policy matched

    The request is matched to active policies and limits.

  3. 03 Automated

    Flags raised

    Special wording or coverage requests are flagged for review.

  4. 04 CSR or account manager review

    CSR checks and issues

    The CSR reviews the draft and issues it from the AMS or certificate tool.

  5. 05 Licensed agent or principal decides

    Coverage changes

    Whether to endorse the policy is decided by the account manager with the carrier.

How it behaves

How COI requests behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the requester sees

  • A short COI request form
  • A status update when the certificate is ready
  • A question back if they asked for wording that needs review

What CSRs see

  • Requests matched to the policy with flags
  • Drafts ready to check and issue
  • Holder lists for reissue at renewal

What the automation does

  • Parses requests and matches policies
  • Flags special wording and limits
  • Never issues a certificate without a person

Edge cases and fallbacks

Policy has expired or lapsed
Blocked and flagged to the account manager.
Requested limit exceeds the policy
Flagged; the CSR talks to the client before anything is issued.
Email request is ambiguous
Sent to the CSR unparsed rather than guessed.
AMS or workflow outage
Requests are queued and the CSR is alerted to issue manually.

Architecture

Certificate of insurance requests at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
COI request Form or email n8n workflow Parse and match Active policies Limits, dates Wording check AI, waivers, limits CSR Approves, issues Certificate sent Holder logged
  • Input
  • Logic and services
  • Data
  • AI step
  • People
  • Output

How it flows

  1. 1 A COI request arrives through the form or a forwarded email.
  2. 2 n8n parses holder details and matches the client's active policies and limits.
  3. 3 Special wording, additional insured and limit requests are flagged.
  4. 4 The CSR approves and issues the certificate, and the holder is logged for reissue at renewal.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Certificate of insurance requests project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Request volume, current certificate tool, AMS access and common wording requests.

  2. 02

    Design

    2 to 3 days

    Form fields, flag rules, approval step and holder list.

  3. 03

    Build

    1 to 2 weeks

    Form, email parsing, policy match, flags, drafts and logging.

  4. 04

    Shadow run

    About 1 week

    Drafts produced beside the CSRs' own certificates and compared.

  5. 05

    Launch

    1 to 2 days

    Share the form with key commercial clients and train CSRs.

  6. 06

    Support

    Ongoing

    New flag rules and form changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Web request form AMS certificate module (access confirmed per project) Claude or OpenAI for email parsing Your email provider Slack or Microsoft Teams alerts

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Form, flag rules and approval step.

    $200 – $400

  • Build

    Parsing, matching, flags and holder list.

    $500 – $1,300

  • Integrations

    AMS, email and alert channels.

    $150 – $400

  • Testing and shadow run

    Drafts compared with CSR certificates.

    $100 – $250

  • Launch and training

    Form launch and CSR walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Certificates are issued from your AMS or certificate tool; writing drafts into it depends on the access your vendor allows. Software is billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • AI model usage: Billed by the provider per use; parsing requests is a small monthly amount.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

Certificates confer no rights

The ACORD 25 certificate states it is issued as a matter of information only and confers no rights upon the certificate holder, and additional insured status requires an endorsement.

Source: www.dfs.ny.gov

US: insurance data security

Certificates show client and policy details, so the request form and logs sit inside the agency's information security program under state laws based on the NAIC model.

Source: content.naic.org

EU and UK: accuracy

Holder and client details must be accurate and kept up to date under Article 5 GDPR, so holders are kept against the policy, not in inboxes.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Certificate of insurance requests questions, answered.

It turns COI requests into structured data, checks them against the policy, flags unusual wording and prepares the certificate for a CSR to issue. It does not issue certificates on its own.

Yes. A simple form replaces back-and-forth emails, and forwarded email requests are parsed into the same format.

No. Additional insured status needs an endorsement on the policy. Requests that ask for it are flagged so the account manager can confirm with the carrier.

We prepare drafts in your AMS certificate module or certificate tool where access allows, or hand the CSR a completed summary to issue in a few clicks.

It keeps a holder list per policy and prompts a CSR to reissue when the policy renews.

Requests per week, time from request to certificate, flagged requests and reissues completed at renewal.

Free 20-minute call

Want this for your insurance broker?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call