The Sticker Price Is the Smallest Number on the Quote

We bought a $48K sales-engagement platform because the demo was good and one AE swore it would change his life. Eleven months later I pulled the seat report. Nineteen of forty-two licenses had logged in during the prior quarter. The AE who championed it had left. Nobody could tell me what the tool did that our existing stack did not, because nobody had ever written down what it was supposed to do. We renewed anyway, because canceling felt like admitting the first decision was wrong.

That is how most GTM tools get bought: a demo high, a loud champion, a quarter of urgency, and no scorecard. And the number that gets quoted, the sticker, is the smallest number on the deal. The price on the slide is the license. The price you pay stacks implementation, internal integration hours, training, the tier you outgrow into, and the switching cost baked in the day you sign. Watch what that stacking does to the sticker. Zoom the levels below: each one holds the license constant and grows the field around it, until the sticker you signed for is a dot inside the number you owe.

1.0x$99.3KL0The 3-year license, the only number on the quote

−

L0L1L2L3L4

+

one dollar of sticker price stays constant. The field around it grows each level.

I stopped letting the vendor’s sales rep run my evaluation. Now every tool over $10K clears the same weighted scorecard before it gets a contract, and the scorecard decides, not the demo. Roughly six in ten proposals die at the scorecard, and the ones that survive are the ones I would defend in a budget review a year later. The zoom above is why: the scorecard scores against the number at L4, not the one at L0.

The demo is not the evaluation

A demo shows you the tool on its best day, driven by someone who has driven it a thousand times, against data the vendor curated. It tells you almost nothing about the two questions that decide whether the tool survives: does it fit the workflow your reps already run, and what does it cost once you count the parts that are not on the quote. Both are boring. Neither shows up in a demo. So both get skipped, and the tool gets bought on the parts that feel good and none of the parts that predict regret.

The workflow question is not soft. Reps spend only 28% to 30% of the week selling and about 41% on administrative work already (Salesforce, State of Sales 2024), so any tool that adds net-new steps is competing for the scrap of time that is left. A scorecard forces that boring question into the decision before the emotional ones can win. It does not make the choice smarter than you. It makes the choice legible: when someone asks in twelve months why we bought this, the answer is a number and a weighting, not “the AE liked it.” That is the same discipline I argue for in tool-sprawl governance, where the problem is rarely one bad tool and almost always the absence of a repeatable gate every tool has to clear.

Six criteria, weighted, because they are not equal

The mistake people make with scorecards is scoring everything one to five and adding it up. That treats “does it integrate with Salesforce” and “is the UI pretty” as equal, and they are not close to equal. A tool that scores a five on polish and a one on integration will rot in your stack. The weighting is the whole point. It says out loud what matters, and it makes the pretty-but-useless tool score badly no matter how good the demo felt.

Here is the weighting I use. The weights sum to 100. They are not universal; a company in a heavy compliance posture would push security higher. But start here and adjust with intent, not vibes.

Criterion	Weight	What a 5 looks like	What a 1 looks like
Workflow fit	25	Slots into a motion reps already run, zero net-new steps	Requires reps to change how they work daily
Integration depth	20	Native two-way sync to system of record, field-level	CSV export only, or one-way, or “via Zapier”
Total cost of ownership	20	All-in year-3 cost near sticker	Sticker is under half the real cost
Adoption likelihood	15	Reps ask for it; it removes work	Requires a mandate and weekly nagging
Security and data posture	12	SOC 2 Type II, SSO, data residency answered	No SSO, vague on where data lives
Vendor viability	8	Funded, real roadmap, references you called	Seed-stage, one big customer, no references

Notice adoption is a first-class criterion, not an afterthought. A tool nobody uses is a 100% loss regardless of how good it is on paper, so the scorecard has to price the odds that it dies on the shelf. That is the criterion that would have killed my $48K engagement platform: a five on features, a two on adoption likelihood, because it duplicated something reps already did in a tool they already opened.

Integration depth sits at 20 for a reason beyond convenience. B2B contact data decays about 30% a year (ZoomInfo), and poor data quality costs the average organization around $15M a year (Gartner). A tool that only reads a one-way CSV export inherits every one of those errors and adds a second stale copy of the truth. Field-level two-way sync is what keeps the tool honest, so the criterion that rewards it earns its weight.

The weighted score is one line of arithmetic

The formula is deliberately trivial, because the value is in the criteria and the weights, not in the math. Each criterion gets a raw score of one to five, you multiply by its weight, sum, and normalize to a 0-to-100 scale so the number reads like a grade everyone understands.

# raw_scores: {criterion: 1..5}, weights: {criterion: 0..100}, weights sum to 100
def weighted_score(raw_scores, weights):
    # each criterion contributes (raw / 5) * weight; sum is already on a 0-100 scale
    total = sum((raw_scores[c] / 5) * weights[c] for c in weights)
    return round(total, 1)

WEIGHTS = {
    "workflow_fit":       25,
    "integration_depth":  20,
    "tco":                20,
    "adoption":           15,
    "security":           12,
    "vendor_viability":    8,
}

# a 5 on everything -> (5/5)*w summed = 100; a 3 across the board -> 60

If you would rather keep it in a spreadsheet, the same thing is one cell. Put raw scores in column B and weights in column C, then:

= SUMPRODUCT(B2:B7 / 5, C2:C7)

That returns the same 0-to-100 grade. The point of writing it down as an artifact, whether Python or a spreadsheet cell, is that the next person who evaluates a tool uses the identical formula, so two evaluations are comparable. A scorecard that lives in one person’s head is not a scorecard.

Two tools, scored the same way

Abstract scorecards convince nobody. Here are two real-shaped candidates for the same job, a conversation-intelligence tool, scored against the six criteria. Tool A is the polished market leader everyone demos. Tool B is the scrappier option that plugs into what we already run.

Criterion	Weight	Tool A (raw)	Tool A (wtd)	Tool B (raw)	Tool B (wtd)
Workflow fit	25	3	15.0	5	25.0
Integration depth	20	4	16.0	4	16.0
TCO	20	2	8.0	4	16.0
Adoption likelihood	15	3	9.0	4	12.0
Security	12	5	12.0	3	7.2
Vendor viability	8	5	8.0	2	4.0
Total	100		68.0		80.2

Tool A is the one the demo made you want. It is polished, secure, and backed by a public company, so it scores fives where confidence is easy. But it lands at 68, under the 70 threshold, because it forces reps into a new daily workflow (a 3 on fit) and its three-year all-in runs close to double the sticker (a 2 on TCO, the same 1.9x the zoom walked through). Tool B is less glamorous and the vendor is younger, but it fits the motion reps already run and costs what it says it costs. It clears the threshold at 80.2.

View as table

Item	Value
Fit	15
Integration	16
TCO	8
Adoption	9
Security	12
Vendor	8

The scorecard did something the demo never would: it let Tool A win the categories it deserved to win and still lose the decision, because the categories it lost are weighted heavier. That is the discipline. The prettiest tool does not get a handicap.

TCO is where the sticker price lies

The single most-skipped criterion is total cost of ownership, and it is skipped because the real number is annoying to compute. The sticker is the license. The real cost adds implementation, the internal hours to integrate and maintain it, training, the premium tier you will need once you outgrow the demo plan, and the switching cost baked in the day you sign. Here is the TCO frame I fill in before scoring that criterion, and it is the same stack the zoom animated at the top. Put real numbers in it, not the vendor’s numbers.

Cost line	Year 1	Year 2	Year 3	Notes
License (sticker)	$30,000	$33,000	$36,300	Assume 10% annual uplift
Implementation / onboarding	$12,000	$0	$0	Often a separate SOW
Internal integration + maintenance	$18,000	$9,000	$9,000	~0.1 FTE ongoing
Training + change management	$6,000	$2,000	$0	Ramp new hires too
Tier upgrade (seats + features)	$0	$12,000	$18,000	You will outgrow entry tier
All-in	$66,000	$56,000	$63,300	3-yr total: $185.3K

The sticker across three years reads as $99.3K. The all-in is $185.3K. That is the 1.9x on the stat tile and the $185.3K at level L4 of the zoom, and the two numbers are the same number seen twice. The scorecard’s TCO criterion scores against the all-in, which is why the leader in the worked example took a 2. A tool whose real cost is near its sticker earns the 4 or 5. Most do not.

The no-regrets threshold

A score is useless without a line. The line I use is 70 out of 100, and it is a hard gate, not a suggestion. Under 70, you do not sign, no matter who is excited. The threshold exists so the decision cannot be argued back open by the loudest person in the room. It is the difference between a scorecard that governs and a scorecard that decorates a slide.

Two rules make the threshold real. First, any criterion scoring a 1 is an automatic fail regardless of total, because a 1 on security or integration is a landmine that a high total can hide. Second, the score gets recorded and the tool gets a 90-day usage check written into the calendar the day you sign, so a tool that scored an 80 on adoption likelihood and then gets used by four people gets caught before the auto-renew, not after. That second rule is the one that would have saved my $48K.

Here is how I would build it

This is the sequence I run for any new tool category, start to signature. It takes about a week of calendar time and maybe six hours of real work, and it replaces the demo-driven decision with an evidenced one.

1. 1

   Write the job before you take a demo

   One paragraph: what specific workflow this tool improves and what metric moves if it works. If you cannot write it, you are not ready to evaluate, you are ready to be sold to. This paragraph becomes the workflow-fit rubric.

2. 2

   Lock the weights before you score

   Set the six weights to 100 as a team, once, and reuse them across evaluations. Adjust only with a stated reason, a compliance push, say. Weights set after you see the tools get gamed toward the tool you already want.

3. 3

   Fill the TCO frame with your numbers

   Build the three-year all-in table using your internal FTE cost and a realistic tier-upgrade assumption, not the vendor quote. This is the criterion that separates a governed buyer from an optimistic one, and it is the L0-to-L4 stack from the zoom at the top.

4. 4

   Score against evidence, not the demo

   Call two references you sourced yourself, run a scoped trial on real data, and score each criterion 1 to 5 with a one-line justification per score. A score with no justification is a guess wearing a number.

5. 5

   Apply the gate and record the decision

   Run the weighted formula. Under 70 or any single 1 is a no. Over 70 signs, and the same day you put a 90-day usage review on the calendar with a named owner. The record is what makes next year defensible.

What changes when the gate exists

	Demo-driven buying	Scorecard-gated buying
Who decides	The champion and the demo high	The weights, set before the demo
What TCO means	The sticker price on the quote	Three-year all-in, often ~1.9x sticker
Adoption	Assumed, discovered later	Scored up front, checked at 90 days
A year later	"Why did we buy this?" with no answer	A recorded score and a usage check
The pretty tool that loses on fit	Wins, because the demo won	Loses, because fit is weighted 25

The gate does not make you buy fewer tools out of stinginess. It makes you buy the tools you can defend and skip the ones you would have quietly regretted. When a tool clears 70 on real evidence, sign fast and commit; the scorecard bought you the right to move quickly because the diligence is already done.

The $48K platform we renewed out of guilt is gone now. It failed a scorecard it never had to take. Build the scorecard once, set the weights before the next demo, fill the TCO frame so the sticker stops hiding the number at L4, and let the score decide instead of the room. Pull the formula above, drop it in a sheet, and grade the next proposal on your desk before you take the second call.