Bradley Chesnut

CP Manager Had To Be Invented

CP Manager Had To Be Invented — Then Our Programmers Had To Be Taught How To Build It

(Seriously. Continue reading to see why our programmers had to be "taught" a new style of programming.)

Here's why the first workflow-driven agency management system took longer — far longer — than anyone else's...

Since 1990, I've worked as an insurance automation consultant helping agencies increase productivity and efficiency, and along the way, selling agency management systems at the highest level for two different companies: Agency One and InStar. Both are gone now. But for over a decade, I was the top producer for each of them and their lead consultant.

Having worked as a productivity consultant to agencies and having actually represented two different system vendors taught me something no programmer ever could have: what actually happens inside an agency when the software gets in the way.

Every year, in agency after agency, I saw the same thing. CSRs re-entering the same data three times. Producers avoiding the system because it fought them. Commercial lines treated like an afterthought. And every time I brought it back to the vendor — "here's what needs to change, here's how to fix the workflow, here's what would make this system actually productive" — I got the same answer:

"We can't do that. Our table structures don't support it."

I heard that sentence more times than I can count. Different vendor, different system, same wall.

The Wall Every Agency Management System Hits

Here's what most agency owners never see, because it happens before they ever log in: every agency management system starts life as a database. 

Someone decides what the client table looks like, what the policy table looks like, how notes and follow-ups and correspondence get stored — and then, once agencies start going live on it, that structure is locked. Permanently.

From there, a vendor can add features on top all day long. New screens, new reports, a new integration here and there. What they can never do is go back and change the foundation. The table structure is the system. It determines how many clicks it takes to process a task, how many windows a CSR has to jump between, how data does or doesn't flow from one screen to the next. And once it's set, it's set.

That's why every "workflow improvement" I ever proposed to a vendor died the same way. Not because they didn't want to fix it. Because they couldn't — not without tearing out and rebuilding a system that already had live agencies on it. Nobody was going to do that.

Those who design systems believe features are the key, and they all strive to create one "wow" feature to impress agencies with. In addition to this, starting with features is typical because that's how programming teams write database programs. Client database first, policies, notes and the rest bolted on as features.

Workflows, if they ever get addressed, are added on top afterward, working around a table structure foundation that was never built to support it. That's not a knock on the programmers who built them. That's just how programmers have been taught to build database systems in this industry and every other industry.

I Actually Built A Process-Driven System

I'm not just an insurance automation consultant who talks about workflow — I've built it.

Before CP Manager, I wrote a process-driven agency management system from scratch for a specialized agency that couldn't use a traditional AMS at all — their business was too unique for anything off-the-shelf.

Other programmers quoted them up to $75,000. I built it for $21,000, and it outperformed every one of those quotes.

I turned their busiest season into push-button processing — update a record, generate the paperwork, print the labels — and the job that used to take 8 people to process, one person could now handle alone.

The key to dropping the number of people from 8 down to 1 to handle the job was having a very clear understanding of "how" they processed the work, and then building the system around that.

It wasn't about features. It was solely about how they did the job, and then automating everything. If changing one field meant three others had to update too, we automated the cascade — change one, the rest were updated also.

With the extensive knowledge I had on workflows, productivity strategies, agency management systems, relational databases...

I Set Out To Build A System Backwards By Starting With Workflows

In 2007, I started designing something different: a system where the workflow comes first, and the table structure gets built to serve it — not the other way around. It took a year alone just doing the blueprint.

That sounds simple. It isn't. It meant that before a single table got designed, we had to map out, in detail, exactly how each policy task actually gets worked — new business, renewals, endorsements, claims, cancellations — across every line of business, because each one genuinely works differently.

I listed out each of the service tools needed to process the work and how they should operate to support the task at hand.

Everything was evaluated. And every service tool from notes to attachments was overhauled to support a workflow driven system with an emphasis on increased productivity.

Only after all of this, after everything was mapped out, could the database get built to fit it.

The problem: no programmer had ever built a system this way. 

Not because it's a bad idea — because standard training doesn't teach it. Every programmer who's ever built a database system was taught the same way I have watched play out the past 30 years of working with agencies to increase their productivity: start with the objects, build the features, ship it.

Starting with workflows and building table-structure-derived-from-workflow isn't a technique you hire for. It's not in the curriculum programmers learn from. I had to teach it, team by team, from scratch.

Why I Wouldn't Let It Slide

I know exactly what needs to happen for an agency to run efficiently. I'm not guessing at it — I spent over 3 decades watching agencies get stuck inside systems that couldn't fix themselves, and I know precisely which decisions cause that.

So when our programming team, mid-project, fell back into old habits by solving a problem the "feature-first" way because that's what they'd been trained to do their whole career, I didn't let it stand. I had them rip it out.

Not patch around it. Literally rip it out and rebuild it the right way, even when that meant walking away from work that was already done.

We lost a good year because of this alone, which happened way too many times. It's just not how programmers are taught to write database programs.

Programmers loved working with me for the same reason some of them hated it: I wasn't going to compromise on the one decision you don't get a second chance at.

You can add a feature next year. You cannot fix foundational table structures after agencies are live on the system. Get it wrong upfront, and you've built exactly the kind of system I spent thirty years watching agencies get trapped inside.

That's Why It Took This Long

Not because we were stalling. Because this had never been done before, and doing it right meant inventing the method, teaching it to programmers who'd never worked that way, and enforcing it every single time the old habits crept back in.

Could a version of CP Manager have shipped years ago?

Sure, if I'd been willing to let table structures get set the same way every other system's did. I wasn't. I'd already watched what that costs an agency, from the inside, as the person agencies trusted to tell them how to fix it and having to tell them, every time, that the fix wasn't possible.

CP Manager exists because I refused to hand agencies a system with that same wall built into it. It's still the only agency management system built based upon workflows as the foundation to the system, where the table structures were designed to support how the work actually gets done instead of building another feature-driven system first and asking the workflow to fit in around them afterward.

That's not a system that gets built fast. It's a system that gets built once, right.

Ready to see the difference a workflow-first foundation actually makes?

Schedule a Walk-Through and we'll even let a CSR from your agency drive. Not only do you get to experience a highly productive workflow driven system, you'll hear from the CSR 'how it felt' driving it.

How To Evaluate A Management System

How To Evaluate A Management System

Choosing an agency management system is one of the most important business decisions you’ll make.

After decades of helping agencies through this process, I can tell you there are smart, effective ways to evaluate a system—and there are poor approaches that almost guarantee a bad decision.

Rule #1: Show Me, Don’t Tell Me

The Importance of a Walk-Through

Let’s be blunt: sales reps often exaggerate what their system can do. Some even stretch the truth.

Example: One vendor advertises “downloading.” But in reality, it only drops a text file into the policy—it doesn’t update the policy. That forces staff to manually update records, which defeats the purpose of downloading altogether.

If you simply ask, “Does your system offer downloading?” the salesperson will say “yes.” Without a walk-through, you won’t realize the feature is nearly useless until it’s too late.

The solution: Insist on seeing the system in action. During a walk-through, have the rep show you exactly how to:

  • Add a client.
  • Add a policy (with full detail).
  • Enter a B-Tran/Invoice.
  • Send an email.
  • Process an endorsement or renewal.
  • See how you stay on top of work in process and open policy tasks.

Pay attention to the steps, clicks, and workflow. How much jumping around does it require? How streamlined is the process?

🔑 Bottom line: A product should sell itself when you see it in action. Without a walk-through, you can’t make a fair determination if CP Manager—or any system—is right for your agency.

Next Step: After a walk-through, if you're still not convinced, the natural next step is a Test Drive. This is where you get either a 7-day or 30-day login to CP Manager where you and your staff can dig in and give CP Manager a real test drive and experience it for yourself.

Once you’ve had a walk-through and you’ve seen how the system works, the smartest next step is to get hands-on. Unfortunately, most vendors don’t allow this — they stop at the demo. That’s why I recommend asking if a system offers a test drive. It’s the only way to know if the workflows truly fit your agency. With CP Manager, we make this possible through both a 7-day and a 30-day Test Drive. Few vendors are willing to do that, but it’s the most reliable way to avoid an expensive mistake.

We’re one of the only vendors that offer this:

  • 7-Day Test Drive ($67): Shared demo agency.
  • 30-Day Test Drive ($197): Full control of your own setup, fee credited if you purchase.

Learn more about our Test Drive program.

Rule #2: It’s Not About Price—It’s About Productivity

A system’s real cost isn’t the subscription fee—it’s how much time it consumes (or saves) for your staff.

A “cheaper” system that requires 10% more CSR hours will cost your agency far more than you save upfront.

Remember:
Increased Productivity = Increased Profitability.

When evaluating a system, focus on:

  • Double-entry: Does data flow seamlessly, or must staff retype information?
  • Workflows: How many steps does it take to process policy tasks? How does the system help staff stay on top of work?
  • Ease of use: Is the system intuitive, or does it create a steep learning curve and painful transition?

📘 Want to dig deeper? Read: What "Increasing Your Productivity" Really Means to Your Agency and The Big Savings with CP Manager.

Rule #3: It’s Not About Features—It’s Still About Productivity

One of the biggest mistakes agencies make when evaluating a management system is getting distracted by feature lists.

Vendors love to overwhelm prospects with long, impressive catalogs of functions and features. And when they demo the system to agencies, they spend most of the time showing features to "wow" the agency and very little time showing how the system will help them handle their day-to-day work.

But here’s the reality: After talking to many agencies on these bloated systems, most agencies only use 15–20% of those features. Those features they were so impressed with ultimately end up not being used. That's because, when the rubber hits the road, your day-to-day work and increased productivity are what really matter!

This also means they’re paying for a system full of things they don’t use and will likely never need or use.

And worse, all those extra bells and whistles often make the system harder to learn, harder to use, and slower for your staff. Instead of making your team more productive, bloated systems actually create drag.

The real question isn’t “Who has the most features?” The real question is:
👉 “Which system helps my staff get their work done faster and more accurately every single day?”

That’s why the smartest agencies focus on:

  • How the system handles core workflows (adding policies, renewals, endorsements).
  • How much double-entry there is.
  • How easy it is to train new staff.
  • How much time it actually saves per CSR per month.

Features don’t drive profitability. Productivity does.

An agency that saves 35 hours per CSR per month (a 20% productivity boost) will see a far bigger financial return than one that bought the system with the thickest feature catalog but increase the time for every task.

👉 Remember: Increased productivity equals increased profitability. That’s the true measure of a great system.

The CP Manager Review Process

We offer multiple ways to review CP Manager—many without ever speaking to an account manager. Some resources require sharing your information first. Why?

Because CP Manager is unique. It was built from over 30 years of industry experience, combining deep workflow knowledge, programming expertise, and an obsession with productivity. No other vendor has invested the time or money we have to create a true productivity-driven system. Protecting these innovations is essential.

When you do speak with an account manager, you’ll find we’re respectful and not pushy. Our goal is simple:

  • Learn what’s important to you.
  • Recommend the most efficient review path based on your timeline.
  • Help you decide confidently if CP Manager is the right fit.

👉 Let's have a discussion and talk about these 3 points. Let's determine if CP Manager is a good fit or isn't the right fit for your agency upfront to save both of us time.

CP Manager Will Unlock Your CSR’s Full Potential

CP Manager Will Unlock Your CSR's Full Potential

Every agency owner knows the truth: the CSR is the backbone of the agency.

They’re the ones juggling client calls, processing renewals, handling certificates, managing policy changes, and making sure every detail is accurate. When CSRs are efficient, clients are happier, producers are more productive, and the agency flourishes.

But here’s the problem: most management systems make life harder for CSRs. Clunky workflows, endless clicks, and double-entry create unnecessary stress and steal valuable time.

That’s why we built CP Manager. It’s not just another management system — it’s the productivity engine that unleashes your CSR’s full potential.

How CP Manager Transforms Your CSR’s Day

Here’s what your CSRs will gain when using the most productive, workflow-driven system on the market:

  • Built by experts who understand agencies. Designed by insurance automation consultants with 30 years of experience.

  • Productivity that pays. The most efficient system in the industry, giving CSRs time back while boosting output.

  • Streamlined client & policy management. Faster, easier service that strengthens client relationships.

  • Easy to learn, easy to use. A user-friendly design means new hires are productive in days, not months.

  • True single-entry. Eliminate redundant data entry, reduce errors, and get work done faster.

  • Hyperlinked navigation. Instantly jump to clients, policies, carriers, emails, and more with one click.

  • Quick record entry. Create new records with just 5 required fields so CSRs can focus on policy data.

  • Commercial & Personal Lines powerhouse. Commercial Lines was built first, making CP Manager the most efficient system for complex accounts.

  • Multi-entity support. Easily manage multiple agencies, locations, and clusters in one system.

  • Client & prospect management. Stay on top of X-dates and nurture valuable leads without missing a beat.

  • Re-engineered communication tools. Notes, Follow-Ups, Attachments, and Correspondence all streamlined and fully integrated.

  • Certificate management made easy. Send one or thousands — CP Manager makes it simple.

  • Insurance-specific accounting. Simplify financial management with a system built for the way agencies really work.

The Result: CSRs Who Love Their Jobs (and Clients Who Notice)

When your CSRs have a system that works with them instead of against them, something amazing happens:

  • They spend less time fighting the software.
  • They spend more time serving clients.
  • They feel less stress and more confidence in their work.

That leads to happier clients, stronger retention, more cross-selling opportunities, and ultimately — a more profitable agency.

There’s a reason agency staff love using CP Manager.

It makes their work easier, faster, and more rewarding — which makes your agency more successful.

Ready to see how CP Manager can transform your CSRs into productivity powerhouses? Schedule a Walk-Through Today!

+ Show More