SaaS Pricing Consultant: Packaging First, Number Last

Segmentation before structure: which customers get which value, and what usage dimension tracks that value. Then packaging: plan boundaries, what is gated, what is metered. Then the price metric, per seat, per usage, per outcome. The number comes last, tested against willingness-to-pay evidence, with a migration plan for existing customers.

The migration plan is where engagements earn their fee. A pricing change applied bluntly to an installed base burns trust and support capacity; sequenced grandfathering, cohort by cohort, converts the same change into expansion revenue. Ask any candidate consultant for their migration playbook before their pricing framework.

Ask what data the recommendation will rest on: win-loss interviews, usage distributions, willingness-to-pay research, competitor benchmarks with dates. My own standard is public: this site publishes the Fractional Rates Index, market pricing research across 1,127 providers, because I hold pricing recommendations to evidence I would publish.

The category has a benchmark problem: most pricing advice cites the same recycled percentages with no dataset behind them. A consultant with an evidence discipline shows you the raw distribution, names sample sizes and dates, and marks which claims are verified against which are hypotheses to test. Anything else is confident opinion.

Three triggers: a funding round approaching, because pricing power is diligence material; NRR flat while usage grows, because the metric is leaking compounding revenue; and a major packaging-dependent launch. Outside these, pricing is important quarterly work inside product strategy, not an emergency, and rushing it produces the blunt migrations that burn customers.

Five artifacts in layer order: a segmentation read on who gets which value; a packaging map of plan boundaries; a price-metric recommendation with the usage data behind it; the number, tested against willingness-to-pay evidence; and the migration plan that moves existing customers without burning them. The plan is where fees are earned.

Expect the artifacts to be auditable. Every recommendation should trace to data you can open: win-loss interviews with counts, usage distributions, research with sample sizes and dates. My own standard for this is public, this site publishes its market research with methodology attached, and it is the standard worth demanding from anyone who prices your product.

Scoped pricing projects price inside the published monthly band of $2,000 to $10,000; inside embedded product leadership it is part of my published $8,000 a month. Payback arrives through the metric layer: a price metric that tracks value compounds every renewal, which is why it outranks the number itself.

The arithmetic that sells the work internally: a packaging change that lifts average revenue per account by even a few percent applies to the entire base at the next cycle, while most roadmap features apply to a segment at best. Few quarters of product work touch as much revenue per hour of effort as the pricing layers do.