# Choose a pricing unit customers can understand > Evaluate potential charging units against value, predictability, measurement and serving cost. Complete the exercise, produce a working artifact and review it against a practical rubric. Source: https://saas-marketing.net/courses/saas-pricing-sprint/01-pick-your-value-metric/ Topic: SaaS Pricing Type: course-lesson Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/courses/saas-pricing-sprint/01-pick-your-value-metric/ ## Short answer Evaluate potential charging units against value, predictability, measurement and serving cost. This lesson turns that decision into a working document: a value-metric scorecard with customer evidence and a proposed validation test. Use the steps, example and review questions below to complete the exercise with your own product or an explicitly labelled practice case. ## Key takeaways - Evaluate potential charging units against value, predictability, measurement and serving cost. - A value-metric scorecard with customer evidence and a proposed validation test. - Keep assumptions separate from observed evidence. - Finish with a decision and a named next action, not only a completed document. --- This lesson is part of the [saas pricing sprint course](/courses/saas-pricing-sprint/). Evaluate potential charging units against value, predictability, measurement and serving cost. ## Prepare your working case Choose one product and one customer segment. Gather the relevant product information, customer evidence and operating records before writing the answer. If you are learning without access to a business, use a clearly labelled practice case and state the assumptions you make. Keep the scope small enough that you can explain the decision to another person. The purpose is to learn how to reason through the work, not to produce a longer document than the situation needs. ## Work through the exercise ### Step 1 List units that plausibly follow the customer's benefit. Record your answer, the evidence behind it and any unresolved dependency before moving to the next step. ### Step 2 Ask how buyers forecast and explain each unit internally. Record your answer, the evidence behind it and any unresolved dependency before moving to the next step. ### Step 3 Compare the unit with product costs and expansion behavior. Record your answer, the evidence behind it and any unresolved dependency before moving to the next step. ### Step 4 Select a candidate and record the conditions under which it fails. Record your answer, the evidence behind it and any unresolved dependency before moving to the next step. ## Worked situation Charging by active employee can fit payroll work, while charging by every login might punish routine use without matching value. Treat this as an illustration of the decision, not a measured result or a claim that the same approach fits every company. In your own case, identify which condition would make the conclusion different. That condition belongs beside the recommendation. ## Produce the deliverable A value-metric scorecard with customer evidence and a proposed validation test. Use the [working template](/templates/saas-pricing-page-spec/) to organize the result, then run the [review checklist](/checklists/pricing-page-conversion-audit/). Add the project name, date, owner and a link to supporting evidence. If a key input is unknown, describe how you would learn it rather than filling the gap with a confident guess. A useful deliverable can be read without a live presentation. Another person should be able to identify the problem, understand the recommended choice and see what happens next. Remove any section that does not help them make or execute that decision. ## Review your work | Review question | Evidence in your work | Revision needed | | --- | --- | --- | | Does the unit reflect the customer's job? | | | | Can the buyer predict the bill? | | | | Can the product measure and explain usage reliably? | | | Ask a colleague to challenge the weakest assumption. Write down the strongest alternative explanation and the evidence that would distinguish it from your current view. This makes the result easier to revise when new information arrives. ## Continue the course Return to the [course outline](/courses/saas-pricing-sprint/) or use the lesson navigation below. For the wider topic, visit [saas pricing](/saas-pricing/). The [resource library](/resources/) and [calculators](/calculators/) provide additional working tools. {/* expanded-practice-2026-09 */} ## Apply choose a pricing unit customers can understand in a working review Use the lesson to produce a small working artifact. State the starting problem, apply the method to one case and ask another person to inspect the result. Compare their interpretation with the explanation you intended. Revise the artifact before repeating the exercise at a larger scope; reading the material alone does not establish that the method can be applied. For this topic, involve the pricing owner with finance, product and customer-facing input and work from offer scope, charging unit and scenario assumptions. The relevant unit is a defined customer segment and comparable commercial offer. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence. ### Evidence to prepare A price is meaningful only with its package, quantity, terms and serving requirements. Test whether buyers can predict the bill and whether the charging unit supports useful adoption. Keep willingness-to-pay statements separate from observed purchasing behavior. | Review field | What to record | | --- | --- | | Topic | Choose a pricing unit customers can understand | | Decision | The specific action this explanation should help you choose | | Working evidence | offer scope, charging unit and scenario assumptions | | Unit and scope | a defined customer segment and comparable commercial offer | | Responsible people | pricing owner with finance, product and customer-facing input | | Remaining uncertainty | The missing fact that could change the decision | ### Two situations that can change the interpretation #### When the pricing model ignores assisted delivery A product that needs repeated specialist intervention may have different economics from a self-serve offer at the same advertised price. Use this check: Estimate the actual support, implementation and maintenance effort for comparable cohorts. Do not treat every employee hour as removable cash cost. The [focused diagnostic guide](/guides/pricing-model-ignores-support-cost/) provides the correction process and a working evidence sheet. #### When buyers cannot predict the pricing unit A contact-based plan needs a clear definition of which contacts count rather than relying on a familiar-sounding label. Use this check: Ask a suitable buyer to estimate an ordinary and high-usage invoice from the page. Do not imply that a public example covers every contract or usage case. The [focused diagnostic guide](/guides/pricing-page-hides-the-value-metric/) provides the correction process and a working evidence sheet. ### Record the decision and the limit An account may object to price because the required integration or implementation support is unclear. Discounting without resolving that concern can create a lower-priced failure. Compare the complete offer and the customer’s actual alternatives before treating every objection as a request for a concession. Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required. Use the [complete topic collection](/topics/saas-pricing/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied. ## Frequently asked questions ### What should I have completed by the end? A value-metric scorecard with customer evidence and a proposed validation test. ### Can I take the lesson without company data? Yes. Use an explicitly labelled fictional practice case. Do not present its assumptions or outcomes as customer evidence, and note what you would need to verify in a real project. ### How do I know if my work is ready? Does the unit reflect the customer's job? Can the buyer predict the bill? Can the product measure and explain usage reliably? Use the rubric to identify what is supported and what needs another check. ### Do I need to sign up for the course? No. The published lessons are free to read. Download forms are optional, and the course can be completed at your own pace.