MarginGuard: Dynamic Cost-Plus Metering & Guardrails for AI-Powered SaaS

The AI margin problem nobody warns founders about before they add the feature

The mistake is trying to keep flat-rate pricing on a product that has variable costs at the atomic level. On our own AI features I stopped looking at cost-per-customer and started measuring cost-per-successful-outcome. A retry loop that finishes in 3 model calls is a different unit than one that hits max\_iterations at 15. Same "one customer request" from the invoice side, 5 times cost delta on our side. Flat pricing masks that until the fat tail eats you. The three fixes you listed all try to protect the wrong number. Raising the tier price is a lagging response to margin damage that already happened. Capping usage puts the failure mode on the customer who happens to trigger the tail case. Cheaper model routing only helps if the routing decision runs before the expensive call, which most naive implementations skip. The framing that works for us: charge for the outcome the customer wanted, not for the tokens burned getting there. Wrap the pricing around a success metric (a valid response, a booked meeting, a completed task, whatever your unit is). Then the compounding-cost tail becomes an internal reliability problem instead of a customer-facing invoice shock. Prompt caching knocks input token costs down on any repeated context, which changes the unit economics enough to matter. Cheap fix that most people ship without turning on.