Request Pricing Model
Price per request or per 1,000 requests with margin-safe assumptions.
Quick checklist
- Define what counts as a billable request.
- Use per-1,000 units for pricing clarity.
- Model request costs with real infra data.
- Add a platform fee if fixed costs are high.
- Use tiers to avoid bill shock.
Step-by-step
- Estimate cost per 1,000 requests.
- Set a target gross margin.
- Convert to a price per 1,000 requests.
- Add tiers for higher usage bands.
- Validate with ARR and ARPA targets.
What to watch
- Bursty traffic can distort costs.
- Request-heavy endpoints need separate pricing.
- Underpriced requests create margin erosion.
Common mistakes
- Pricing per request without rounding.
- Ignoring caching and batching effects.
- Mixing read and write requests in one unit.