Usage-Based Pricing 2.0

Summary

Usage-based pricing (UBP) is not just a billing model — it fundamentally restructures the vendor-customer relationship around shared success. The core framework:

Choosing a pricing metric. Not every product has a good usage metric. The ideal metric must:

1. Strongly correlate with customer-perceived value
2. Share in the customer’s success (not discourage adoption)
3. Allow starting small and scaling over time
4. Consistently increase month-over-month for the average customer
5. Be feasible to monitor and meter

The compound interest analogy. UBP grows like compound interest — slower to the first $1M (you must wait for customers to launch, succeed, and grow) but accelerating afterward. Unlike fixed subscriptions recognized immediately, usage billing is recognized in arrears.

Organic vs. inorganic expansion. Two distinct motions:

• Organic: customers use more of what they already bought. Owned by Customer Success. The key lever is a patient zero analysis — reverse-engineer behaviors of your best customers and replicate them across the base.
• Inorganic: customers add new products, use cases, or business units. Requires a commercially-minded AE or AM partnering with CS.

Organizational alignment. The entire company must orient around customer success: don’t treat bookings as the holy grail, be willing to run pilots/POCs, invest in product adoption UX (not just features), simplify pricing so it doesn’t block adoption, and offer generous support. New Relic’s insight: “if we aren’t focusing every function around making customers successful, we aren’t living up to our commitments.”

Comp alignment. Pay bounties on new lands regardless of initial deal size to keep reps closing fast. Don’t incentivize over-commitment.

Relevance to projects:

• 01-projects/data-marketplace/index — A data marketplace is a natural fit for UBP. The metric could be datasets accessed, rows queried, or API calls. The compound interest dynamic means early revenue will be modest but should accelerate. The patient zero analysis is directly applicable: find which early data buyers expanded usage fastest and why.
• 01-projects/squarely-puzzles/index — Not a natural UBP product (puzzle consumption is episodic, not monotonically increasing). Better suited to pack-based IAP or subscription. See 06-reference/2026-04-03-b2b-saas-pricing-masterclass on value metrics.
• 01-projects/phdata/index — Consulting is inherently usage-based (billable hours) but the expansion motion is inorganic (new projects, new stakeholders). The patient zero analysis concept applies: which client engagements expanded into multi-project relationships, and what behaviors drove that?

Connects to 06-reference/2026-04-03-four-fits-framework on model/market fit — UBP works when market segments have highly variable usage patterns. Connects to 06-reference/2026-04-03-nathan-barry-saas-scaling-profit-sharing on aligning team incentives with growth. See also 06-reference/2026-04-03-the-e-myth-revisited on building systems that compound.

Open Questions

• For 01-projects/data-marketplace/index, what is the right usage metric? Per-dataset, per-row, per-API-call? Which correlates best with perceived value?
• How do you handle the “slow start” problem of UBP for a bootstrapped company that needs near-term revenue? Hybrid model (base subscription + usage)?
• The patient zero analysis is a powerful concept — what does it look like applied to 01-projects/phdata/index consulting clients?