How to Set Sales Quotas With No Historical Data

Setting quota from attainment history is straightforward. Setting it for a team that has never sold anything is a modeling exercise with no answer key, and the usual response is to divide the revenue target by headcount and call it a plan. That produces a number with no relationship to what a rep can physically do in a quarter.

The method below replaces missing history with capacity math and a documented assumption set.

What replaces historical attainment?

Selling capacity, which is a physical constraint you can estimate without any closed-won data.

A rep has a fixed number of selling weeks per year after holidays, training, and pipeline reviews. They can hold a bounded number of active opportunities at once before quality drops. Each opportunity takes a knowable amount of time to work. Those constraints exist before you sell anything.

Capacity math gives you a ceiling. Assumption-driven conversion math turns the ceiling into a revenue number:

Annual quota = (opportunities a rep can run per period x periods per year) x win rate x average deal size

The output is only as good as the inputs, which is exactly why each input needs to be written down with its source and a date for replacement.

How do you build the assumption set?

List every input, name where the number came from, and mark it for replacement with your own data. The discipline that matters is the third column. A first-year quota model is a set of hypotheses. Teams get into trouble when the placeholders quietly become permanent and nobody remembers that the win rate in the model was somebody's guess in month two.

Watch the deal size input in particular. Pipeline average deal size and closed-won average deal size diverge, sometimes sharply. A pipeline carrying an $80,000 average while closed-won deals land at $40,000 will produce a quota model with double the revenue capacity the business actually has.

What quota should the first sales hire carry?

Below what the capacity model produces, because their first two quarters are process construction rather than selling.

The first quota-carrying hire in a company does work that never appears in a capacity model. They find out which objection actually kills deals, which title has budget, whether the pricing survives procurement, and how long legal review really takes. That work has enormous value and it consumes selling weeks.

Two practical adjustments:

- Reduce available selling weeks for the first two quarters rather than reducing the deal math, because the constraint is time, not conversion. - Set explicit non-revenue deliverables alongside the quota, such as a documented qualification standard and a completed win-loss review of the first cohort of deals.

Do not solve this by setting a trivially low quota. A quota nobody can miss teaches nothing about capacity and gives you no information for the second hire's plan.

How much buffer belongs between aggregate quota and the revenue target?

Some, stated explicitly, and sized as a decision you can defend rather than a percentage you copied.

Aggregate quota across the team should exceed the company revenue target. The gap absorbs reps who leave mid-year, reps who never ramp, and the ordinary fact that a team does not produce at exactly 100 percent of plan.

With no attainment history you cannot size that gap from your own distribution. What you can do is make it visible. Write the revenue target, the aggregate quota, and the implied buffer in the same document, and put the reasoning next to it. When the first real attainment spread arrives, the buffer becomes the first thing you correct.

How do you check the quota against pipeline reality?

Convert the quota into required pipeline and ask whether your demand engine can produce it.

A quota is a claim about pipeline as much as a claim about selling. Multiply the quota by the coverage ratio your model implies and compare it against what marketing and outbound can realistically create in the period. If the answer requires triple the pipeline your current motion produces, the quota is fiction regardless of how careful the capacity math was.

Across ORM's customer base, pipeline coverage runs from roughly 1.4x to 5x, with most companies sitting near 3.5x and 3x to 5x treated as the standard range. Use that as a sanity check on your own required coverage, then read why the 3x coverage rule is wrong before you rely on it as a planning constant. Coverage tells you about volume and says nothing about composition, and a new team's pipeline composition is usually worse than the average because qualification standards have not been set yet.

One more calibration point from ORM data: of the pipeline carrying close dates inside the quarter on day one of the quarter, about 20 percent actually closes in that quarter. A first-year plan that assumes day-one pipeline converts at a much higher rate will miss on timing even when the annual math holds.

When do you re-set the quota?

Review the assumptions every quarter and re-baseline at the period boundary, never in the middle of one.

The trigger for re-baselining is data volume, not calendar time. Once you have enough closed deals in a segment to compute an actual win rate and an actual cycle length, replace the placeholders and rerun the model. Expect the first correction to be large. That is the model working, not failing.

Two rules keep the process from destroying trust:

1. Quota changes take effect at the start of a period, with the new number communicated before the period opens. 2. When a quota moves, state which input changed and by how much. Reps accept a higher number tied to a measured win rate improvement. They do not accept a higher number that appeared without explanation.

Forecasts fail most often when the model still runs on assumptions the business has already outgrown. A first-year quota model is made entirely of those assumptions, so the review cadence matters more than the initial precision. Feed each corrected input into how you build the forecast as well, because the same numbers drive both.