# OKRs for a small sales team: key results you can pull straight from your CRM

https://salesbond.app/blog/okrs-sales-team-owner-key-results-from-crm-data/
Published: 2026-10-31 · Updated: 2026-11-13

OKRs (objectives and key results) are a goal-setting framework: one objective, and a few measurable key results that show whether you reached it. For a sales team, each key result should be a number you can read from your CRM, such as closed-won revenue or win rate. A typical sales OKR pairs the objective “Stop losing deals after the proposal” with a key result such as a higher proposal-to-won conversion by quarter end.

## OKRs in plain words, and OKR vs KPI vs quota

The objective is a sentence about where we want to be at quarter end, often taken from a [vision statement for a small business owner](https://salesbond.app/blog/vision-statement-small-business-owner-sales-team/) written in a few plain lines. The key results are the numbers that prove we got there, each with a start value and a target. The usual count is three to five key results per objective, and Cora Systems suggests one objective per team per quarter, with key results that measure “the value created, not the activity performed” ( [Wikipedia: Objectives and key results](https://en.wikipedia.org/wiki/Objectives_and_key_results); [Cora Systems: What are OKRs](https://corasystems.com/blog/what-are-okrs)).

Andrew Grove popularised it at Intel in the 1970s and described it in *High Output Management* in 1983. John Doerr, then an Intel salesperson, took Grove’s course in 1975, when it was still called iMBO, and later brought it to Google. So the idea reached Google through someone who started out in sales.

A quota is one rep’s number for the period, agreed in advance and usually tied to pay; we took it apart next to target and forecast in [sales quota vs target vs goal vs forecast](https://salesbond.app/blog/sales-quota-vs-target-vs-goal-vs-forecast-owner/). The quota answers “did you sell enough”, while an OKR asks whether the team changed the thing it said it would change, and the useful one targets whatever makes quota hard this quarter, like a leaking proposal stage.

Both are numbers, so KPIs and OKRs get mixed up. Mailchimp separates them like this: OKRs are overarching goals with measurable milestones, KPIs are standalone metrics for evaluating performance, and some businesses use KPIs as key results ( [Mailchimp: OKRs](https://mailchimp.com/resources/okrs/)). Win rate is a KPI you glance at every quarter. “Raise win rate from 24% to 30% by June 30” is a key result, because this quarter you decided to move it. The plain definition of a KPI, with examples from a small sales team, is in [what a KPI is](https://salesbond.app/blog/what-is-a-kpi/) for a small business owner.

## One objective, three key results: the shape for a sales team

We use three for a team under ten people. Five key results on a five-person team means each rep carries a different one and nobody carries the objective.

- The objective is a sentence a rep would say out loud: “Stop losing deals after the proposal.”
- Key result 1 is the money number, closed-won revenue or revenue from one segment.
- Key result 2 covers pipeline: qualified deals created, or coverage for next quarter.
- Key result 3 is about quality. A stage conversion, win rate or cycle length.

Every key result gets a start value, a target, the CRM report it is read from, and one owner, a named person. No report, no key result.

Mailchimp sorts OKRs into aspirational, committed and learning ( [Mailchimp: OKRs](https://mailchimp.com/resources/okrs/)). In plain terms: a committed key result is expected to land at 1.0, an aspirational one is a stretch where 0.7 already counts as good, and a learning one is about finding something out rather than moving a number. We label each key result, not the set, because the label decides how you read its score. Revenue is almost always committed. A conversion jump is usually aspirational. One learning key result per quarter is fine, as long as the other two are numbers.

![Table of six sales key results, the CRM filter each is read from, and how often to check it; every filter depends on a date field](https://salesbond.app/wp-content/uploads/2026/10/okrs-sales-team-owner-key-results-from-crm-data-2.png)

## OKR examples for a sales team: new business, pipeline, win rate

The team here has five reps and a quarterly target of $600,000. The numbers are illustrative.

**New business.** Objective: make new logos the main course this quarter.

1. Closed-won revenue from new customers, from $190,000 last quarter to $310,000. Committed. Won deals, won date in quarter, customer type = new.
2. Qualified new-business deals created, from 40 to 60. Committed. Same filter, on deals entering Qualified.
3. Proposal-to-won conversion on new business, from 25% to 35%. Aspirational, read from stage history.

**Pipeline coverage.** Objective: enter next quarter with a pipeline that can carry the target without a heroic last month.

1. Weighted pipeline with a close date in next quarter, from $650,000 to $1,200,000 on the last day of this quarter. Committed.
2. Share of the quarter’s new deals created in month one, from 25% to 40%. Aspirational.
3. Average age of open deals sitting in Qualified, from 35 days to 20, measured from the stage-change date to today. Committed.

**Win rate.** Objective: lose earlier or win more, but stop losing at the end.

1. Win rate, from 24% to 30%. Aspirational.
2. Deals lost at the negotiation stage, from 18 last quarter to 8. Committed. Lost deals whose last stage was Negotiation.
3. A loss reason on every lost deal, and one review of those reasons by week six. Learning.

None of the nine counts calls, since calls are the work a rep does to move one of them.

## Key results that come straight from CRM fields

The test: can a manager open the CRM on Monday and read the current value in a minute, with no spreadsheet in between? These six pass.

- Closed-won revenue. Deals with status Won and a won date inside the quarter, summed by value. Read it weekly.
- Qualified deals created. Count the deals that entered your first post-discovery stage with a create date inside the quarter, also weekly.
- Stage conversion, say proposal to won: won deals that passed the proposal stage divided by all deals that left that stage in the period. This one needs stage history, and every two weeks is often enough.
- Win rate is won divided by won plus lost, by close date. Monthly.
- Pipeline coverage for next quarter. Open weighted pipeline with a close date next quarter, divided by next quarter’s target; check it every Monday.
- Average sales cycle: won date minus create date, averaged over the deals won in the period, read once a month.

Every line depends on a date field: won date, create date, stage-change date. If reps mark deals Won a week after the contract is signed, the won-date filter moves March revenue into April and the key result lies in both months. Fix that habit in week one.

Where your CRM has a goals feature, the first two lines fit it well; we wrote up the setup for [HubSpot goals](https://salesbond.app/blog/hubspot-goals-rep-targets/) and [Pipedrive goals](https://salesbond.app/blog/pipedrive-goals-monthly-targets/). The CRM goal holds the target, the OKR records why that target matters this quarter, and both belong on the same page as the [six numbers the sales plan is built from](https://salesbond.app/blog/sales-plan-one-page-small-team-numbers-from-crm/). The targets themselves come from the [strategic plan for a sales team](https://salesbond.app/blog/strategic-plan-sales-team-owner-one-page-targets-crm-evidence/), one page with the CRM evidence next to each target, and [goal setting for a small business owner](https://salesbond.app/blog/goal-setting-small-business-owner/) covers how to pick them so the people who carry them accept them.

## The Monday check, and when to change course

Monday, fifteen minutes, three numbers against a straight line. In week five of thirteen, a committed revenue key result should be about five thirteenths of the way from start to target. Pipeline key results aren’t linear, so draw the line you expect.

We change the actions when a key result is off pace for two weeks in a row and we can name why. A single bad week changes nothing. After two weeks with a named reason, pick the action, such as moving a rep onto new business, cutting discount approval time or running the loss-reason review in week four instead of six.

The key result itself stays put mid-quarter, with one exception: its data source turns out to be wrong. If you find in week three that half the team never used the Negotiation stage, “deals lost at negotiation” is measuring stage usage. Rewrite it, say so in the the notes and keep going.

Most of these numbers are already tiles on a [CRM dashboard for the owner](https://salesbond.app/blog/crm-dashboard-owner-head-of-sales-tiles-and-fields/). The OKR check is the same tiles with a target drawn on them. In SalesBond, Sales Plan puts the target next to the forecast and the gap for the period, so the revenue key result can be read there without a separate sheet.

## Common mistakes (activity as result, no data source, quota in disguise)

The most common one is activity dressed up as a result. “Send 60 proposals” is a task; the result is how many of them became customers. The honest version is “proposal-to-won conversion from 25% to 35%”.

Then there’s the key result with no named report. “Improve pipeline quality” measures nothing. If nobody can open the CRM and point at the number the quarter ends with a conversation about what the words meant.

The third is a quota in disguise. If the objective is “hit $600,000” and the three key results are each rep’s share of it, the OKR only repeats the comp plan. The OKR is for the thing that would make the quota easier next time, which is why none of our three sets is the target itself.

## Scoring at quarter end: what a good OKR score looks like

Each key result is scored from 0.0 to 1.0, where 1.0 means the target was reached; 0.7 is the normal aim for an aspirational key result and 1.0 for a committed one ( [Wikipedia: Objectives and key results](https://en.wikipedia.org/wiki/Objectives_and_key_results)). Cora Systems treats 0.7 to 0.8 as a successful stretch ( [Cora Systems: What are OKRs](https://corasystems.com/blog/what-are-okrs)). Count progress from the start value.

Take the new-business set. Revenue went from $190,000 to $280,000 against a target of $310,000: $90,000 of a $120,000 climb, so 0.75. It was committed, so 0.75 is a miss. Proposal-to-won conversion went from 25% to 32% against 35%, which is 0.7. Aspirational, so a good quarter on that line. The two scores are nearly equal and read in opposite directions, which is why the label goes on each key result.

We score each line and don’t average them. An average of 0.9, 0.3 and 0.9 is 0.7 and hides which lever moved. So “what is a good OKR score” has two answers: 1.0 on committed, around 0.7 on aspirational. If every line comes in at 1.0 two quarters running, the targets were too soft.

Then write next quarter’s objective from what teh scores say. If conversion moved and revenue did not, the problem sits upstream of the proposal, and that is the sentence at the top of the next page.
