Who Owns Your Book of Business Data?

Agency valuations run on the book. Retention rate, mix of business, average account size, how concentrated the revenue is among top clients. Every one of those numbers comes from data, and that data lives in systems the agency does not own.

For most agencies this has never been a problem, which is exactly why it has never been examined.

Where an agency’s information actually sits

Take inventory and the picture is usually scattered.

Policy and client records live in the management system. Prospect and pipeline information lives in a spreadsheet or a producer’s notes. Commission history lives in whatever combination of carrier statements and workbooks the finance side uses. Client communication lives in email, spread across individual mailboxes. Service history lives partly in the management system and partly in the memory of whoever handled it.

Each of these is fine on its own. Together they mean there is no single place that represents the agency’s knowledge of its own book.

The moments this becomes real

Switching systems. An agency decides to move off its management system. The migration quote comes back higher than expected and the scope is narrower than expected: policies and clients transfer, activity history transfers partially, notes and attachments transfer poorly or not at all. Years of context about why decisions were made stays behind.

A producer leaves. Their client relationships are documented to whatever degree they chose to document them. If their pipeline lived in their own notes, it leaves with them. Agencies discover the extent of this a week after the resignation.

Due diligence during a sale. The buyer wants retention by segment, loss ratios by line, revenue concentration, growth by source. If that requires someone spending three weeks assembling it from multiple systems, that is not just inconvenient. It affects the perception of how well run the agency is.

A vendor changes terms. Pricing changes, a product is discontinued, an acquisition happens. Now the switching cost you never calculated becomes a negotiating position you do not have.

What “we own our data” usually means

Most contracts say the agency owns its data. The question is what retrieving it looks like.

Export scope matters more than export rights. A system that exports client and policy records but not activity history, attachments or notes is giving you a fraction. The fraction is often the part that was easiest to reconstruct anyway.

Format matters. A PDF report is not data. A structured file you can load somewhere else is.

Timing matters. Export available on request within thirty days is a different thing than export available whenever you want it, particularly in a situation where the relationship has gone sideways.

None of this suggests vendors are acting in bad faith. It reflects that export was not the feature they optimized for, because it is the feature that helps you leave.

What building your own layer changes

This is the practical argument for agencies that build systems alongside their management system rather than only inside it.

You control the data model, so it holds what your agency actually cares about rather than what the vendor anticipated. Client relationships across multiple policies. Why an account was lost. What a producer learned in a conversation two years ago.

You control access, so pulling the numbers for a valuation or a strategy question is a query rather than a project.

You control continuity. Changing management systems becomes a migration of policy servicing, while the relationship history, pipeline and commission analysis stay where they are.

This is not an argument for replacing everything. The management system does real work under real regulatory requirements, and rebuilding that is rarely wise. The argument is narrower: the information that represents your agency’s own knowledge should live somewhere you control.

The obligations that come with it

Holding your own data means holding the responsibility that goes with it, and insurance client data is sensitive.

Access controls that reflect who should see what, not everyone seeing everything because it is simpler. Audit logging, so there is a record of who accessed what. Encryption at rest and in transit. Backups that have actually been tested by restoring them. A retention policy that matches your state’s requirements rather than keeping everything forever by default.

These are not exotic requirements and any competent build includes them. But they are real, and an agency taking ownership of its data should understand it is also taking ownership of protecting it.

A thirty-minute exercise

Before deciding anything, do this.

Run a full export from your management system. Not a report. The export. Open the file.

Ask three questions. Is the client and policy data complete and structured. Is the activity history there, with dates and content. Are attachments and notes included.

Then do the same for any other system holding agency information.

Most agency owners find at least one gap they did not expect, and the gap is usually in the part that would take the longest to reconstruct. That is the piece worth addressing, and it is usually a much smaller project than replacing anything.

If you want to understand what your agency actually controls and what a layer you own would look like, get in touch.