Are Logistics & Supply Chain Firms Underpricing? Use the Kano Model to Find the Money You're Leaving on the Table
Direct answer: Most logistics providers underprice because they treat differentiating capabilities—real-time visibility, guaranteed transit times, exception management—as free extras rather than billable value. The Kano Model separates what customers expect (basic needs you can't charge more for) from what genuinely delights them (features they'll pay a premium for). Run your service catalog through it and you'll usually find two or three "delighters" you're giving away, plus commodity services you're overinvesting in. That gap is your pricing upside.
Why logistics pricing quietly leaks value
Freight, warehousing, and 3PL pricing is anchored to cost-plus math and competitive benchmarking. Both anchors ignore how customers actually perceive value—and that's where the leakage happens.
Two failure patterns dominate:
- You bundle premium capabilities into a flat rate. A shipper who would happily pay for guaranteed dock appointments, control-tower visibility, or proactive exception alerts gets them for free because they're baked into your standard SLA.
- You over-serve on commodities. You've invested in gold-plated tracking or white-glove onboarding for freight lanes where the customer only cares about on-time delivery and price. That spend doesn't move the win rate or the margin.
The Kano Model exists precisely to distinguish these cases. It classifies every service feature by how satisfaction changes as you deliver more or less of it—which is a far better pricing lens than "what do competitors charge."
The Kano Model, applied to a logistics service catalog
Kano sorts features into five categories. For a logistics or supply chain provider, they map like this:
- Basic (Must-be): Expected as table stakes. Presence earns nothing; absence loses the account. Examples: accurate invoicing, freight arrives undamaged, shipments delivered within the quoted window.
- Performance (One-dimensional): Satisfaction scales linearly with how well you do it. More is better, and customers will pay proportionally. Examples: transit speed, on-time percentage, cost per mile, claims ratio.
- Excitement (Delighters): Unexpected features that create disproportionate satisfaction and premium willingness-to-pay. Examples: predictive ETA with automatic re-routing, embedded carbon reporting, self-service capacity booking, proactive delay alerts before the customer notices.
- Indifferent: Features customers don't care about either way. Examples: a slick portal nobody logs into; multiple redundant notification channels.
- Reverse: Features that actually reduce satisfaction. Examples: over-communication, forced software adoption, complex onboarding for a simple lane.
The pricing insight: you can only charge a premium on Performance and Excitement attributes. Basic attributes are hygiene. Indifferent and Reverse attributes are cost you should cut.
A concrete walkthrough
Here's how to run it on your book of business.
Step 1 — Inventory your service features. List every capability across your catalog: visibility tooling, exception handling, dedicated reps, SLA tiers, reporting, sustainability data, integration options, appointment scheduling. Be granular. "Tracking" is three features, not one.
Step 2 — Ask the Kano question pair for each feature. For every feature, survey or interview key accounts with two questions:
- Functional: "How do you feel if we provide [feature]?"
- Dysfunctional: "How do you feel if we do NOT provide [feature]?"
Answers use a fixed scale (I like it / I expect it / I'm neutral / I can tolerate it / I dislike it). The response pair classifies the feature. For example: "I like it" + "I dislike its absence" = Performance; "I'm neutral" + "I dislike its absence" = Basic; "I like it" + "I'm neutral about its absence" = Excitement.
Step 3 — Segment, because Kano varies by customer. A high-volume industrial shipper treats real-time visibility as Basic. A specialty pharma or perishables shipper treats it as an Excitement feature worth a premium. Run the classification per segment. This is where flat-rate pricing across mixed segments visibly bleeds margin.
Step 4 — Overlay cost and current price. For each feature, note what it costs to deliver and whether it's currently priced. The money-on-the-table list is: Excitement + Performance features that are unpriced or under-priced. The cost-cut list is: Indifferent + Reverse features you're funding.
Step 5 — Redesign tiers and repackage. Move delighters into a premium tier or à-la-carte add-ons. Keep basics in the base rate. Kill or de-invest in indifferent features. What "good" looks like: a clear good/better/best structure where each step up is justified by Performance and Excitement attributes your segments confirmed they value.
One caution built into the model: today's Excitement becomes tomorrow's Basic. Real-time visibility was a delighter a decade ago; now most large shippers expect it. Re-run the analysis annually so your premium tier stays genuinely premium.
Where Percision fits—and where it doesn't
Full disclosure: I write for Percision, so treat this as one option, not gospel.
Running Kano well is straightforward in concept but demanding in execution: you need customer input, honest cost data, and the discipline to translate classifications into pricing tiers and a rollout plan. Two honest paths:
A spreadsheet and a few customer calls are enough if you have one main segment, a short service list, and internal analysts who can run the survey and build the tier logic. Don't over-engineer this—Kano on a napkin beats no analysis.
Percision helps when you're running this across multiple segments and want it tied to financial impact. It's an AI strategic-intelligence platform that runs your business context through structured reasoning steps across frameworks (Kano among 27+), then produces board-ready output: pricing scenario analyses, the margin impact of repackaging tiers, and an execution plan with an Excel-exportable model. It's positioned as a co-pilot, not autopilot—your team supplies the customer judgment and stays in control of the call. It compresses the analysis-and-deck timeline from weeks to minutes.
When to hire a human consultant instead: if your pricing change requires renegotiating major contracts, deep organizational change management, or hands-on primary research with your accounts, a specialist advisor earns their fee. Percision accelerates the analysis; it doesn't sit across the table from your largest shipper.
What this looks like when the analysis is actually run
Freight is treated as a commodity, which is mostly true and not entirely. Kano's question is which lanes carry a service attribute a shipper will actually pay for.
The subject is Ridgeway Freight Systems, a sample company profile we use for testing rather than a customer: a regional LTL carrier, $284M revenue, 18 terminals, 620 drivers.
Excerpt from a real Percision run · Quick Market Scan (T1) · sample company profile
Where the premium exists. Implement lane-level dynamic pricing on the 50 densest LTL lanes to capture a 5–8% premium justified by terminal density — generating $4.2–6.3M of incremental revenue at 85%+ incremental margin.
Why density is the attribute. The 18-terminal network is fully depreciated; the shared equipment pool allows dynamic reallocation between LTL and dedicated operations. Ridgeway generated $284M of revenue in FY2025 with operating income of $14.8M and an operating ratio of 94.8.
What the premium funds. Reinvest the incremental revenue into driver retention: a 13-point turnover reduction saving $1.1M of replacement cost, and a 0.8-point empty-mile reduction improving the LTL operating ratio from 92.1 to 91.3.
What it costs. $0.6–0.9M over 36 months for a pricing engine and retention bonuses, returning 7–10× within 24 months. Revenue: $289–293M Year 1, $298–306M Year 2, $310–320M Year 3.
The reversal. Reverse if net revenue per hundredweight on the 50 lanes has not increased by at least 2% within 12 months.
| Phase | Gate metric | Target | Deadline |
|---|---|---|---|
| Foundation (0–6 months) | Net revenue per hundredweight on pilot lanes | +3% vs. control lanes | Month 6 |
| Traction (6–18 months) | Driver turnover rate | ≤70% | Month 18 |
| Scale (18–36 months) | LTL operating ratio | ≤91.3 | Month 36 |
The Kano insight is that density is a performance attribute, not a basic one. On a thin lane the carrier is one of many and price is the only variable; on the fifty densest lanes Ridgeway can offer transit times and frequency competitors cannot match from a sparser network, and 5–8% is what that is worth.
The 2% reversal threshold against a 5–8% target is a wide corridor, deliberately. Freight pricing moves slowly and a lane-level programme that has produced nothing in twelve months has failed; one that has produced 3% is simply working slower than hoped.
Read a complete Percision report — every page, no email required.
FAQ
Q: How is Kano better than cost-plus pricing for logistics? Cost-plus tells you your floor; it says nothing about willingness to pay. Kano identifies which capabilities customers value enough to pay a premium for—so you price to perceived value, not just cost.
Q: How many customers do I need to survey? Enough to reach stable classifications per segment, typically a focused set of representative accounts rather than a mass survey. The goal is directional clarity per segment, not statistical precision across your whole book.
Q: Won't customers just say they want everything for free? The Kano question pair defends against this. Asking how they feel about a feature's absence forces trade-offs and exposes which items are true delighters versus assumed entitlements.
Affiliation note: This article is published by Percision (percision.app). We've tried to represent both the DIY and platform paths honestly.