What makes a sales goal SMART?
A SMART sales goal states a specific result, a way to measure it and a deadline. It also needs a credible basis for being achievable and a clear reason it matters. Writing a precise target does not make the target realistic.
Use the five criteria as questions. What exactly should change? How will the team measure it? What evidence supports the target? Which business need does it serve? When is the result due?
The SMART sales goals examples below are fictional. Their figures illustrate how to write and review a goal; they are not benchmarks. Replace them with targets based on your own accounts, resources and sales cycle.
Example: grow revenue from existing customers
“By the end of next quarter, increase monthly recurring revenue from the named existing-customer portfolio from $100,000 to $110,000. The account-management lead owns the result and reviews progress monthly.”
This is a 10% increase from the stated baseline. Define whether the measure includes expansion, contraction and churn. If it excludes losses, label it as gross expansion revenue rather than the portfolio’s net growth.
Before accepting the target, inspect the accounts with a plausible expansion need. Identify the product fit, buyer decision and timing for each. An aspiration to grow by 10% is not evidence that the available opportunities support it.
Example: acquire new customers in a defined segment
“By the end of the next two quarters, win six new customers in the named mid-market account segment. Count a win when both parties sign the agreed contract, and report credited wins at each monthly review.”
Name the segment and account list in the working plan. Define how subsidiaries, reactivated customers and duplicate account records are treated. Those rules prevent different teams from counting the same outcome differently.
Test the target against current opportunities, capacity and the time buyers need to decide. If the team lacks enough plausible opportunities, record the gap and the work needed to address it. Do not assume a higher call target will close that gap on its own.
Example: reduce a specific sales-process delay
“During next quarter, reduce the median internal approval time for eligible mid-market proposals from five working days to three. Sales operations will report approval time weekly using the agreed submission and approval timestamps.”
This goal targets a delay the team can inspect and influence. Define a complete submission and record returns for missing information. Otherwise people could improve the measured time by delaying when they start the clock.
Check proposal errors and rework alongside speed. Faster approval is not useful if it sends inaccurate terms to customers. Keep the same eligibility rules when comparing the baseline with the new period.
Example: improve customer retention
“For the next renewal cohort, retain 92 of the 100 accounts due to renew, compared with 88 of 100 in the baseline cohort. The customer-success lead will review account risks monthly and report the final result after the renewal window closes.”
This raises account retention from 88% to 92%, an increase of four percentage points. It is not the same as a 4% relative increase. State whether you measure retained accounts or retained revenue; a large lost account affects those measures differently.
Compare cohorts with care. Differences in account size, contract terms and product fit can affect the result. Assign actions to the identified renewal risks instead of treating every account as if it needed the same outreach.
Connect activity targets to outcomes without promising certainty
Activity goals help organise work, but an activity count is not proof of progress. “Complete ten discovery meetings” needs a definition of a completed meeting and a check on whether it produced useful qualification evidence.
In a fictional planning model, a 20% opportunity win rate suggests that ten wins would require about fifty comparable opportunities. That is an estimate based on an assumption, not a guarantee. The opportunities may differ from the historical sample, and some may close outside the planning period.
Record the assumed conversion rate and sales cycle. Review them as evidence changes. Avoid turning a chain of estimated conversions into a claim that a certain number of calls will inevitably produce a revenue result.
Give each goal an owner and a review process
Keep a short working record for each goal:
- The result, baseline, target and deadline.
- The eligible accounts or transactions and calculation rules.
- The accountable owner and source of the data.
- The resources and assumptions needed to make the target credible.
- Review dates and any quality measures that must not deteriorate.
A CRM report may provide the data, but check that the fields actually match the goal’s definition. Assign someone to resolve missing or inconsistent records before interpreting the numbers.
At each review, discuss what changed and what support is needed. If a target or definition changes, retain the original and record why the revision was approved. Moving the target silently makes later comparisons unreliable.
Use the review to decide what to do next
When progress falls short, inspect the cause before increasing activity expectations. The team may need better account selection, a clearer approval process or help with a particular selling skill. A missed goal does not identify the remedy.
For revenue targets, keep actual results separate from expected future deals. The quota attainment guide explains how to report progress against a target without confusing it with the forecast.
If your goals repeatedly expose unclear qualification or inconsistent pipeline reviews, bring those examples to a discussion with The Sales Arc. They give the process review a specific problem to address.
