Use it for
- Transcripts of pricing or willingness to pay interviews.
- Sales call notes and lost deal notes that mention price.
- Comments from the pricing page, plan changes and downgrade forms.
Steps
- Find every price passage
Search the data for price words: cost, expensive, cheap, plan, tier, seat, discount, budget, worth. Read each match in its context. Keep passages where the customer reacts to how much or how you charge.
- Code what the complaint is about
Ask one question for each passage: would a lower price fix it? If yes, it is about the level. If not, it is about the structure, the terms or the value. Choose the code with that rule.
- Record stated amounts apart
When a customer names a number, write it in a separate field with the plan and the context. Do not average these numbers. Use them only to see the range and the anchors people use.
- Note the reference point
For each Price level passage, write the reference point, such as a competitor price or a budget line. The reference point tells you which message to change.
- Split by segment and plan
Count codes for each plan and company size. Small accounts often complain about the level. Large accounts often complain about the value metric or the terms.
- Test before you change prices
Treat what customers say as a reason to test, not as proof. Stated willingness to pay is often lower or higher than what customers do. Confirm with a pricing test or real purchase data.
Codebook
Copy the codebook as a table. It pastes into a spreadsheet with one row for each code.
Price level
The customer reacts to the amount they pay, with no complaint about how it is charged.
- Include
- The customer says the price is too high, fair or low, and a different amount would fix the complaint.
- Exclude
- The customer compares the price to what they get from the product. Use Value for money for that.
- Example
- “Forty a month is just a lot for a small shop like mine.”
Value for money
The customer weighs the price against the benefit they get.
- Include
- The customer links the price to results, time saved, use or features, and judges whether it is worth it.
- Exclude
- The customer only mentions the amount with no link to benefit. Use Price level for that.
- Example
- “If it saves me one hour a week it pays for itself, so I do not mind.”
Value metric fit
The customer reacts to the unit that the price is based on, such as seats, usage, contacts or projects.
- Include
- The customer says the unit does not match how they get value, or grows faster than their value.
- Exclude
- The customer hits a limit inside a plan, not the unit of charge. Use Plan limits for that.
- Example
- “Paying per seat makes no sense for us. Ten people look at it once a month, two people use it every day.”
Plan limits
The customer reacts to features or caps that separate one plan from another.
- Include
- The customer mentions a feature that is only in a higher plan, or a cap that forces an upgrade.
- Exclude
- The customer cannot understand which plan to choose. Use Plan confusion for that.
- Example
- “I need one feature from the Business plan and I would pay for it alone, but not for the whole plan.”
Plan confusion
The customer does not understand the plans, what each includes or which one to choose.
- Include
- The customer asks which plan fits them, misreads what a plan includes or picked the wrong plan.
- Exclude
- The customer understands the plans but dislikes the split. Use Plan limits for that.
- Example
- “I read the table three times and still did not know if Pro includes the API.”
Unexpected cost
The customer found a cost they did not expect at the time of purchase.
- Include
- The customer mentions an overage, an add-on, tax, a setup fee or a price change after the first period.
- Exclude
- The customer knew the cost in advance and thinks it is too high. Use Price level for that.
- Example
- “The first bill had a setup fee nobody told us about.”
Billing terms
The customer reacts to how and when they pay, not how much.
- Include
- The customer mentions annual or monthly billing, contract length, payment method, invoicing or currency.
- Exclude
- The customer reacts to a discount for a longer term. Use Discount expectation for that.
- Example
- “Our finance team cannot pay by card. If you do not invoice, we cannot buy.”
Competitor price reference
The customer compares the price with a named or described competitor.
- Include
- The customer names a competitor's price, or says another tool costs less or more for the same need.
- Exclude
- The reference is a free tool or a free plan. Use Free alternative for that.
- Example
- “Their basic plan is half of yours and does the same reports.”
Free alternative
The customer compares the product with a free option, including your own free plan.
- Include
- The customer mentions a free tool, a free plan, a spreadsheet or a built-in function they already have.
- Exclude
- The free option is a trial of a paid competitor. Use Competitor price reference for that.
- Example
- “Why pay when Google Sheets does 80 percent of this for free?”
Discount expectation
The customer expects or asks for a discount, a promotion or special pricing.
- Include
- The customer waits for a sale, asks for a special price or asks for a discount for a longer term.
- Exclude
- The customer says the list price is too high in general. Use Price level for that.
- Example
- “I will wait for Black Friday, you always do 30 percent off.”
Willingness to pay signal
The customer states an amount or a condition under which they would pay.
- Include
- The customer names a number, a range or a condition such as "if it did X I would pay Y".
- Exclude
- The customer gives no amount and no condition. Code the reason instead.
- Example
- “If it did the invoicing too, I would pay 60 without thinking.”
Report outline
- Sources and sample: interviews, sales notes and forms, with dates and segments.
- Complaints about the price level versus complaints about structure and terms, with the share of each by segment.
- Reference points: what customers compare your price with, and what that means for the pricing page.
- Value metric and plan findings, with quotes, for the pricing owner.
- The range of stated amounts, shown as a range with the context, not as an average.
- Changes to test, each with the metric that will show the result.
Mistakes to avoid
- Do not average the amounts customers name. Stated numbers depend on the anchor in the question and are not a price point.
- Do not code every complaint as Price level. Ask if a lower price would fix it. Often the unit or the terms are the problem.
- Do not change prices from interview data alone. Use the codes to choose what to test, then test it.
- Do not ignore praise for the price. Customers who say the price is fair tell you which value to keep in the message.
Guides that use it