Find your pricing model. It's already built.

Open your Claude bill. Every model has its own rate — Fable 5 costs a multiple of Haiku — and what the model writes costs more than what you send it, because generation is the expensive part. Repeated prompts are cheaper, non-urgent jobs are cheaper, and your monthly limits grow as your spend does. And the money moved first: you topped up, then you sent requests.

In Tirdad you build the same thing with settings, not code: a meter per model, a price for the prompt and a price for the response, cheaper rates for repeated and non-urgent work, monthly limits you set yourself, and a prepaid wallet — you collect from your customer before you pay your provider. Claude-grade pricing, zero billing code.

Open your GitHub bill: you pay per seat per month, and procurement approves it easily — headcount is known, so the invoice is known. But the machine work is counted separately: Actions minutes and storage have a monthly allowance, and past it the meter bills by the minute and the gigabyte.

You have the same problem: a five-seat account running heavy automations can cost you more than a fifty-seat one. The fix is to split it like they do — seats as the fixed base, a shared allowance for the machine work, priced overage past it. In Tirdad that's one plan: the meter attached to the subscription, nothing to build yourself.

Open Vercel's pricing page: they sell bandwidth, build minutes and function calls — things nobody can predict their own consumption of — yet the page couldn't be simpler: a free tier, a Pro tier at a fixed monthly price with generous included usage, overage billed past it, and spend caps so nobody is surprised. The tier is really usage bought upfront at a fixed price; the meter only shows up when you outgrow it.

The trick is the soft limits: a spike passes through and bills as overage, and your customer's work never stops mid-month. When the overage repeats month after month, the invoice itself becomes the best salesman for the next tier. In Tirdad you build all of it with settings — tiers, allowances, limits, overage — without a line of code.

Canva converts millions without a sales call, and the trial mechanics carry the weight: Pro opens completely for the trial window — every premium feature, not a crippled preview — the price is visible from day one, and when the window closes the same plan simply starts billing. Cancel, and the premium features close behind you; nothing migrates, because the trial was never a separate system.

That's the whole discipline: build the trial as a real plan with a time window and flag-gated features, and conversion becomes a billing-state change instead of an engineering project.

AWS built the largest infrastructure business in the world on a simple promise: no subscription, pay for what you use — per second, per gigabyte, per request. Budgets and alerts warn before spending surprises anyone, one consolidated invoice closes the month, and when a workload stabilizes, savings plans convert steady usage into committed discounts.

For agencies, APIs and any project-shaped business, the same shape keeps relationships alive through quiet months: the invoice grows with a busy month and falls to zero in a slow one, alerts protect the trust, and steady customers graduate onto committed tiers when the meter data says so.

Watch Microsoft or Salesforce sell to a bank or a ministry: nobody pays the list price. The number is negotiated in a private agreement, deployment follows security and data-sovereignty requirements, SSO and audit trails are conditions of signature — not add-on features — and at every renewal, consumption is reviewed against commitments. One product; only the terms change.

Do the same: negotiate price, limits and deployment per contract, and keep one system for all your customers. In Tirdad the agreed number is just a value on the plan — the same plan for everyone, running in your cloud or inside their infrastructure, with the same meters keeping renewal talks about numbers. New contract? A new number in settings, and the system stays as it is.