Your Agency Runs on Two Systems That Never Talk: AMS360, Zoho and the Report That Joins Them

Ask the principal of an independent insurance agency where their numbers live, and the honest answer is "two places that do not talk to each other." The quote and the relationship sit in the CRM — Zoho, HubSpot, Salesforce. The bound policy, the premium, the endorsements and the commission sit in the agency management system — AMS360, Applied Epic, EZLynx. Both are doing their job. Neither knows what the other knows.

The moment a producer wins a deal, the story splits in half. Zoho recorded the opportunity; AMS360 recorded the policy. Nobody joins the two records — so the agency can tell you how many policies are in force, and separately how many deals closed, but not the one number that matters: which quotes actually became policies, by producer and by line.

That is not a reporting gap. It is a data foundation problem — and it is why the monthly board pack is rebuilt by hand in Excel, from an AMS360 canned report and a Zoho export, every single month.

Because the CRM and the management system never join, four expensive things stay invisible.

The true hit ratio. You know how many quotes went out and how many policies bound, but not which quote became which policy — so "conversion" is a guess, not a number by producer and line of business.

Retention, discovered too late. Most agencies find out a policy lapsed after it lapsed. The renewal date, the premium at stake and the rate shock are all knowable 90 days ahead — but only if someone is watching the book, not the calendar.

Commission variance, found by hand. Producer payouts are reconciled against split percentages manually, after month-end, when the carrier statement and the AMS360 record are compared line by line. The gaps are real money and they are found late.

The cross-sell book, unseen. The agency's single biggest source of cheap growth is the client who has one policy and should have two. But that list only exists where Zoho's prospect view and AMS360's policyholder view are joined — which is nowhere.

The fix is not a new CRM or a new management system. It is the layer that sits above both and joins them — Zoho Deal matched to AMS360 Policy on client and effective date, carrier statements reconciled against booked commission, all landing in one governed model that refreshes nightly instead of being rebuilt in Excel.

We build it on the Microsoft stack: Microsoft Fabric and OneLake hold the joined model, Power BI in Direct Lake carries the report, and Power Platform pushes the worklists back to producers. AMS360 and Zoho stay exactly where they are and mirror in.

Here is a screen-by-screen walkthrough of that report — five pages, illustrative figures, built on the structure I would put on an agency's own AMS360 and Zoho data. The demonstration book runs USD 42.8M in written premium across four GCC branches.

The Executive Summary is the page the principal opens: written premium, commission revenue, policies in force, retention rate and cross-sell depth, split new versus renewal, by branch and line of business. The commission number is tied to the policy that earned it — no manual reconciliation.

Behind it sit the four pages that do the work. Production reads the quote-to-bind funnel by matching Zoho Deals to AMS360 Policies on client and effective date, giving a real hit ratio by producer. Retention pushes a 90-day at-risk worklist to producers, ranked by premium at stake and rate shock, so the save happens before the lapse. Commissions models earned commission against split percentage and surfaces payout variances the day the transaction posts. And Pipeline joins Zoho's prospects to AMS360's policyholders to expose the single-policy clients ripe for a second line — the fastest revenue in the book.

The point is that the report is not four exports stapled together. It is one model, so the deal a producer closes in Zoho on Monday is in the hit ratio, the commission forecast and the cross-sell list on Tuesday.

The join is only as good as the client matching. If the same client is "ABC Trading LLC" in Zoho and "A.B.C. Trading" in AMS360, the match fails — and no model fixes a master-data problem it cannot see. The first work is usually a client-matching and dedupe pass, not a dashboard. We build it; the ongoing discipline is the agency's.

It does not replace the producer relationship. The at-risk worklist tells a producer which renewal to call and why — it does not make the call, and it does not know that the client's business changed in a way the data has not caught up with yet. The report ranks; the producer judges.

And it will not manufacture retention that the service model never earned. If clients leave because they do not hear from anyone between renewals, a better report just tells you that faster. The visibility is the start of the fix, not the fix itself.

You stop rebuilding the board pack in Excel, because the numbers reconcile themselves nightly. You know your real hit ratio by producer, so you coach on evidence rather than anecdote. You work renewals before they lapse instead of chasing them after. And the cross-sell book — the single-policy clients who should have two — becomes a worklist a producer can act on, not a report nobody runs.

That is the difference between a management system with a reporting tab and an operating picture of the whole agency. One tells you what is on the books. The other tells you what to do about it, today.