From Product Feature to Priced Entitlement
Follow one SaaS feature from a product idea to a plan, allowance, price, entitlement check, usage event, and customer experience.
6 min readOpen field guide
See the system behind the price.
Start with the commercial decision, then follow it through the catalog, subscription, usage, and invoice.
One decision, five connected steps
Follow the full path or enter where your current decision begins.
Each route answers a different decision without repeating the same guide.
Five connected guides take one feature from its first pricing decision to a billable customer journey.
Know What Every Feature Costs with Tirdad
Build a Tirdad cost sheet, connect its charges to product usage, and see revenue, cost, and margin by feature and customer.
3 min readOpen field guide
Turn Your Pricing Description Into a Working Catalog with AI
Describe your plans, limits, and usage rules; review the result; then let Tirdad create the features, meters, prices, entitlements, and usage units behind them.
4 min readOpen field guide
How to Implement Subscriptions with Tirdad
Follow one customer from plan selection to activation, a mid-cycle upgrade, renewal, payment recovery, and cancellation—and see which system owns every decision.
5 min readOpen field guide
From Product Usage to an Invoice with Tirdad
Define a billable action, configure its meter, make retries safe, apply an allowance and overage price, and trace every invoice quantity back to the product.
4 min readOpen field guide
Patterns for products whose pricing needs a different operating model, starting with AI usage units.
Turn Different AI Actions into One Credit Balance
Map AI actions to credit costs, fund wallets from plans, deduct safely after successful work, and design renewal, expiry, top-up, and low-balance behavior.
4 min readOpen field guide
Pressure-test the model before customers, costs, regulation, or architecture expose the assumptions hiding inside it.
Your Best Customers Outgrew Your Pricing. Now What?
A small customer creates 10 reports. A large one creates 10,000. Find the value metric that lets the price grow without turning the bill into a puzzle.
3 min readRead the story
The Meter Is Accurate. The Price Can Still Be Wrong.
You counted every action correctly. The customer still disputes the bill. Learn which product events deserve a price—and which should never reach an invoice.
3 min readRead the story
Your AI Cost Is Not Your Price
A report costs you tokens, retries, storage, and model calls. The customer buys none of them. Build a price around the result without losing control of margin.
3 min readRead the story
Before the First Saudi Invoice, Four Systems Must Agree
The pricing page says SAR 299. Make sure the contract, tax decision, invoice, and payment journey all mean the same thing before the customer pays.
3 min readRead the story
One Report. Five Systems. One Number Must Survive.
A report leaves your product as one fact and crosses five billing decisions. See how to keep its identity intact until it becomes an invoice line.
3 min readRead the story