An x-date register that gives every commercial prospect a date to be contacted on

Commercial insurance has a buying window a producer cannot influence and can absolutely miss. A prospect who is content with their broker in July is a different person in the weeks before their policy renews, and the whole job is being present in that window with something to say. Most agencies hold that information as producer knowledge: the renewal dates that matter live in one person's head or in a note field on a contact record, and when that producer is busy in March the accounts renewing in April get contacted in May.

The single most valuable field on a commercial prospect record is a date, and in most agencies it lives in a note that nothing reads.

1. 01

   The x-date is a scheduling field, not a note

   A renewal date stored as free text cannot fire a sequence, cannot be sorted and cannot be reported on. Stored as a date field it becomes the spine of the whole outbound programme: every contact window in the agency is derived from it arithmetically.

2. 02

   The window is derived, not chosen

   Contact windows are calculated from the x-date rather than set per account — a first touch at a defined lead time, a second inside the decision window, a post-renewal touch for accounts that stayed put. A producer who wants a different cadence changes the lead time on that record, and the change is visible to everyone.

3. 03

   An unknown x-date is a task, not a blank

   Records without a renewal date generate a discovery task rather than sitting inert. Finding out when an account renews is a five-minute conversation and it is the highest-value five minutes in the prospecting week, so it gets scheduled like work rather than left to chance.

4. 04

   Line of business changes the lead time and nothing else

   A workers' compensation renewal and a commercial property renewal have different decision lead times and the same structure. One register with a lead-time value per line is far more durable than separate programmes maintained per line.

Commercial insurance is the one category where organic and paid acquisition cost effectively the same — **$590 vs $600, blending to $593** (First Page Sage, Jan 2026). When the channel choice is worth ten dollars, timing is the real lever — reaching the prospect in their renewal window beats out-spending competitors year-round.

The register holds one row per prospect account: renewal date, line of business, derived lead time, the calculated first-touch and decision-window dates, the incumbent broker where known, the owning producer, and a confidence flag on the date itself — a date from a conversation and a date read off a declarations page are not the same asset. Sequences trigger from the calculated dates rather than from list membership, so an account added in June with a September renewal enters at the right point rather than at the start. Records with no date generate a discovery task and reappear until the field is filled or the account is closed out.

1. 1

   Week 1

   Field schema

   Date field, confidence flag, lead time by line of business, derived-date formulas

   Owner: OmniFlow

2. 2

   Weeks 1–2

   Register build

   Existing prospect records audited, dates migrated out of note fields

   Owner: OmniFlow + agency ops

3. 3

   Week 2 onward

   Discovery tasks

   Every dateless record generates a task until the field is filled or the account is closed out

   Owner: Producers

4. 4

   Weeks 2–3

   Sequence wiring

   Touches triggered from calculated dates rather than from list membership

   Owner: OmniFlow

5. 5

   Post-renewal

   Cycle close

   Date confirmed or corrected for the following year, confidence flag updated

   Owner: OmniFlow + producers

This entry makes no performance claim. It documents a record structure and a timing rule, and the waste that rule removes: prospecting effort spent on accounts ten months from a decision while accounts three weeks out go untouched.

These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.

The first build treated the confidence flag as optional and it was left blank on most migrated rows, which meant a date a producer half-remembered from two years earlier drove the same sequence as a date read off a declarations page. The flag is now required at entry, and a low-confidence date generates a verification task ahead of the first touch rather than triggering it.

Real client work that shipped. No performance figures are published, because none have been verified and approved for release. See all our work