For product leaders.
You’re shipping new modules, new metrics, and AI features. But pricing architecture is still living on the marketing team’s website page, and the gap is widening. We build the architecture that evolves with the roadmap.
SPP designs pricing architecture from real product usage data, not from internal opinion or competitor scrapes. The value metric reflects the unit customers actually use to measure success. Packaging boundaries follow where the roadmap is heading. New modules and metrics ship with pricing built in from the start.
LevelSetter becomes the operating layer connecting product roadmap to pricebook. As the product evolves, packaging tracks. New editions ship without the cross-functional fire drill. Product leaders stop being on a different orbit than pricing.
Former B2B software CEO — built an angel-backed company ($13M raised) recognized as an Intuit Top 10 Developer. Business of Software keynote speaker. Hired SPP as a client in 2008. Joined the firm in 2013 and built LevelSetter from the problems he’d lived firsthand.
shipping cadence.
analyzed.
the product, not against it.
The roadmap ships modules. Pricing ships annually. The gap fills with discounting, packaging exceptions, and “we’ll figure that out at GA.” Product velocity outpaces pricing velocity.
When product outruns pricing.
Shipping a new module
with no pricing answer
The module is built. GA is in 90 days. Nobody has decided whether it’s an edition add-on, a metered metric, or its own SKU. Whatever you ship at launch will anchor every customer conversation that follows.
AI feature is breaking
the value-metric story
You’re adding AI on top of a seat-based product. Per-seat pricing doesn’t fit because compute scales differently than human use. The metric question is suddenly architectural and you have weeks, not quarters, to answer it.
Packaging boundaries
don’t match the product
Editions were drawn around features that customers no longer treat as differentiators. Bundles meant to drive enterprise upgrades have piled up so much value they’ve become the default purchase, training the market to skip the lower editions entirely. Marketing’s segmentation has moved on; the pricebook hasn’t.
Roadmap dependencies
on pricing decisions
Product needs to know whether to build feature X as core or as add-on. The packaging decision drives the build, but pricing isn’t ready to make it. The roadmap stalls waiting on a cross-functional pricing committee that never converges.
New value shipped daily.
Price unchanged.
Every release adds capability to the existing pricebook. Customers paying last year’s price keep getting this year’s product, plus next quarter’s roadmap on top. What you sold them is now the deal of the century, and your team leaves expansion on the table every renewal cycle as the gap widens.
SKU sprawl from
sales workarounds
The new module isn’t in the pricebook yet, but sales needs to close the deal that walked in last week. Reps invent product codes in the CRM and quote them. Multiply by every rep every quarter, and the pricebook becomes a thicket of off-book SKUs that finance can’t reconcile and the deal-desk can’t govern.
Product is a discipline.
Pricing rarely is.
Product is a discipline. There are product managers. There are roadmap rituals. There is a practice. Pricing typically isn’t a discipline at software companies. There’s no pricing owner, no equivalent of the product manager whose full-time job is keeping the architecture coherent. As long as one side is a discipline with an owner and the other isn’t, product will always outrun pricing.
The fix is to make pricing a discipline with an owner. SPP brings the design and ongoing expertise; your team builds the muscle. LevelSetter is the operating layer that holds the architecture between sprints. Value metric, packaging boundaries, and pricing decisions live as a living artifact your team works against. Product leaders and pricing finally operate on the same orbit.
Capabilities first.
Customer Groups follow.
Most software companies don’t have a central repository of capabilities or a synthesized list of value drivers. Yet they expect salespeople to sell from value. We step back from product usage as the starting point. Usage shows what customers do; capabilities show what they’re paying for. The four phases below capture inputs, map them across the customer mix, document the organization’s working hypothesis of value, and validate continuously.
Catalog capabilities and value drivers
Most software companies don’t have a central repository of what the product actually does for buyers, separate from what it does technically. SPP engages your team to build it together — ownership has to live with the people who’ll operate it. The catalog of capabilities paired with value drivers lives inside LevelSetter as a living artifact your team works against. It’s what you’re monetizing, and it compounds with every architecture iteration.
Map value across the customer mix
Different customers value the same capabilities very differently. SPP maps each capability against the customer mix and surfaces the patterns. Customers naturally cluster around the capabilities they value most. Those clusters are Customer Groups, the canonical SPP unit for pricing decisions.
Document the org’s hypothesis of value
Before validating anything in the field, SPP captures what the organization currently believes customers value. This belief is almost always partial, and rarely written down. We document it explicitly so it can be tested against how customers actually behave.
Validate continuously through LevelSetter
LevelSetter operates the architecture day-to-day and closes the gap between what the organization believes and how customers behave. Each customer interaction produces a validation signal. The architecture tunes packaging and pricing as the gap closes. That continuous validation is what reduces strategic pricing risk.
You know your product better than any outside firm. Surveys come back 2x what the market actually pays because they ask the wrong people the wrong way at the wrong depth. And when the engagement ends, your team hasn’t built anything they own.
Skipping the homework isn’t outsourcing pricing strategy. It’s hiring a substitute to take the final exam in your major. That’s the blind spot. Continuous monetization is built bottom-up: the validation process is the alignment process, and the team doing the work owns the architecture afterward.
BambooHR: How a pricing overhaul changed the trajectory of the business.
Hear how BambooHR’s leadership partnered with SPP to restructure packaging and pricing — and what it meant for revenue, sales confidence, and the ability to invest in what came next.
Read the case study →Architecture review.
$800M follow-on.
A software vendor wanted to charge more as customers realized more value, but couldn’t measure usage. SPP’s architecture team mapped how the platform was built and scaled. An existing element of the infrastructure surfaced as a pricing lever — the gearing was already there. An $800M follow-on contract closed within the year.
Frequently asked questions
Pricing as a discipline.
Sprint by sprint.
If your packaging can’t keep up with the roadmap, the answer isn’t another consulting deck. It’s pricing as a discipline your team owns. Renewable. Each renewal is one we earn.