Pricing Generation

Pricing generation helps teams draft a starting catalog structure from a business description.

Treat generated pricing as a proposal, not a final pricing decision. Review the output with product, sales, finance, and customer success before launch.

What it can generate

• Suggested product or plan names.
• Tier structure.
• Monthly and annual price points.
• Feature limits or usage allowances.
• Add-on ideas.
• Packaging rationale.

Review criteria

Question	Why it matters
Does the price match buyer value?	Pricing should map to customer outcomes.
Are usage limits measurable?	Billing needs reliable units.
Can support explain the tiers?	Confusing packaging creates tickets.
Does finance approve discount room?	Sales needs margin and approval rules.
Can the product enforce limits?	Billing promises should match product behavior.

From generated pricing to production catalog

1. Generate a draft pricing strategy.
2. Remove tiers or features that are not launch-ready.
3. Create products and prices in Floatless.
4. Add usage units for metered items.
5. Create test customers and subscriptions.
6. Run bill run preview.
7. Review generated invoices.
8. Launch only after billing and product behavior match.

Common pitfalls

Pitfall	Better approach
Too many tiers	Start with two or three clear tiers.
Vague usage unit	Use a measurable unit such as seat, GB, API call, or transaction.
Overpromised feature limits	Only include limits the product can enforce or report.
No annual plan policy	Decide annual discount, renewal, and cancellation rules.

Related docs

• Pricing models
• Products
• Usage-based billing
• Launch checklist