MCP, auth & payments

Usage-Based Pricing

Billing tied to actual consumption rather than seats — the model most agent products lean toward.


Usage-based pricing charges customers for what they actually use, not for how many seats they buy. You pay per call, per lead, per action — billing tracks consumption.

Seat licenses charge the same whether someone logs in daily or never. Usage-based pricing only rings the register when real value happens, so cost scales with results.

Why it matters for the ChatGPT funnel

The buying journey now starts inside ChatGPT and Claude, where there are no seats and no logins. A buyer asks a question, gets an answer, and acts — once.

That single moment of intent is hard to bill against with seat pricing. There's no recurring user to charge. There's only the action: a booked meeting, a captured lead, a tool fired at the right time.

Usage-based pricing fits this world because it bills the outcome, not the login. You pay when the assistant actually converts demand into pipeline — not for access nobody used.

How drio fits

drio runs on this logic. You don't buy seats to show up in AI answers; you pay per booked lead the assistant delivers inside the chat.

It's the same idea as pay-per-call, pushed all the way to the result that matters to a demand-gen team. Cost tracks pipeline, so the spend only grows when the booked meetings do.

Win the answer, not just the ranking

drio turns the ChatGPT and Claude conversations your buyers are already having into booked calls. Build the app that gets you picked.

Sell inside ChatGPT