LIFE INSURANCE
Renewals that stopped depending on someone checking a spreadsheet.
An insurance agency running its book out of a spreadsheet, where a renewal was only caught if a person happened to look at the right row in the right week.
The problem
What was going wrong
Policies were tracked in a spreadsheet. Renewals were being missed and there was no clear view of where any given prospect sat in the process.
A spreadsheet does not tell you anything until you open it. Every renewal depended on someone remembering to check, which means the failure mode is silent: nothing alerts you to the policy you did not notice.
What I built
The system, piece by piece
A six-stage pipeline
Every prospect sits at a visible stage rather than in a row that has to be interpreted. The stage itself drives what the system does next, so the pipeline is the source of truth instead of a report someone maintains alongside the real work.
Seven workflows, including a renewal cycle
The renewal workflow reactivates policyholders ahead of their date rather than after it has passed. The trigger is the policy date held on the record, so it fires whether or not anyone is watching that account.
A central exit workflow
One workflow cleanly removes a contact from every active sequence the moment they convert or opt out. It is a single place that owns the decision, rather than each sequence trying to check whether it should still be running.
Reasoning
Why it was built this way
Why the exit workflow matters more than it sounds
Without it, a contact can sit in two sequences at once and receive contradictory messages: a renewal reminder for a policy they just renewed, or a nurture email after they already said no. The client sees a business that is not paying attention, and the damage is done before anyone internally notices.
Why this is the failure I look for first
In accounts built by someone else, overlapping sequences with no central exit are the single most common thing I find. Each individual workflow looks correct in isolation. The problem only appears when two of them are true at the same time, which is exactly the case nobody tests.
What changed
The result
Renewals are triggered ahead of the policy date instead of being watched in a spreadsheet, and every prospect sits at a visible stage in one pipeline. The exit workflow means nobody receives two conflicting sequences at once.
Described in terms of what the system does. No performance figures are published here, because none have been independently verified.
Next Step
Recognise any of this in your setup?
Every project starts with an audit of what you already have, sent to you in writing before any building starts.