# AI SaaS Pricing Calculator

URL: https://www.paydude.io/resources/tools/ai-saas-pricing-calculator
Type: Free interactive calculator
Summary: Know your inference cost per user? Work out the minimum price for an 80% gross margin, with payment fees included in cost of goods sold.

Model cost calculators tell you what inference costs. The decision you actually face is what that forces your price to be — and payment fees, which almost every AI cost model leaves out, are part of the answer.

## Summary

Price is not cost plus margin — it is cost divided by (1 − margin − fee rate). Payment processing belongs in cost of goods sold and is routinely omitted. AI products often run at 50–70% gross margin, well below the 80%+ SaaS norm. Usage-based costs with flat-rate pricing means your worst customers set your margin.

## Why you divide rather than add

The intuitive move is to take an $8 cost, want an 80% margin, and charge $8 × 5 = $40. That is close, but it ignores that payment fees are themselves a percentage of the price you have not set yet.

```text
price = (variable cost + fixed fee) / (1 - fee rate - target margin)

      = (8.00 + 0.30) / (1 - 0.029 - 0.80)
      = 8.30 / 0.171
      = $48.54
```

$48.54, not $40. The gap is entirely payment fees, and it grows as the target margin rises.

## AI margins are not SaaS margins

**Typical gross margin by product type**

| Product | Typical gross margin | Main COGS |
| --- | --- | --- |
| Classic SaaS | 80–90% | Hosting, support |
| AI-assisted SaaS | 65–80% | Inference plus hosting |
| AI-native product | 50–70% | Inference dominates |
| Heavy generative (video, agents) | 30–60% | Inference dominates heavily |

This matters for expectations as much as pricing. An AI product at 65% margin is not underperforming — it is a different cost structure, and investors and founders alike often benchmark it against the wrong number.

> **Flat pricing on usage-based costs:** Charge one price while paying per token and your heaviest users set your margin. Either cap usage, add a usage component above a threshold, or price for your heaviest realistic user rather than your average one.

## Levers other than price

- **Route by difficulty.** Most requests do not need your largest model.
- **Cache aggressively.** Repeated prompts and shared context are often a large share of spend.
- **Trim context.** Tokens you send every call are the ones you pay for every call.
- **Lower the payment rate.** At a $49 price point, moving from 2.9% + 30¢ to 2.6% + 25¢ recovers about 0.4 points of margin — small, but it requires no engineering.

**Take payment fees out of COGS** Lower published rates on both the percentage and the fixed fee. — [See Paydude pricing](https://www.paydude.io/pricing)

## Frequently asked questions

### Why divide by (1 − margin − fee rate) instead of multiplying the cost?

Because payment fees are a percentage of the final price, which you are still solving for. Multiplying cost by a margin multiple ignores them and leaves you short. At an 80% target and 2.9% fees, the difference on an $8 cost is roughly $40 versus $48.54.

### What gross margin should an AI product target?

50–70% is realistic for AI-native products where inference dominates COGS, versus 80–90% for classic SaaS. Insisting on 85% usually means either underpricing risk or capping usage so tightly that the product stops being useful.

### Should I charge per seat or per usage for AI features?

If your costs are usage-based, some usage component protects your margin. A common structure is a flat price covering typical usage plus overage above a generous threshold — predictable for the customer, safe for you.

### Do payment fees really matter next to inference costs?

Less than inference, but they are not negligible and they are far easier to change. At a $49 price, 2.9% + 30¢ is about $1.72 — roughly 3.5% of revenue, straight out of gross margin, with no engineering work required to reduce it.