◆ PROFITABILITY GUARDRAILS FOR AI SAAS
Your most active user might be your least profitable.
Flat subscriptions meet metered AI costs, and somewhere in your customer list the math turns negative. MarginFuse connects Stripe revenue to per-request AI cost, shows you exactly who’s underwater, and stops loss-making requests before they run. Connect today, know your real margin by next week.
○ No credit card required · prompts and responses never leave your app · free until you activate protection
SUPPORT COPILOT · AUG
○ DRY-RUN
THIS WEEK · DRY-RUN FINDING
3 customers had negative margin. Protection would have saved $184.00 EST.
| CUSTOMER | REVENUE | AI COST | MARGIN |
|---|---|---|---|
| Nova Labs | $29.00 | $35.67 | ▼ −23.0% |
| Pixel North | $99.00 | $62.20 | ◆ 37.2% |
| Acme Studio | $99.00 | $18.40 | ● 81.4% |
○ Dry-run: Nova Labs would have been downgraded at $25.00 - $8.90 EST prevented, nothing blocked.
REPRESENTATIVE EXAMPLE · USD · ONE WEEK - NOT YOUR DATA
WORKS WITH
STRIPE
OPENAI
ANTHROPIC
TYPESCRIPT SDK · ONE TRACK CALL PER AI REQUEST
Don’t take our word for it. We’ll show you a whole company. Open the live demo: a fictional AI support product, 65 customers, one month of traffic, every simulated protection decision inspectable.
Explore the demo →THE PROBLEM
You know the total bill. You don’t know who caused it.
Your OpenAI invoice is one number. Your Stripe revenue is another. Between them sits the only question that decides whether you’re running a business: which customers, plans, and features make money, and which quietly don’t.
$29 − $35.67 EST
One heavy customer
pays a flat subscription and quietly costs more than they bring in - every single month.
$0.157/req EST
One expensive feature
image generation costs 26× your cheapest feature - and nothing stops a 150-request day.
◆ 48.8% EST
One mispriced plan
looks fine on averages while its heaviest users drag gross margin below half.
REPRESENTATIVE EXAMPLES · USD · MONTHLY
WHAT YOU GET
See margin per customer, not per invoice.
Every customer, plan, and feature gets a real gross margin, computed from your own traffic. Averages hide your worst customers. This doesn’t.
Catch the leak before it compounds.
A customer who costs $6 more than they pay isn’t a crisis in week one. In month six, at scale, it’s your runway. Alerts fire when margin crosses your target, not after the invoice lands.
Stop losses without touching production.
Policies run in dry-run first: you watch what would have happened, every decision and every dollar, before anything is allowed to act. When you activate, it’s reversible. If MarginFuse is ever unreachable, your requests proceed unchanged.
HOW IT WORKS
See the leak free. Fix it when you’re ready.
01
Connect Stripe
Read-only. Customers, plans and revenue - the money side of margin.
02
Report AI usage
One TypeScript call per AI request:
mf.track({ customerId, feature, model, usage })
03
Watch a week of truth
Profit by customer, plan and feature, plus what every policy would have done. Production untouched.
○ DRY-RUN
04
Activate protection
Alert, downgrade, require a top-up, or block - simulated first, reversible always, fail-open by default.
● PROTECTION ON
NOT ANOTHER OBSERVABILITY TOOL
- LLM observability answers: which prompts are slow, which traces failed.
- Cloud FinOps answers: what did infrastructure cost.
- Billing answers: did we collect the invoice.
- MarginFuse answers: which customers, plans and features make or lose money - and what will stop the losses.
PRIVACY BY ARCHITECTURE
MarginFuse never sees prompts or responses - identifiers, usage metadata, costs, and revenue only.
- ● We receive: customer ID, feature, provider, model, tokens/cost - the metadata needed to attribute cost and decide policies.
- ■ We never receive: prompts, responses, or your customers’ content. There’s no toggle to send them - the SDK has no field for it.
Decisions are fast enough for request time. If MarginFuse is ever unreachable, your requests proceed unchanged - fail-open by default.
$184.00 EST
would have been saved last week - measured before you activate anything.
REPRESENTATIVE EXAMPLE · USD · ONE WEEK
No marketing math. Every number MarginFuse shows is labeled OBSERVED EST PROJECTED or REALIZED. A savings report is built by replaying your own recorded traffic. Inspect every decision behind it before paying a cent.
QUESTIONS
Asked before signing up.
- What does dry-run mean?
- Dry-run is MarginFuse's observe-only mode. It computes margin per customer, plan and feature, and simulates what every policy would have done - but changes nothing in production. No request is blocked or altered until you explicitly activate protection.
- Do I need a credit card to start?
- No. Dry-run is free and never asks for a card. You pay - from $29/mo - only when you activate protection.
- What happens when protection acts on a request?
- Your app receives the decision - downgrade to a cheaper model, require a top-up, or block - and stays in control of how to present it to the user. Every decision is logged and inspectable, every policy is reversible, and you can watch a policy run simulated in dry-run before it goes live.
- What if MarginFuse goes down?
- Your requests proceed unchanged. The SDK fails open by default: if a decision doesn't come back in time, your app continues as if MarginFuse wasn't there.
- Can MarginFuse see my prompts or my customers' content?
- No - by architecture, not by policy. The SDK has no field for prompts or responses. We receive identifiers and usage metadata only: customer ID, feature, provider, model, tokens and cost.
- How long until I see results?
- Margin data appears as soon as your traffic flows: connect Stripe read-only and add one track call per AI request. After about a week of traffic you get your first dry-run savings report, built by replaying your own recorded requests.
Stop users from burning your margin.
One track call. One week of data. Your real margin. Free in dry-run, no credit card. $29/mo when you’re ready to protect.