How Do I Motivate Reps to Sell More Than the Core Product?

The job this scorecard is hired to do

The problem almost never looks like a motivation problem when it lands on your desk. It looks like a mix problem. Attach rate is flat. The second module hasn't moved in two quarters. Service plans sit at 11% penetration while the flagship SKU sells itself. Leadership responds with a spiff, a contest, a Monday huddle, a slide deck about "consultative selling" — and the mix doesn't budge. Six weeks later everybody agrees the reps just aren't hungry.

They're plenty hungry. They're sprinting toward the one number you chose to publish. If gross revenue is the only figure on the wall, a rep does the arithmetic in about four seconds: the fastest path to that number is the product they can close in a single call with no objection handling, no discovery detour, and no risk of stalling the deal. Every add-on they raise is a chance to lengthen the cycle and lose the whole thing. Selling the full line is *rationally* worse for them under a single-line quota. No amount of encouragement out-pulls that math.

So the job the weighted scorecard is hired to do is narrow and mechanical: change what gets counted so the rational move and the desired move are the same move. That's it. It isn't a culture program. It isn't a values exercise. It's an instrument that makes the full book of business legible in one number, and then puts real consequences behind that number.

Concretely, the instrument has to do four things. It has to inventory every line a complete rep is supposed to move — in most orgs that's eight or nine lines, not one. It has to weight those lines so leadership's priorities are explicit rather than implied. It has to grade each rep on each line on a simple scale, typically 1-to-5, so gaps are visible at a glance rather than buried in a report. And it has to roll up into a single composite that a rep can watch move.

The arithmetic is deliberately boring: composite = the sum of (weight × level) across every KPI. Picture a rep who is a flawless level 5 on the core product and a level 1 on everything else. Under a revenue quota, that rep is a hero. Under the composite, the score collapses — and because the composite is what stands between them and the largest paycheck available, the rep feels a steady, self-generated pull toward the empty lines. Nobody had to nag. The number did it.

Two failure modes are worth naming up front, because they kill more rollouts than anything else. The first is a hidden matrix. If reps can't see their own levels and the exact distance to the next one, the scorecard is just a management report and it changes nothing on the floor. Publish it. The second is a decorative matrix — one that gets calculated and displayed but never touches pay or promotion. Reps read that immediately as theater and go right back to the easy SKU. The composite has to have teeth, and the teeth are money, territory, or advancement.

How it fits the RevOps stack

The scorecard isn't a standalone tool so much as a layer that sits between systems you already run. RevOps owns the plumbing, and the plumbing determines whether the composite is trustworthy enough to pay on.

Upstream, the raw lines come from wherever the transaction actually lands. The CRM gives you deal-level product mix, close rates, and activity. The billing or ERP system gives you what was truly invoiced — which is not always what the opportunity record claimed. The customer success platform gives you retention, renewal, and expansion. If your attach or service-plan data lives in a POS or an order system rather than the CRM, that's a real integration item, not a footnote: a KPI you can't pull cleanly is a KPI you'll end up maintaining by hand, and hand-maintained lines go stale within a month.

Midstream sits the scorecard itself — the weighting engine and the roll-up. This can be a spreadsheet, a purpose-built scorecard product, or a set of custom CRM dashboards. The important design decision here isn't the software, it's who owns the weights. Weights should be a RevOps-administered configuration that sales leadership sets and can change quickly, not something hard-coded into a report that takes a two-week ticket to modify. The whole value of the instrument is that when a supplier renegotiates terms, a line gets discontinued, or demand shifts, you re-weight and the entire floor re-aims by the next shift.

Downstream, the composite feeds three consumers. It feeds compensation — either through a commission platform that pays multi-component plans, or through a simpler modifier on the existing plan. It feeds coaching, because a manager can now open a rep's matrix, point at the lowest weighted line, and build a specific one-rep plan instead of saying "sell more." And it feeds visibility — leaderboards, dashboards, recognition rituals — which is what keeps the composite in a rep's field of view daily rather than surfacing once a quarter in a review.

There's a fourth consumer that gets overlooked: forecasting and planning. Once you're grading product mix per rep, you can see structurally which lines are under-sold across the whole team versus under-sold by three specific people. That's a completely different intervention. Team-wide weakness on a line usually means an enablement or packaging problem — the pitch doesn't work, the pricing is wrong, the objection isn't answerable. Individual weakness means coaching. Conflating those two wastes an enormous amount of effort, and the matrix separates them for free.

One caution on scope: resist the urge to make the scorecard the system of record for anything. It's a read-and-roll-up layer. The moment reps start disputing the composite because the underlying CRM data is wrong, you've inherited a data-quality project, and the motivation program stalls while you clean it up. Audit the source lines *before* you attach money to them.

Building the matrix: KPIs, weights, and levels

Start with the inventory, and be exhaustive before you're selective. Write down every line a fully-formed rep is supposed to move. For a hardware or retail floor, that typically looks like: core product units, high-margin add-ons, accessories or attach, service and protection plans, financing or payment products, trade-ins, retention or churn saves, and raw activity or traffic conversion. For a SaaS team: new logo ARR on the primary product, second-module attach, seat expansion, multi-year commitment rate, gross retention on the book, pipeline generated, and discount discipline. For professional services: project revenue, retainer conversion, utilization, scope expansion, referenceability, and renewal.

The list will come out somewhere between six and ten lines. That range matters. Below about five lines you haven't described the job — you've described a slightly wider version of the same single-product quota. Above about ten, the weights get so thin that moving any individual line barely registers in the composite, and reps stop being able to hold the model in their heads. Eight is a comfortable center of gravity for most teams. Small teams with a narrow catalog can run five or six perfectly well.

Then weight. This is the step where leadership has to be honest, and it's usually the most uncomfortable meeting in the rollout, because weights are strategy stated numerically. If the core product carries 40% of the weight, you have said out loud that it is 40% of the job — no more. Some patterns that hold up in practice: keep the core product meaningful but never dominant, because a core weight above roughly half re-creates the original problem. Give the strategically under-sold line more weight than its current revenue contribution justifies — the weight is a *steering* signal, not a mirror of last year. And keep retention or churn-save weighted somewhere in the mix even on a pure new-business team, because otherwise you've just built a faster machine for selling to customers who leave.

Levels are the simplest part and the one people over-engineer. A 1-to-5 scale against defined thresholds is enough. Level 3 should be "meets the standard for this role" — the honest expectation, not a stretch. Level 5 should be genuinely rare and reserved for top-decile performance on that line. Write the thresholds down. "Level 4 on service plans = 28-35% attach" is a coachable target; "level 4 = strong" is an argument waiting to happen. Publish the thresholds alongside the matrix so nobody has to ask their manager what the bar is.

A worked example makes the pull obvious. Say core product carries weight 5, add-ons 4, attach 3, service plans 3, retention 3, and activity 2 — twenty weight points total, so a perfect composite is 100. A rep at level 5 on core and level 1 everywhere else posts 25 + 4 + 3 + 3 + 3 + 2 = 40. A rep at level 3 straight across posts 60. The single-product specialist, who looks like the top performer on the revenue report, is a full third behind the balanced rep on the instrument that now determines pay. That gap is the entire mechanism, and it's why the composite has to be published: the specialist needs to *see* that 40 and be able to compute exactly which line moves it fastest.

One refinement worth adding once the basic matrix is stable: a floor condition on one or two non-negotiable lines. If retention below a certain level zeroes out the accelerator regardless of composite, you've closed the loophole where a rep buys a high composite with churn-heavy volume. Use floors sparingly — one or two, on lines where a bad outcome is genuinely unacceptable — because a matrix full of gates stops being a scorecard and becomes a compliance checklist.

Attaching teeth: compensation, coaching, and recognition

A composite with no consequence is a dashboard. Three levers turn it into a motivator, and most teams need at least two of them.

Compensation is the strongest lever and the slowest to change. There are two broad approaches. The first is a multi-component plan that pays different rates on different lines — core at one rate, add-ons at a higher rate, service plans at a higher rate still. This is direct and reps understand it instantly, but it can get complicated to administer and it doesn't inherently reward balance; a rep can still ignore a line entirely if the rate on their favorite line is high enough. The second approach is a composite modifier: keep the underlying commission structure, but multiply the payout or the accelerator by a factor tied to the composite score. A rep at composite 40 earns at a reduced rate; a rep at 75 earns an accelerator. This rewards balance directly rather than just repricing individual lines, and it's usually simpler to administer.

Whichever you choose, respect the practical constraints. Comp plan changes generally take effect at a plan-period boundary, not mid-quarter, and they usually need finance and sometimes legal review. Model the new plan against the last two quarters of actual data before you ship it — you're looking for reps whose earnings would swing dramatically, because those are the conversations you'll have to have personally, and you want to have them prepared. And give the team a transition period: run the composite visibly for at least one full quarter before it affects pay. Reps need to watch their own number move under the new rules before those rules touch their income, or the rollout reads as a pay cut in disguise.

Coaching is the fastest lever and the most under-used. The matrix hands managers something they've never reliably had: a specific, per-rep, next-best-action. Instead of a generic pipeline review, a one-on-one starts at the lowest weighted line on that rep's matrix. "Your service-plan line is a 2. Everything else is a 4. Moving that one line is worth more to your composite than improving anything you're already good at." That's a concrete, achievable, non-insulting conversation, and it converts far better than a blanket demand to sell more.

Go one level deeper on diagnosis before you build the plan, because a low line has at least three distinct causes and they need three different fixes. The rep might never raise the product at all — that's a call-structure problem, fixed with a mandatory discovery question or a checklist. The rep might raise it and lose the objection — that's an enablement problem, fixed with objection scripts and role-play. Or the rep might raise it, handle the objection, and still lose because the offer genuinely isn't competitive — that's a product or pricing problem, and coaching the rep harder is unfair and useless. Conversation-intelligence tooling helps here if you have it, but a manager sitting through three calls tells you the same thing for free.

Recognition is the cheapest lever and the one that fades fastest. Leaderboards, floor displays, Slack callouts, and public celebration of full-line wins do move behavior, especially on floors that already run on visible competition. The critical detail is *what you recognize*. If the leaderboard still ranks by revenue, it's actively fighting the composite. Rank by composite, or run a leaderboard on the specific under-sold line you're trying to move. Recognition works best as a short campaign layered on top of a permanent scorecard — a four-week push on the second module, publicly tracked — rather than as the permanent mechanism.

Rollout, cadence, and the objections you'll hear

Sequence the rollout so trust builds before stakes do. A workable order: build the matrix and validate the data sources privately for two to four weeks; publish the matrix and every rep's current levels with no pay implications for one full quarter; then attach the composite to comp at the next plan boundary. Rushing straight to pay is the single most common rollout mistake, and it converts a fair instrument into a perceived ambush.

On cadence: weights change quarterly by default, with the explicit right to change overnight when something material happens — a supplier rewrites terms, a line gets discontinued, demand shifts hard. The rule that matters is announcing new weights the moment they change, with a one-line reason. Reps tolerate a moving target far better than a silent one. What to avoid is weekly fiddling, which reads as noise and erodes trust in the whole instrument; if reps can't predict what's being asked of them, they revert to the safest behavior, which is the core product.

Levels re-grade monthly. Frequent enough that improvement is visible and worth chasing, infrequent enough that a single bad week doesn't tank someone's number. Pair the re-grade with the one-on-one so the rep sees the movement and the coaching conversation in the same sitting.

Now the objections, because they're predictable and they're mostly reasonable.

*"This is just a way to pay us less."* It can be, if you build it that way. The honest answer is to model the plan so a balanced rep at the same total revenue earns the same or more than before — you're redistributing earning opportunity toward the full book, not shrinking the pool. If the plan genuinely reduces total comp, say so plainly rather than dressing it as a motivation program; reps will figure it out within one cycle either way.

*"My territory can't sell that line."* Sometimes true, and worth checking before you dismiss it. Enterprise-heavy patches, rural territories, and certain verticals genuinely have different mix potential. The fix is territory-adjusted thresholds on the affected lines — not different weights, which would fragment the strategy, but different level definitions. If a 20% attach is top-decile in one segment and mediocre in another, the thresholds should say so.

*"I'm the top revenue producer and now I look average."* This is the specialist confronting the 40-versus-60 gap, and it's the conversation that decides whether the rollout survives. Handle it individually and early. The framing that works: nothing about their core performance is being devalued — level 5 on core is still the highest score available on the heaviest-weighted line. What's changed is that the rest of the job is now visible too, and it's the fastest available path to a bigger check for them specifically, because they have more headroom on the empty lines than anyone else has on the full ones.

*"Too many numbers."* Legitimate if you shipped ten KPIs with unwritten thresholds. Cut to six, write the thresholds, publish one page. If a rep can't explain their own composite from memory after two weeks, the matrix is too complex, and that's your problem to fix, not theirs.

Where this pattern travels: adjacent use cases

The mechanic generalizes further than most people expect, and seeing the adjacent applications usually helps clarify the core one.

Services and consulting. Nothing about the model requires a SKU. Swap product rows for service categories — advisory, implementation, support, training — or for behaviors like scope expansion and referenceability. A services bench that only sells project work and never converts a retainer has exactly the single-product problem in a different costume, and the same weighted composite pulls the retainer line forward.

Customer success and account management. CS teams face the mirror-image version: they're graded on retention alone, so expansion never happens. Weight renewal heavily, but put real weight on expansion, multi-product adoption, and reference generation, and the CSM stops treating an upsell conversation as a risk to the renewal.

Partner and channel programs. Channel partners are the extreme case of the core-product trap, because they have their own catalog competing for attention and no manager on your side of the table. A partner scorecard — weighted across certified headcount, mix breadth, deal registration hygiene, and renewal rate — with tier benefits attached to the composite is the same instrument applied to a population you can't coach directly. The weights do all the work precisely because coaching isn't available.

Multi-unit retail and field operations. Store-level or district-level scorecards weighting attach, service plans, labor efficiency, and customer satisfaction run on identical logic, and they're where a lot of RevOps teams first encounter the pattern. The instructive part is what happens when weights get set carelessly: weight labor efficiency too heavily and stores under-staff peak hours to protect the number, which kills attach and satisfaction two lines over. Composite scorecards make trade-offs explicit, which means badly chosen weights produce clearly wrong behavior — fast. That's a feature. You find out you were wrong in weeks rather than at the end of the year.

Marketing and demand gen. Weighted scorecards across MQL volume, pipeline sourced, pipeline influenced, and conversion quality solve the analogous problem where a team optimizes the one metric it's judged on — usually volume — at the expense of everything downstream.

The through-line across all of these: whenever a team has more than one thing to do and exactly one thing gets measured, the unmeasured work stops happening. That's not a character flaw in reps, CSMs, partners, or store managers. It's a predictable response to an incomplete instrument, and the fix is always the same shape — measure the whole job, weight it deliberately, publish it, and attach consequences. Motivation, in this frame, is a measurement problem before it is a money problem, and it's a money problem before it's a morale problem.

Related questions

How many KPIs should be on the scorecard?

Six to ten for most teams, with eight as a comfortable center. Fewer than five doesn't describe the job. More than ten makes each weight so thin that moving a line barely registers, and reps lose the ability to hold their own model in their heads.

Can I run this without changing the comp plan?

Partially. Publishing the matrix and running coaching off the weakest line moves behavior on its own, and it's a good first quarter. But if the largest paycheck still comes from the single line, the pull back to the core product eventually wins. Comp is the durable lever.

How do I keep reps from gaming the composite?

Define levels against outcome thresholds rather than activity counts wherever possible, and add a floor condition on one or two non-negotiable lines — typically retention or churn. Audit a sample of graded lines each cycle. Gaming usually reveals a badly specified threshold, not a bad rep.

Does this work for a three-person sales team?

Yes, and often faster, because there's nowhere to hide. Trim to five or six KPIs to match a leaner catalog. The composite still resolves each person to one unambiguous number, and the full mix stays visible to everyone in the room.

What if the under-sold product is genuinely bad?

Then the matrix tells you that quickly, which is the point. If the line is weak across the entire team rather than for three specific reps, it's a packaging, pricing, or competitive problem. Fix the offer before you weight it heavily — otherwise you're paying people to fail.

FAQ

How long before this changes behavior on the floor?

Expect visible movement on the weakest lines within four to eight weeks of publishing the matrix, and more durable change one full quarter after comp is attached. The first cycle is mostly reps orienting to the new number. The second is where habit shifts. If nothing has moved after two cycles with pay attached, the usual culprits are a composite reps can't see daily, weights too close to uniform to signal a priority, or thresholds so far out of reach that improvement feels pointless.

Should the composite be public across the whole team, or private per rep?

Publish the matrix structure, the weights, and the thresholds to everyone — that part is non-negotiable, because secret rules feel arbitrary. Individual composites are a judgment call. Fully public rankings work well on floors that thrive on competition and poorly on teams with wide tenure gaps, where the bottom of the board demoralizes rather than motivates. A reasonable middle: publish team distribution and each rep's own number privately, with voluntary opt-in leaderboards for specific campaigns.

What data do I actually need before I can start?

Per-rep, per-line outcome data for at least one full quarter, from a source you trust enough to pay on. Product mix and attach usually come from the CRM or order system; retention from the CS platform or billing. If a line can only be assembled by hand, either fix the integration or leave that line off the initial matrix — a hand-maintained KPI goes stale within a month and a stale line poisons trust in the whole composite.

Do I need dedicated software, or is a spreadsheet enough?

A spreadsheet is genuinely enough to start and plenty of teams run this way for a year. List the KPIs, set the weights, grade 1-to-5, and let one formula roll up the composite. The cost shows up later as maintenance hours and staleness risk — reps stop trusting a number that's clearly frozen. Dedicated scorecard or incentive-compensation tooling starts paying for itself once the team grows past the point where manual upkeep is somebody's real job.

How do I set weights when leadership disagrees about priorities?

Force the disagreement into numbers, because that's what the weights are. Ask each stakeholder to allocate 100 points across the KPI list independently, then compare. The gaps are the actual strategic argument, and they're much easier to resolve as a specific numeric difference than as a debate about emphasis. Whatever you land on, ship it and revisit next quarter — a published imperfect weighting beats an unpublished perfect one.

Will this hurt my best single-product rep?

Short-term, their score drops relative to peers and that conversation needs to happen face-to-face before the matrix goes live. Medium-term, they often become the biggest gainer, because they have the most headroom: a proven closer who adds two lines they'd been skipping typically moves their composite further than a balanced rep can move theirs. Frame it as available upside rather than a correction, and give them a specific first line to attack.

Sources

• https://hbr.org/2012/07/motivating-salespeople-what-really-works
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/sales-compensation-a-key-to-driving-sales-performance
• https://www.gartner.com/en/sales/topics/sales-performance-management
• https://www.salesforce.com/resources/articles/sales-compensation/
• https://www.shrm.org/topics-tools/tools/toolkits/designing-managing-incentive-compensation-programs
• https://sloanreview.mit.edu/article/the-hidden-costs-of-incentive-pay/
• https://www.investopedia.com/terms/k/kpi.asp
• https://www.bls.gov/ooh/sales/sales-managers.htm

Related on PULSE

• [How Do I Know Where, When, and How Many People to Schedule at Each of My Multi-Unit Retail Locations?](/knowledge/tl0001)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)
• [How Do I Know How Many Cooks and Servers to Schedule Each Shift at My Pizza Restaurant?](/knowledge/tl0003)
• [How Many Salespeople Should I Schedule Each Day on My Furniture Store Floor?](/knowledge/tl0004)
• [How Do I Decide How Many Reps to Schedule at Each Store in My Mattress Retail Chain?](/knowledge/tl0005)