Draft Multi-Tier SaaS Product Packaging and Feature Matrix
Generate a clear, competitive feature matrix for your SaaS product that aligns tiered capabilities with specific user upgrade triggers.
Prompt
Act as a Senior Product Manager. Your task is to design a three-tier SaaS pricing and feature packaging matrix. Before starting, please ask me these 4 questions: 1. What is the core value proposition of the product? 2. What are the three primary user personas? 3. What is the single most common usage metric that drives value or capacity limits? 4. What is the main differentiator for the Enterprise tier? Once I answer, provide the matrix. Follow these rules: 1. Create three tiers: Free, Pro, and Enterprise. 2. Include one unique upgrade trigger metric for each tier transition. 3. Ensure every feature listed in a tier directly solves a specific pain point for that persona. 4. Use a table format with features as rows and tiers as columns. 5. Include a brief rationale for why the upgrade trigger is placed at that specific usage level. This is not professional financial or legal advice; consult a business strategy professional for final pricing decisions.Example output
Tips and common edits
Why this works
- Requires specific persona-based feature mapping to ensure tiers have real value.
- Forces identification of a core usage metric that aligns pricing with value.
- Uses a structured table format for immediate professional presentation.
Use this when you are defining your product's go-to-market strategy or revising your pricing page tiers. It works best in ChatGPT, Claude, or Gemini. Simply copy the prompt, send it, and answer the 4 follow-up questions provided by the model.
Common edits
- Adjust the tier names if your product uses different terminology like Starter or Business.
- Add a row for specific usage limits if you have tight infrastructure cost constraints.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Analyze customer feedback using Jobs to Be Done
Extract functional, emotional, and social customer drivers from raw user feedback. Use this to separate true user motivations from reactionary feature requests.
Reframe a feature request into a core user problem
Break down prescriptive feature requests into underlying user motivations, workflow bottlenecks, and testable problem statements.
Draft a Zero-to-One Product Discovery Experiment Card
Generates a structured, one-page test card with a falsifiable hypothesis, cheap validation test, and numeric kill threshold for new features.
Construct a quarterly product review executive narrative
Transform fragmented product metrics and sprint deliverables into a structured executive narrative connecting outcomes, misses, and forward bets.
Turn Engineering Changelogs into Customer Release Notes Users Read
Paste a changelog or ticket list and get customer-ready release notes grouped into New, Improved and Fixed, with internal-only changes removed and listed.
Design a customer grandfathering plan for pricing changes
Structure a fair, phased grandfathering framework that updates customer pricing without triggering mass cancellations.
- Draft a working-backwards press release and FAQ
- Write a Customer Interview Script That Validates a Problem with Past-Behavior Questions
- Define beta cohorts and launch exit metrics
- Draft a customer advisory board charter
- Rewrite empty state copy to accelerate user activation
- Schedule phased customer communications for feature sunsetting