How to use the Pricing Tier Planner.
Pricing tiers should reflect real customer needs and cost drivers. Give each tier a clear buyer and boundary, and avoid promising features or margins that have not been validated.
Make the workflow fit your task.
Group customers by needs and map confirmed features and limits to a small set of coherent offers. Identify cost drivers and support commitments before proposing boundaries. Keep price hypotheses separate from validated willingness to pay and actual margins.
- What you provide
- Customer segments, product entitlements and costs.
- What you get
- Tier packaging options with assumptions and trade-offs.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Confirmed capabilities: individual exports, shared workspaces, priority support. Propose packaging for solo users and teams; prices and support response times are unvalidated.
Completed example
Solo — individual workflow with exports. Buyer: one person managing their own work. Team — exports plus shared workspaces. Buyer: people coordinating shared work. Priority support — optional service proposal; define coverage and response commitment before offering it. Prices: not set. Validate customer demand, support cost and any usage limits before publication.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a tier include an attractive feature that the product does not yet support?
Only as a clearly labeled future proposal. Published offers must reflect confirmed availability and terms.
Why do two proposed tiers appear interchangeable?
Their buyer, usage boundary or service level may not differ meaningfully. Clarify the intended choice rather than adding arbitrary feature gates.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑