Advanced Agent Marketing

In insurance, a lead contacted within minutes converts at a dramatically different rate from the same lead contacted the next morning. Everything in this platform is downstream of that fact: not the reporting, not the interface, but the number of seconds between a prospect submitting a form and an agent being on the phone.

That reframes the architecture. The system is not a marketing dashboard that happens to route leads; it is a routing system that happens to produce reports.

Every ad platform reports conversions using its own attribution window and counts what it can see. They are, structurally, grading their own work, and their totals are generous by design. Add a CRM with a different definition of a qualified lead and the numbers will never reconcile on their own.

The fix is not a smarter reconciliation algorithm. It is deciding, once and explicitly, which definition is authoritative, then counting events once in a single store using that definition and treating each platform's figure as an input rather than as truth. Making that decision visible instead of encoding it silently is what stops the same argument recurring every reporting cycle.

Ad platforms and CRM systems change their APIs on their own schedule, and the failure is rarely an outage. A field is renamed, a value that was a percentage becomes a fraction, a deprecated endpoint starts returning partial data. Everything continues to run and the numbers quietly become wrong.

So the pipelines were built to assert on their own data rather than only on their own code - row counts within expected bounds, freshness checks, and reconciliation against the source. A pipeline that stops loudly is a minor incident; one that keeps running with bad data is a decision made on a false premise, and it can run for weeks.

Booking looks trivial until the states between "link sent" and "meeting happened" are enumerated: booked, rescheduled, cancelled, no-showed, rebooked after a no-show. Each means something different commercially, and a system that only records bookings reports a pipeline that does not exist.

Calendly's webhooks make these states available, and the work was in modelling them honestly and making sure the CRM and the reporting layer agree on what each one means. It is unglamorous, and it is the difference between a forecast an agency owner can act on and a number that flatters everybody.

A marketing platform that only its builders can operate is a liability for the agency that owns it. Configuration lives in the interface rather than in code wherever it reasonably can, so adding a campaign source or adjusting routing does not require a developer and a deployment.

That constraint costs more up front and it is the reason the system does not need us to keep running.