Are Manufacturers Underpricing? Use the Kano Model to Find Money You're Leaving on the Table
Direct answer: Most manufacturers underprice because they price on cost-plus math instead of on the value customers actually perceive. The Kano Model helps you separate features customers take for granted (and won't pay extra for) from features that genuinely delight them (and command premiums)—so you can raise prices where value is real and stop giving away performance for free. Run this analysis by segment and product line, not across your whole catalog at once.
Why Cost-Plus Pricing Hides Money in Manufacturing
Cost-plus is the default because it feels safe and defensible. You know your bill of materials, you add a target margin, and you quote. The problem: that number is disconnected from what a customer would actually pay. Two customers buying the same part—one for a non-critical bracket, one for a safety-critical aerospace assembly—get charged the same, even though the second values reliability, traceability, and lead-time far more.
Underpricing usually shows up as one of three patterns:
- Undifferentiated premiums: You deliver tight tolerances, faster lead times, or better quality data than competitors, but you price at market because you've never quantified what that's worth to specific buyers.
- Free "delighters": Engineering support, custom tooling, expedited shipping, or vendor-managed inventory bundled in at no charge—features some customers would gladly pay for.
- Uniform pricing across unequal value: One price list applied to segments that value your capabilities very differently.
The Kano Model attacks all three by classifying features according to how they affect customer satisfaction—not according to what they cost you to produce.
The Kano Model, Applied to a Manufacturing Line
Developed by Noriaki Kano, the model sorts product and service attributes into categories. For a manufacturer, the practical three are:
- Must-be (basic) features: Expected as table stakes. Meeting spec, hitting dimensional tolerance, on-time delivery, quality certifications. Present, customers are neutral; absent, they're furious. You cannot charge a premium for these.
- Performance (one-dimensional) features: More is better and buyers will pay proportionally. Shorter lead times, tighter tolerances, lower defect rates, faster turnaround on quotes. These map directly to price tiers.
- Attractive (delighter) features: Unexpected value that drives loyalty and premium willingness. Design-for-manufacturability consulting, real-time production visibility, guaranteed capacity reservations, lifecycle documentation. These are your monetization opportunities.
A concrete walkthrough:
Step 1 — Pick one product family and one or two customer segments. Don't boil the ocean. Take a machined-component line serving both automotive tier-2 and medical-device customers. They value very different things.
Step 2 — List 8–12 attributes you deliver. Include the boring ones (spec conformance, packaging) and the extras (engineering support, expedited runs, PPAP documentation, EDI integration, consignment inventory).
Step 3 — Ask the paired Kano questions per attribute, per segment. For each feature ask two questions:
- Functional: "How do you feel if this feature is present?"
- Dysfunctional: "How do you feel if it's absent?" Answer options run from "I like it" to "I dislike it." The pattern of answers classifies each attribute as must-be, performance, attractive, or indifferent. Talk to real buyers and your sales team—not just internal engineers who assume they know.
Step 4 — Add willingness-to-pay probing. Kano tells you the type of value; pair it with a simple question—"If we guaranteed 5-day lead time instead of 10, what's that worth per unit?"—to get direction on magnitude.
Step 5 — Reprice by category. Stop charging premiums for must-be features (customers won't pay). Build tiered pricing on performance features. Unbundle and price the delighters you've been giving away—or make them the reason a premium tier exists.
What "good" looks like: You end with a segment-by-segment map showing which features are table stakes, which scale with price, and which delighters you can monetize—plus a revised price architecture and a short list of pricing experiments to run on new quotes.
How Percision Runs This—and When You Don't Need It
I work on content for Percision, so treat this as one option, not the only one.
Percision is an AI-powered strategic intelligence platform. For a pricing question like this, you'd feed in your product lines, customer segments, cost structure, and competitive context. It runs that through structured reasoning steps across multiple frameworks—including Kano—and returns a segment-level value map, pricing-tier recommendations, a financial model showing margin impact of repricing, and a board-ready deck. That's minutes-to-hours instead of an 8–12 week consulting engagement, and the human team stays in control of every decision—it's a co-pilot, not an autopilot.
Where that helps: you have several product families and segments, you want the Kano analysis tied to a DCF and margin model, and you need something you can defend in front of a board or ownership group quickly.
When a spreadsheet is enough: If you have one product line and a handful of long-standing customers, you can run Kano with a survey and a whiteboard. Interview your top ten accounts, classify the attributes yourself, and reprice manually. The framework works fine on paper.
When to hire a human consultant instead: If your pricing problem is entangled with a channel conflict, a union negotiation, or a major contract renegotiation with a dominant OEM customer, the relationship and negotiation dynamics matter more than the framework. Get someone who's sat across that table. Broad AI-productivity research (for example, studies from BCG and Harvard Business School on knowledge work) suggests AI tools lift performance most on well-structured analytical tasks—and less on the messy relational ones. Pricing analysis is structured; a hostile customer negotiation is not.
Turning the Analysis Into a Pricing Plan
The output is only useful if it changes quotes. A workable execution sequence:
- Pilot on new business first. Apply the revised architecture to fresh quotes so you learn before touching existing contracts.
- Sequence existing accounts by risk. Reprice low-switching-cost, high-underpricing accounts first.
- Arm sales with the value story. Reps need to articulate why the delighter feature costs more—not just quote a higher number.
- Track win-rate and margin together. If win rates hold and margin rises, you were underpricing. If wins collapse, you misclassified a feature or a segment.
What this looks like when the analysis is actually run
Kano asks which attributes a customer will pay a premium for. For an OEM buyer that is rarely the part — it is the speed of a change.
The subject is Kessler Industrial Components, a sample company profile we use for testing rather than a customer: a precision machining supplier, $340M revenue, three plants, 1,180 staff.
Excerpt from a real Percision run · Quick Market Scan (T1) · sample company profile
The basic expectation, priced accordingly. Piece-price production at a 24% gross margin, under contractual price-downs.
The performance attribute nobody was charging for. Engineering change orders delivered at 35–40% gross margin, priced at $400–600K each with a $1.2M annual floor — 8–12 per year. The capability rests on tooling already owned and PPAP/APQP records already accepted.
What makes it defensible rather than merely chargeable. A 6.5-year qualification lock-in; 61% of automation hours already tied to Customer A's manifold family; an alternative supplier would need 12–18 months and $250–750K to requalify.
The competing lever, priced very differently. A $45M automation programme raising overall equipment effectiveness from 61% to 74% and cutting direct labour content 19%, for a 24% IRR over the 7-year programme life — $11M of annual gross profit derived from a 13-point OEE lift × $340M revenue × 24% gross margin, funded by a debt draw against roughly $32M of covenant headroom.
What the chargeable attribute is worth over three years. Year 1 $1.2–1.8M of incremental design-fee revenue; Year 2 $3.0–4.0M cumulative; Year 3 $4.5–6.0M cumulative, on $0.3–0.5M invested — payback under 6 months, 8–10× return. Targets: design-fee run-rate $4–6M annually by Month 24, ECO gross margin at 35% or better from Month 12, and 80% of informal ECOs converted to paid by Month 18.
| Phase | Gate metric | Target | Deadline |
|---|---|---|---|
| Foundation (0-6 months) | Signed letter-of-intent with Customer A for paid-ECO pilot covering at least 3 ECOs | LOI executed | Month 6 |
| Traction (6-18 months) | Cumulative design-fee revenue ≥ $2.4 M and gross margin ≥ 35 % on ECO work | $2.4 M revenue, 35 % GM | Month 18 |
| Scale (18-36 months) | Segment 3 pipeline ≥ $8 M with ≥ 2 signed design-authority programmes | $8 M pipeline, 2 programmes signed | Month 36 |
The Kano split here is unusually clean. Parts are a basic expectation: required, competitively bid, worth 24%. The ability to redesign a manifold and have it qualified quickly is a performance attribute worth 35–40% — and it is being given away because it arrived as a favour rather than as a product.
Set against the $45M automation case, the contrast sharpens. One spends $45M to defend a 24% margin on parts; the other spends $0.4M to start earning 35–40% on work already being performed. Both are defensible; only one of them requires a covenant conversation.
Read a complete Percision report — every page, no email required.
FAQ
How is Kano different from just doing a competitor price comparison? Competitor comparison anchors you to the market's current pricing—which may be collectively underpriced. Kano anchors to what customers actually value, which can reveal premiums competitors are also missing.
Can we use Kano if we make commodity parts? Yes, but expect most attributes to land in "must-be." Your monetizable delighters will be service-side: lead time, availability, documentation, and integration—not the part itself.
How often should we redo this? Revisit when you launch a product line, enter a new segment, or see win rates shift. Value perceptions drift as customer expectations rise (today's delighter becomes tomorrow's must-be).
If you want to run a Kano-based pricing analysis with margin modeling attached, Percision can produce a board-ready version quickly—while your team keeps final say on every price.