SAYLOR The result you are building
A versioned pricing model with a clear billable unit, customer segments, cost and margin by usage cohort, packaging, limits, overage/abuse rules, sensitivity scenarios, and a measured launch experiment.
Use this guide when:
- You are pricing an API, SaaS, x402 endpoint, subscription, or usage product.
- Revenue grows while cash or infrastructure margin worsens.
- Free users, heavy users, support, refunds, or provider fees distort the headline price.
Do not use it as a substitute for:
- Copying a competitor's tiers without knowing your value and costs.
- Using average gross margin while a small usage cohort creates unbounded loss.
Before you change anything, collect: customer jobs/alternatives/consequence/frequency/willingness evidence; billable unit and usage distribution by segment; full cost breakdown (model/API/data/compute/storage/network/payment/refund/support/acquisition); price, discounts, taxes/fees, quota, overage, contract and payment timing; cohort contribution, cash timing, sensitivity, and abuse evidence.
Understand the system before pricing it
- Terms must map to observable events. Scope, acceptance, payment, support, and ownership only work when each obligation has an owner, date, artifact, and pass/fail condition.
- Cash flow outranks informal assumptions. A promising conversation is not collected revenue. Record actual state.
- Revenue is not contribution margin. Subtract all variable and attributable service costs, paid failures, payment fees, support, credits, and refunds from collected revenue by cohort.
- The pricing metric shapes customer behavior. Per-seat, task, result, API call, data volume, compute, success, or fixed tiers shift risk between seller and buyer — choose a unit customers can predict and you can meter.
Evidence-to-decision map
| Evidence | Likely layer | First decisive check | What the result means |
|---|---|---|---|
| Revenue rises, cash falls | Cost/cash timing | Reconcile collected cash and cost by cohort | Upfront provider spend, delayed collection, refunds, or negative-margin usage is consuming cash |
| One customer drives losses | Usage distribution | Plot contribution by account and work unit | Average pricing hides heavy-tail cost or abuse |
| Conversion low despite interest | Packaging/value | Interview and test price/metric/friction | Buyer cannot predict value, unit, commitment, or risk |
| Churn after first bill | Expectation/metering | Compare quote, usage visibility, invoice | Pricing or limits feel unpredictable, or output value is weak |
| Agent endpoint sells but loses money | Paid failure economics | Include retries, cache, provider failures, settlement, support | Price covers successful compute only, not full delivered-result cost |
Step-by-step procedure
- Define the paid outcome and segment. State the customer job, measurable result, frequency, consequence, alternatives, and who owns budget. Separate materially different value/cost segments. *A buyer can explain what they pay for and why it matters.*
- Choose a measurable pricing unit. Compare seat, task, result, call, token, dataset, compute, asset, success, or tier units for predictability, value alignment, meter integrity, and abuse risk.
- Build full cost-to-serve. Allocate provider/model/data, compute, storage, network, payment, failed calls, refunds, support, onboarding, fraud, and attributable operations by task and cohort. *Collected revenue minus full cost reconciles to contribution by cohort.*
- Model distribution and limits. Use p50/p90/p99 usage, concurrency, failure, support, and retention. Set included use, hard/soft limits, overage, spend caps, fair use, and approval. *Worst-case authorized usage stays inside margin and capacity limits.*
- Create packages and guardrails. Make tiers distinct by outcome, freshness, volume, SLA, support, integrations, or rights. State taxes, cancellation, refund, overage, and usage visibility clearly.
- Run sensitivity and cash scenarios. Vary price, conversion, churn, expansion, provider cost, payment delay, refunds, support, and usage mix. Model base/downside/stress without fake precision.
- Test, measure, and revise. Use transparent pilot pricing; track activation, conversion, usage, result quality, support, cohort margin, churn reasons, and willingness interviews. Version changes and protect existing commitments.
Worked example
Starting problem: An x402 token-risk endpoint charges $0.02 while upstream calls and failed responses average $0.031.
Evidence collected: The endpoint fulfills unique uncached requests; 4% of paid calls fail after settlement; support and payment fees are not allocated; heavy agents retry the same asset repeatedly.
Decision: The product has negative contribution despite working technically. Add caching/idempotency, improve paid-failure handling, and price above p95 delivered-result cost plus target margin.
Actions taken: Measured cost by successful paid result; cached within declared freshness by chain/mint/version; returned stored result for duplicate payment ID; tested a higher price and a bulk plan with limits.
Proof of completion: Each cohort has positive contribution under stress limits, price and freshness are transparent, and no paid retry repeats unnecessary upstream cost.
Acceptance scoreboard
- Paid outcome, customer segment, alternatives, and value evidence are explicit.
- Pricing unit is predictable, meterable, and aligned with value and cost.
- Full cost-to-serve and collected cash reconcile by cohort.
- Usage distribution, paid failures, support, abuse, discounts, and refunds are included.
- Tiers, limits, overage, cancellation, and usage visibility are clear.
- Pilot metrics, stress gates, owner, and versioned pricing decisions are recorded.
Decision rule: proceed only when every required acceptance check is supported by direct evidence, rollback is available, and remaining risk is explicitly owned. Unknown is not a pass.
For agents
This guide's structured-delivery boundary: human-readable use is free; the paid product for agents/automation is this same body delivered as deterministic, versioned JSON — not a separate hidden tool. When applying this as a decision procedure, an agent should: require a versioned target (the product/environment being priced) and sanitized, timestamped evidence; respect stated constraints (budget, authority, reversibility, freshness); return a diagnosis (likely pricing failure layer, evidence, alternatives, confidence), an ordered plan, and verification checks rather than an unqualified recommendation. Refuse requests that require secrets/credentials in ordinary input; escalate rather than guess when evidence is missing or contradictory; never convert an unknown into an automatic pass.
Official reference starting points
- U.S. SBA pricing guidance — https://www.sba.gov/business-guide/manage-your-business/set-prices
- FinOps Framework — https://www.finops.org/framework/
- FTC truth in advertising — https://www.ftc.gov/business-guidance/advertising-marketing
*This material is educational operational information, not legal, tax, accounting, or financial advice. Use qualified professionals for decisions requiring those licenses.*