What SaaS Pricing Teaches Post-Purchase Platforms
Key Takeaways
- The best SaaS businesses price on value delivered, not infrastructure consumed. Payment processors charge per transaction processed, not per API key issued. AI support tools charge per query resolved, not per chatbot deployed.
- Physical product platforms are often stuck in "per identity" or "per label" models borrowed from software seat licensing. This charges for infrastructure, not outcomes.
- The right unit of value for a post-purchase platform is the action: a warranty claim filed, a spare parts order completed, an ownership transfer processed. Each is a discrete, measurable moment of value delivery.
- Flat platform fees create predictability. Action-based pricing creates alignment. The best model combines both.
The Seat Licence Trap
Most B2B software started with the same pricing model: per seat, per month. It was simple. It was borrowed from office software licensing. And for decades, it worked.
Then a new generation of payment platforms arrived with a different idea: don't charge for having a payment infrastructure, charge when a payment actually goes through. A small percentage of each successful transaction, and nothing at all if nothing happens.
That single decision, pricing on value delivered rather than infrastructure deployed, changed the economics of an entire industry. It made software free to start, cheap to test, and expensive only when the customer is making money. Competitors had to follow.
The lesson took years to spread. But the best SaaS companies tended to arrive at the same conclusion: charge when the customer gets value, not when they get access.
Five Pricing Models That Got It Right
Payment Processing: Per Transaction
Modern payment processors typically charge a small percentage of each successful transaction, plus a fixed fee. Not per merchant account. Not per API key. Not per team member. The fee scales with the value delivered, which is money moved.
Why it works: The merchant's cost stays near zero until revenue flows. Growth is frictionless because pricing aligns with the merchant's own success. A small shop and a large enterprise both pay in proportion to what they process, so both can feel the deal is fair.
The principle: Price on the unit of value delivery. For a payment processor, that is a completed payment.
AI Support: Per Resolution
A growing class of AI support tools charges per resolution: a customer query that the AI answers without human involvement. Not per message sent. Not per chatbot deployed. Not per seat.
Why it works: The customer only pays when the AI does something useful. An unresolved query costs nothing. Resolution rate becomes a shared success metric, because the vendor is incentivised to make the AI better when better resolution means more revenue.
The principle: Charge for outcomes, not attempts.
Communications APIs: Per Message
Communications platforms commonly charge per SMS sent, per minute of voice, per API call. The infrastructure itself is effectively free; you pay for usage.
Why it works: A developer can prototype with a few pounds of credit, and a company sending large volumes pays in proportion. The pricing barrier to adoption is close to zero.
The principle: Make the first unit nearly free. Revenue scales with usage.
Commerce Platforms: Platform + GMV
Some commerce platforms charge a flat platform fee plus a small percentage of gross merchandise volume. The flat fee covers access to the tools. The GMV percentage aligns the platform's revenue with the merchant's success.
Why it works: The flat fee is predictable and budgetable. The GMV percentage means the platform earns more when the merchant sells more, creating genuine incentive alignment. Merchants tend not to resent the percentage when the platform is visibly driving the sales.
The principle: Flat base for predictability. Variable component for alignment.
Cloud Infrastructure: Per Request
Cloud infrastructure is typically billed per compute-second, per request, per gigabyte transferred. You pay for what you use, and idle infrastructure costs little or nothing in theory.
Why it works: No upfront capacity planning. No wasted spend on unused servers. Costs track closely with actual usage.
The principle: Don't charge for capacity. Charge for consumption.
What These Models Have in Common
| Model | Charges for | Doesn't charge for |
|---|---|---|
| Payment processing | Completed transaction | Having an account |
| AI support | Resolved query | Unanswered queries |
| Communications API | Message sent | Platform access |
| Commerce platform | Platform + sales made | Products listed |
| Cloud infrastructure | Resources consumed | Resources provisioned |
Every model charges for value delivered. None charges for infrastructure deployed. The customer pays when something useful happens, not when something could happen.
Where Physical Product Platforms Got Stuck
Many connected product platforms, including the current generation of DPP, QR, and warranty management tools, tend to price on one of two dimensions:
Per identity / per tag: You pay for each product unit that has a digital identity. A given number of identities maps to a given monthly tier. Hit the limit and you upgrade.
Per seat: Traditional helpdesk pricing, a flat charge per admin user per month.
Both models charge for infrastructure, not value. And both can create problems at scale:
The identity ceiling problem
A power tools manufacturer shipping a large annual volume of units needs an identity for each one. Many platform tiers cap well below that volume, so the manufacturer is forced into an enterprise conversation before the product has proved its value, because the pricing model punishes manufacturing volume, not because the platform can't handle it.
The equivalent in a payment processor's world would be charging per credit card issued rather than per transaction processed. No payments company would do this, because the card is infrastructure and the payment is value.
This mirrors the challenge in connected product platforms: pricing models that treat infrastructure (identities, labels) as the billable unit instead of outcomes. This is particularly painful for manufacturers at scale, where spare parts revenue and product identity are directly linked to transaction volume.
The "success penalty" trap
Suppose you price per warranty registration, and the platform increases registration rates substantially. The customer's bill rises in step. The platform's success becomes the customer's cost increase. That is misaligned.
Imagine if a payment processor charged more when your conversion rate improved, or if an AI support vendor charged more when its AI resolved more queries. The incentive would be backwards.
What a Post-Purchase Platform Should Charge For
If the SaaS pricing lesson is "charge for value delivered," the question for post-purchase platforms is: what is the unit of value?
Here are the candidate actions, each a discrete, measurable moment where a physical product platform delivers value to the brand:
| Action | Value to the brand | Analogous SaaS model |
|---|---|---|
| Warranty claim processed | Support cost avoided, customer retained | Per-resolution |
| Spare parts order completed | Revenue captured directly | GMV percentage |
| Ownership transfer processed | Second-owner relationship acquired | Per-transaction |
| AI support query resolved | Phone call deflected | Per-resolution |
| Product registration captured | Known customer acquired, warranty activated | Free (top of funnel) |
Notice what is absent from this list: "identity created." Creating a digital identity for a product is infrastructure. It is cheap to host. It delivers no value until someone does something with it.
The valuable actions are the ones that happen after the scan: registering, claiming warranty, ordering parts, transferring ownership, getting AI support. These are the transactions. These are where the pricing should anchor.
The Hybrid Model
The SaaS companies that get pricing right tend not to use pure consumption models. They combine a flat platform fee with action-based pricing: a predictable base for access, plus a variable component that scales with usage or outcomes.
For a post-purchase platform, the hybrid looks like this:
Flat monthly fee covers: platform access, unlimited product identities, unlimited scans, product experience hosting, basic analytics, DPP data hosting. This is the infrastructure. It should be predictable and simple.
Action-based pricing covers: warranty claims processed, AI support resolutions, spare parts commerce (a GMV percentage), ownership transfers. These are the value-delivering moments. They should scale with the brand's success.
Registrations are always free. Registration is the top of the funnel. Charging for it would be like a commerce platform charging per product listing: it suppresses the behaviour that drives everything downstream.
This model creates the right incentives on both sides. The platform is motivated to increase registrations (more top-of-funnel), improve AI resolution rates (more revenue per query), and drive spare parts discovery (GMV growth). The brand pays in proportion to value received.
The Pricing Conversation Is a Positioning Conversation
How a platform prices reveals what it believes its value is.
A platform that charges per identity believes its value is being a database. A platform that charges per seat believes its value is being a tool. A platform that charges per action believes its value is delivering outcomes.
For physical product brands evaluating post-purchase platforms, the pricing model is a signal. The platform that charges when your customer registers, your warranty claim gets processed, and your spare part gets ordered is telling you: we succeed when you succeed.
The platform that charges for a fixed block of identities whether anyone scans them or not is telling you something different.
FAQ
Q: Doesn't action-based pricing make costs unpredictable? Not if the model includes generous included allowances. Most SaaS hybrid models include a base allocation (for example, a set number of warranty claims per month in a given tier) with overage only above that. Most customers never hit overage. The base is predictable; the variable component catches outliers.
Q: Should registrations really be free? Yes. Registration is the moment a brand acquires a known customer. Charging for it suppresses the behaviour that drives all downstream value: warranty claims, parts orders, support queries, ownership transfers. It is the top of the funnel, not the billable event.
Q: How does this apply to DPP compliance pricing? DPP data hosting is infrastructure, so it should be covered by the flat platform fee, or offered as a flat add-on. The value is not in hosting the data; it is in what happens when a consumer or regulator accesses it. The access event is the action worth tracking.
Q: What about enterprise pricing? Enterprise customers typically prefer committed spend with volume discounts, similar to reserved-capacity cloud pricing. The action-based model still applies, but with negotiated per-action rates and annual commitments rather than monthly pay-as-you-go.