Behavioural Signals That Reveal Willingness to Pay — Before Customers Say It

Stated preferences lie. Behavior doesn't. If you're setting prices based on survey answers or Net Promoter Score (NPS), you're working with a lagging indicator while the real signals sit in your product analytics untouched.

The Number That Moves

Pricing decisions built on stated willingness to pay systematically underprice your product. McKinsey's pricing practice has documented a 20 to 30 percent gap in B2B contexts, where customers rate themselves as more price sensitive than their behavior proves them to be. The implication for a $20M annual recurring revenue (ARR) company: every pricing move is calibrated against a signal that's understating the ceiling by a quarter or more.

The cost compounds. NPS-driven pricing sits on top of the same problem. A customer with a 9 on NPS might accept a 20 percent price increase without friction, or they might churn. Sentiment doesn't predict economic behavior. When the pricing committee reviews NPS and concludes customers love the product so we can raise prices, they're guessing. When they review usage frequency, feature adoption, and ticket themes, they're reading a map.

Most of the customers you could reprice by 15 to 30 percent today are showing you the readiness signal in data you already have. You're just not looking at it through a pricing lens.

Working the Problem

Step 1: Measure feature adoption velocity in the first 45 days

Track how many distinct features a new customer activates within 45 days and whether the adoption pattern looks like job-expansion or curiosity. Job-expansion is sustained engagement with a specific new feature set. Curiosity is brief touches across many features. The first predicts willingness to pay. The second predicts churn.

A fintech analytics company we worked with found that customers who activated three or more features within 45 days had 2.4x the expansion revenue of single-feature users over the following 18 months. The signal was visible in week six. The pricing conversation was happening in month 18. That 12-month gap is the opportunity.

Step 2: Define your usage frequency threshold

Every product has a threshold above which retention becomes nearly guaranteed. Pull your retention curves by weekly active usage and find the inflection point where the curve flattens. That's your threshold. Forrester research on SaaS retention shows customers above this threshold are 3 to 4x more likely to accept a price increase without churning, because switching cost now exceeds the increase.

Segment your customer base into above-threshold and below-threshold. Only the first group is ready for a pricing conversation. Applying a price increase to the second group accelerates churn.

Step 3: Categorize support tickets by intent

Read your last 50 tickets and sort them into troubleshooting, how-to, and capability requests. Capability requests are expansion signals. A customer asking "can your API handle 50,000 calls per hour" is telling you their usage is scaling past your current tier. A customer complaining about a seat limit is ready for the next tier.

Tag tickets automatically going forward. The ratio of capability-to-troubleshooting tickets, by account, becomes a pricing signal that updates weekly.

Step 4: Build a three-color dashboard

Green signals: high adoption velocity, above-threshold usage, expansion-oriented tickets. Yellow signals: stable usage, maintenance tickets. Red signals: declining usage, basic troubleshooting, long login gaps. Run your customer base through this dashboard monthly.

Green accounts are ready for upgrade, expansion, or price increase conversations. Yellow accounts hold. Red accounts need retention intervention, not pricing pressure.

Step 5: Tie the signal to the action

A signal without a trigger is analytics theater. For each green account, define the next pricing action: upgrade outreach, tier review, contract expansion, multi-year renewal. For each red account, define the retention action. The signal is only useful when it changes what someone does on Monday morning.

The Breakdown Point

The most common failure mode is treating behavioral signals as nice-to-have product analytics rather than core inputs into pricing. Product teams look at adoption to prioritize the roadmap. Customer success looks at usage to prevent churn. Pricing teams look at surveys. The data silo is the problem.

The second failure is over-indexing on a single signal. Usage frequency without feature depth misses the customer who logs in daily but uses one feature. Feature adoption without frequency misses the customer who activated everything in week two and hasn't returned. You need the pattern, not the point.

What do your top-decile customers look like behaviorally, and how many of them are you pricing as if they were average?

Move This Quarter

• Pull product analytics for your top-decile accounts and document their feature adoption velocity
• Define the usage frequency threshold where your retention curve flattens
• Tag your last 100 support tickets by intent and calculate the capability-to-troubleshooting ratio per account
• Build a green/yellow/red pricing signal dashboard and review it monthly with sales leadership
• Map each signal color to a specific pricing action so the data drives a decision

If your team is wrestling with how to convert behavioral signals into pricing decisions, we can help. Assess Your Pricing Health and we'll walk through the signals sitting in your data today and the pricing actions they support.