Fixed quote after a free call

Insurance renewal automation that starts the work months ahead

We build a renewal workflow that reads expiry dates from your AMS, opens each renewal at a lead time set by line of business, sends the client a tailored information request, chases replies, compares what came back with last year and lists the changes for the account manager. Marketing the risk and recommending cover stays with your licensed team. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why insurance renewals start too late

Commercial renewals need fresh exposure data, updated schedules and time to approach the market. When the pipeline lives in memory and spreadsheets, information requests go out late, clients reply in the final fortnight and account managers end up renewing as-is because there is no time to remarket.

Personal lines renewals pile up differently: hundreds of policies a month, rate increases clients only notice when the bill arrives, and calls that come too late to review options. A renewal process that starts on time is the simplest retention tool an agency has.

What we build

What our insurance renewal automation includes

Pipeline from expiry dates

Renewals opened automatically at lead times you set, such as 120 days for commercial packages and 45 for personal auto.

Tailored information requests

Questionnaires for the line of business, prefilled with last year's answers for the client to confirm or change.

Chasers and escalation

Polite reminders to the client, then a task for the account manager if nothing comes back.

Change summary

A side-by-side of this year's answers against last year's, so the account manager sees what changed without judging what matters.

Rate change review list

Personal lines renewals with notable premium changes listed for a review call, using a threshold you set.

Renewal dashboard

Every renewal by stage and days to expiry, by account manager.

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

    Renewal opens

    At the agreed lead time the workflow creates the renewal from the AMS expiry date.

  2. 02 Automated

    Information requested

    The client gets a prefilled questionnaire for their line of business.

  3. 03 Automated

    Replies chased

    Reminders go out, then a task for the account manager.

  4. 04 CSR or account manager review

    Account manager reviews

    The account manager checks the change summary and markets the risk.

  5. 05 Licensed agent or principal decides

    Recommendation

    Which terms to recommend and how the risk is presented is decided by a licensed agent.

How it behaves

How the renewal pipeline behaves

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

What the client sees

  • An early, clear request with last year's answers prefilled
  • A few reminders, then a call from their account manager
  • More time to discuss options before expiry

What account managers see

  • A renewal board by days to expiry
  • Change summaries ready when information comes back
  • Tasks for clients who have not replied

What the automation does

  • Opens renewals at the lead time for each line
  • Sends and chases information requests
  • Never recommends cover or sends notices without approval

Edge cases and fallbacks

Policy cancelled mid-term
The AMS status removes it from the pipeline.
Client replies by phone
The account manager marks the request complete and chasers stop.
Large change in exposures
Listed at the top of the summary for the account manager.
AMS unavailable overnight
The run is skipped and retried, never sent from stale data.

Architecture

A renewal pipeline for an insurance agency at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
AMS Expiry dates n8n schedule Lead times by line Info request Prefilled form Change summary Vs last year Account manager Market and advise Renewal board By stage
  • Input
  • Logic and services
  • Output
  • AI step
  • People
  • Data

How it flows

  1. 1 Each night the workflow reads upcoming expiries from the AMS and opens renewals at the lead time for each line.
  2. 2 Clients receive a prefilled information request with reminders until they reply.
  3. 3 Replies are compared with last year and the changes are listed.
  4. 4 The account manager reviews, markets the risk and advises; the board shows every renewal by stage.

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.

Renewal pipeline & client information requests project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Lines of business, lead times, current questionnaires, AMS access and notice rules where you operate.

  2. 02

    Design

    2 to 3 days

    Questionnaires per line, chaser timing, change summary format and dashboard.

  3. 03

    Build

    1 to 2 weeks

    AMS read, scheduling, forms, chasers, summaries and dashboard.

  4. 04

    Shadow run

    About 1 week

    Renewals are opened and listed, but requests go to a test inbox for account managers to check.

  5. 05

    Launch

    1 to 2 days

    Start with one line of business, then add the rest.

  6. 06

    Support

    Ongoing

    New lines, questionnaire changes and notice rule updates.

What it runs on

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

n8n Applied Epic SDK, AMS360 APIs, NowCerts API or AMS export Secure form tool DocuSign for signed applications Twilio SMS and email Claude or OpenAI for change summaries

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

    Lines, lead times, questionnaires and dashboard.

    $200 – $400

  • Build

    Scheduling, forms, chasers and change summaries.

    $500 – $1,300

  • Integrations

    AMS, form tool, e-signature and messaging.

    $150 – $400

  • Testing and shadow run

    QA and a test-inbox run checked by account managers.

    $100 – $250

  • Launch and training

    Switch-on per line and 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. Form tool, messaging and n8n are billed to you directly. AMS access may need vendor approval.

Monthly running costs you pay directly

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

  • Form tool: Your secure form provider's own plan.
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • AI model usage: Billed by the provider per use; change summaries are short.

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.

UK: Consumer Duty

The FCA Consumer Duty sets high standards of protection for retail customers and requires firms to put their interests first, which shapes renewal communications and timing.

Source: www.fca.org.uk

US: notice rules vary by state

Cancellation and non-renewal notice periods are set state by state, so the workflow follows the rules your compliance team confirms for each state. General information, not legal advice.

Source: content.naic.org

US: protect client data

The NAIC Insurance Data Security Model Law requires licensees to maintain an information security program; renewal questionnaires go through secure forms, not open email.

Source: content.naic.org

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

Renewal pipeline & client information requests questions, answered.

It opens each renewal on time, sends the client the right questions, chases replies and shows what changed, so account managers spend their time on the market and the client rather than on chasing.

It depends on the line. Commercial packages often need months to gather data and remarket; personal lines need less. You set the lead time per line and the workflow keeps to it.

No. It lists differences from last year. Judging what is material and how to present the risk is the account manager's job.

It can prepare them for review against your checklist. Notice content and timing rules vary by state and country, so a person approves before anything is sent.

Yes, through the Applied Epic SDK or Vertafore's APIs and partner routes where your agency has access, or from a scheduled export if not. We confirm the route first.

Renewals opened on time, information returned before the target date, renewals remarketed and retention by line.

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