Quotas vs. Production

The Quotas vs. Production KPI measures how effectively sales agents meet their sales targets. It compares what agents were expected to sell against what they actually sold, giving managers a clear read on team performance.

In insurance, there are two main types of sellers. Captive agents work exclusively for your organization and sell only your products. Non-captive agents work for a third party and sell policies across multiple companies, typically finding the best rate for clients. Both types need realistic quotas: targets that challenge without discouraging.

What is Quotas vs. Production?

Quotas vs. Production is a sales performance KPI that tracks the ratio of actual sales output to assigned targets. A high ratio means your agents are meeting or exceeding expectations. A low ratio signals that targets may be misaligned, agents may need support, or both.

Why Quotas vs. Production matters

Knowing whether your team is hitting targets is the starting point for every sales decision: who to develop, where to reallocate resources, and whether your targets reflect market reality.

Without this metric, you're managing by instinct. With it, you can spot underperformance early, adjust quotas before morale suffers, and reward the agents who are actually driving results.

A few things this KPI helps you answer:

• Are quotas realistic? If most agents are consistently missing targets, the problem may be the target, not the team.
• Who needs support? Agents falling well below quota are easy to identify and coach before the gap becomes a retention issue.
• Where is production concentrated? If a small number of agents are hitting quota while others lag, you have a distribution problem worth addressing.

How to calculate Quotas vs. Production

The formula is straightforward:

Quotas vs. Production (%) = (Actual Production / Quota) × 100

Example: An agent has a monthly quota of 20 policies. They close 17.

(17 / 20) × 100 = 85%

That agent is at 85% of quota for the month. Tracked over time, this number tells you whether performance is improving, plateauing, or declining.

Captive vs. non-captive agents

The context around quota-setting differs depending on agent type.

Captive agents sell only your products, so their quotas can be tied directly to your product mix, pricing, and sales cycle. You have more control over the inputs, which makes it easier to set accurate targets.

Non-captive agents represent multiple carriers. Their production reflects a choice: they're directing business to you instead of a competitor. Quotas for non-captive agents need to account for that competitive dynamic, and targets should reflect a realistic share of their total book, not just an internal number.

What a good Quotas vs. Production ratio looks like

There is no universal benchmark. The right ratio depends on your market, product complexity, and agent experience. That said, a few general principles apply:

• Consistently above 100% may indicate quotas are too low and not stretching the team.
• Around 80% to 100% is typically a healthy range: agents are being challenged and most are succeeding.
• Below 70% across the team warrants a closer look at whether targets are realistic, whether agents have the tools and training they need, or whether market conditions have shifted.

Track this metric by agent, by team, and by channel (captive vs. non-captive) to get a useful picture rather than a single blended number.

Tracking Quotas vs. Production on a dashboard

Pasting production numbers into a spreadsheet each week, or explaining your sales context to a generic AI tool every time you want a quick answer, is not a sustainable way to manage a team.

A dashboard that pulls agent production data automatically and compares it against assigned quotas in real time means you know where things stand without having to go looking. When managers and agents see the same numbers, conversations about performance become faster and more grounded.

Klipfolio connects to your CRM and other data sources to keep Quotas vs. Production current automatically, so you can focus on coaching and decisions rather than data assembly.