Reading time:

10 min read

|

Last updated:

AI Product Pricing Page Design: Credits, Seats, Usage

Pricing page design for AI products: how to show credits, seats and usage so buyers can pick a plan, plus a rewrite checklist you can ship this week.

We design websites and products that make AI companies more money.

Siddarth Ponangi

Founder, Studio Maydit

We design websites and products that make AI companies more money.

Web and product design for AI companies

We help AI companies build fast, clean, and conversion-focused websites and products.

A good pricing page for an AI product tells a buyer what their money gets them in the thing they came to make, not in credits, tokens or seats. Show the unit in plain words, translate every plan into real output, say what happens when the credits run out, and give each button a different job.

Most AI founders price by credits or usage because inference costs them money on every request. That is a fair reason to charge that way. It is not a reason to make the buyer do the maths. The founder knows exactly what a credit buys, because he built the meter. The person on the pricing page has never seen it before, and they are deciding whether to pay.

The pricing page that asks for arithmetic

Picture an AI voiceover tool. The free plan gives you 50 credits. You make three voiceovers, and on the fourth a modal slides up. It reads You are out of credits, with one button: See plans.

The pricing page has three cards. Starter is $19 a month with 500 credits. Creator is $49 a month with 2,000 credits and a purple Most popular badge. Team is $39 per seat a month with 1,500 pooled credits per seat. Above the cards sits a Monthly and Yearly toggle, with a small green tag that says two months free. Every card has the same button, Get started.

Under the cards, in grey 12px text, is the actual price. One credit equals 1,000 characters of standard audio. Studio voices cost two credits per 1,000 characters. Voice cloning costs 25 credits per voice. Unused credits expire at the end of each billing cycle.

Now picture who is reading it. She edits a weekly explainer video for one client, four a month, each with about ten minutes of narration in a Studio voice. To choose a plan she has to know that ten minutes of speech is roughly 1,500 words, that 1,500 words is about 9,000 characters, and that a Studio voice doubles the cost. That is 18 credits a video and 72 a month. Starter covers her many times over. Nothing on the page says so. The badge points her at Creator. So she either pays for a plan four times bigger than the one she needs, or she closes the tab to think about it and never comes back.

Why he keeps changing the price and not the unit

The founder can see the leak. His analytics show pricing as one of the most visited pages among free users, and most of those sessions end there. So he changes the thing he can see. Creator went from $49 to $39 and back again this quarter. He added a What is a credit answer to the FAQ, 180 words long, and then a second one about Studio voices.

He also answers the emails himself. On a Sunday night he replies to three people asking how many credits they need, does the maths for each one, and names a plan. Most of them buy. He reads that as proof the price is right and the traffic is wrong. It is proof of something else. The price was never the problem. The page could not do what he did in each reply, which is turn a credit into a number of videos.

He knows his product and nobody else does. On the pricing page that gap is not about flow or screens. It is about a unit of measure that only one person in the room can convert.

What a confusing pricing page costs an AI company

For a product-led company the pricing page is the last screen before revenue. Benchmarks measured on SaaS and product-led companies put freemium free-to-paid conversion at a median of 2 to 5 percent. That number is already small. Every buyer who reaches the page ready to pay and leaves because they cannot size a plan comes out of that 2 to 5.

An AI company pays for that loss twice. The free credits were not free to serve. Inference sits in cost of goods, which is why AI product builders average around 52 percent gross margin against 70 to 80 percent for traditional software. Every free user who hit the wall and walked away was served at real cost and returned nothing.

The buyer who overpays is not a win either. When her unused credits expire at the end of month two, she downgrades or cancels. And your buyer is now comparing units across vendors. In Growth Unhinged's 2026 survey of 230 B2B software and AI companies, 29 percent already used AI credits and another 33 percent planned to add them within a year. No two of those credits mean the same thing, so every page that leaves the unit unexplained adds to the same fog.

Price in credits, sell in outcomes

The usual pricing page advice is three tiers, a highlighted middle plan and an expensive top plan that makes the middle look cheap. That advice was written for seat-based software, where a buyer already knows how many people are on their team. For a credit-priced AI product, the tiers are rarely the problem. The unit is.

So keep the credits, because they protect your margin. Stop leading with them. Put the outcome in the largest type on each card and the credits underneath it. Starter becomes About 25 ten-minute Studio voiceovers a month, with 500 credits in smaller text below. Creator becomes About 110. The number is an estimate, and the card should say so. An honest estimate is still far more useful than an exact figure nobody can read.

Pick the outcome your buyers already count. For a voiceover tool that is minutes of audio. For a coding agent it might be tasks or pull requests. For a research tool it might be reports. If you cannot name the outcome in one short phrase, that is worth knowing before you touch the layout, because the same confusion is waiting inside the product too.

Seats, usage or both: price what the buyer can predict

Seats are easy to predict and hard to justify when one person does most of the work. Usage is fair and hard to predict. Most AI products end up with both, a seat price plus a pool of credits, and that is where team buyers get nervous.

The fear is a surprise bill. A Zylo survey of 218 IT leaders found 78 percent had seen unexpected charges on a SaaS bill because of consumption or AI pricing. The person approving your Team plan has probably been burned once already. A seat price with a meter on top reads to them like a risk.

The decision rule is simple. Charge by seat when value grows with the number of people using it. Charge by usage when value grows with the amount of work done. When you combine them, put a hard answer next to the meter. Say what happens at 80 percent of the pool, whether work stops or keeps going at the limit, and who gets the email. A spend cap the admin sets is often worth more to this buyer than a lower price.

When a pricing calculator helps and when it hides the answer

The common fix for a confusing unit is a slider. Drag it to your monthly volume and the page picks a plan. It works when the buyer already knows their volume in your unit, such as a developer who knows their monthly API calls. For everyone else it moves the arithmetic from the grey footnote into a nicer box. A slider labelled Characters per month still asks her to count characters.

If you build one, make the input the outcome. How many videos a month, and how long is each one. Pre-fill it with a typical buyer, show the recommended plan with the credits it uses, and show the leftover credits so she can see there is room. A calculator should answer the question she arrived with. It should not ask her a new one.

A pricing page rewrite you can ship this week

  • Write down, in one phrase, what a buyer makes with your product. Minutes of audio, tasks, reports, images. Use that phrase as the headline number on every card.

  • Convert each plan into that outcome using your real median usage. Show it as an estimate, with the credits in smaller text below.

  • Move the credit rules out of the grey footnote. Put a short table right under the cards: what each action costs, in credits and in plain words.

  • Say what happens at the limit. Does work stop, slow down, or bill extra? Do unused credits roll over? One sentence each, next to the plan it applies to.

  • Give each button a different label. Start free, Choose Creator, Talk to us about Team. Three identical Get started buttons tell the buyer nothing about the difference.

  • Carry the answer into the product. The out of credits modal should show how much she used, what it made, and which plan fits that use. It should not only send her to a page of cards.

  • Read the last ten emails asking how many credits someone needs. Every question in them is a line missing from the page.

The pricing page is part of your onboarding, not a separate marketing page. Most people reach it from inside the product, at the moment the free credits run out, so it shares a job with your AI onboarding and the first screens. If you want to see how the pricing page sits among the other pages that decide conversion, this breakdown of SaaS website conversion rates covers the hero and the proof as well. And if you would rather compare outside help for this one page, there is a shortlist of studios that design pricing pages.

Where the pricing page meets the product

Studio Maydit is a product and web design studio for AI founders in the US, UK and Europe. Much of our work sits where this post does, on the screens where someone decides whether to pay and stay: the first run, the out of credits moment and the page it opens. A fixed-scope project runs three to four weeks and ends with a diagnosis of what is leaking in the product, pricing included. If your buyers keep emailing you to ask which plan they need, book a 30 minute call with us.

Frequently Asked Questions

Table of Contents
Scroll to view headings
0%