MarketingProduct DescriptionsAdvanced68 minSaves 2+ hours

Streamlining SaaS Product Tiers: Refactoring 40+ Features into Outcome-Based Bundles

For Product Marketing Managers, simplify complex SaaS product tiers by refactoring 40+ features into clear, outcome-driven bundles. Improve market positioning and customer value perception.

This prompt assists Product Marketing Managers in restructuring a SaaS product's pricing and packaging. It helps consolidate over 40 features across five tiers into three outcome-based bundles, including grandfathering rules, to clarify value for customers and improve market alignment.

READY-TO-USE PROMPT

Copy Prompt

prompt.txt
Role:
You are an experienced Product Marketing Manager specializing in pricing and packaging strategy. Your task is to develop a comprehensive plan for refactoring an existing product's feature set and pricing tiers.

Context:
Our product, `{{product_name}}`, currently offers over 40 distinct features spread across five complex pricing tiers. This extensive feature sprawl and convoluted tier structure have led to confusion among prospects and existing customers, hindering sales cycles and making it difficult to communicate clear value propositions. We need to simplify our offering significantly. We aim to consolidate these features into three distinct, outcome-based bundles. Each new bundle must clearly articulate the primary value it delivers. We also need a strategy for managing existing customers under the new structure (grandfathering rules).

Task:
Develop a detailed pricing and packaging refactor plan. This plan should clearly define the new tier structure, justify the bundling logic, propose a primary value metric, and address potential customer concerns.

Constraints:
*   **New Tier Structure:** Exactly three outcome-based bundles.
*   **Bundling Logic:** Features from the current `{{current_feature_list_and_tiers}}` must be logically grouped into these three new bundles, emphasizing customer outcomes over individual feature counts.
*   **Tone:** The final output must be clear, honest, and value-anchored. Avoid jargon where simpler language suffices.
*   **Grandfathering:** Include explicit rules and communication strategies for existing customers transitioning to or remaining on their current plans.
*   **Primary Value Metric:** Propose a single, clear value metric for each new bundle that aligns with the outcome.
*   **Buyer FAQ:** Anticipate common questions from buyers regarding the new packaging and provide concise, reassuring answers.

Output:
Provide the plan in the following structured format:

1.  **Executive Summary:** A brief overview of the refactoring strategy and its expected benefits.
2.  **Current State Analysis:**
    *   Summary of existing 5-tier structure and feature sprawl.
    *   Key pain points identified (e.g., customer confusion, sales friction).
3.  **New Packaging Strategy:**
    *   **Tier 1: [Bundle Name]**
        *   Primary Outcome: [Describe the core outcome for this tier]
        *   Included Features: [List key features from `{{current_feature_list_and_tiers}}` that support this outcome]
        *   Proposed Value Metric: [e.g., per user, per transaction, per project]
        *   Target Persona: [Who is this bundle for?]
    *   **Tier 2: [Bundle Name]**
        *   Primary Outcome: [Describe the core outcome for this tier]
        *   Included Features: [List key features from `{{current_feature_list_and_tiers}}` that support this outcome]
        *   Proposed Value Metric: [e.g., per user, per transaction, per project]
        *   Target Persona: [Who is this bundle for?]
    *   **Tier 3: [Bundle Name]**
        *   Primary Outcome: [Describe the core outcome for this tier]
        *   Included Features: [List key features from `{{current_feature_list_and_tiers}}` that support this outcome]
        *   Proposed Value Metric: [e.g., per user, per transaction, per project]
        *   Target Persona: [Who is this bundle for?]
4.  **Packaging Rationale:**
    *   Explanation of why these specific bundles were chosen.
    *   How they address current pain points and align with customer value.
5.  **Grandfathering Rules & Communication Plan:**
    *   Detailed rules for existing customers.
    *   Key messaging points for communicating the changes.
    *   Suggested channels for communication.
6.  **Buyer Frequently Asked Questions (FAQ):**
    *   Q: [Common question 1]? A: [Concise answer].
    *   Q: [Common question 2]? A: [Concise answer].
    *   Q: [Common question 3]? A: [Concise answer].
    *   (Include at least 5 relevant questions and answers)

Estimated results

DifficultyAdvanced
Setup time68 min
Time saved2+ hours
Best modelsChatGPT, Claude, Gemini
Best audienceSaaS

Editor's note

Why this prompt matters

Product marketing teams often face the challenge of an expanding feature set that outgrows its original pricing and packaging structure. Over time, products accumulate dozens of features, leading to complex, multi-tiered plans that confuse prospects and make it difficult for sales teams to articulate clear value. This scenario is particularly common in maturing SaaS companies where initial rapid development adds features without a regular review of how they align with customer outcomes.

This workflow is designed for Product Marketing Managers tasked with simplifying an overly complex SaaS product offering. When your current five-tier (or more) structure obscures the core value propositions, and customers struggle to understand which plan best suits their needs, it's time for a strategic refactor. The goal is to move beyond feature-counting to outcome-based bundling, making it easier for buyers to self-select and for your organization to communicate tangible benefits.

Reaching for this workflow means you're ready to define a clearer market position, reduce sales friction, and improve customer perception of value. It provides a structured approach to transition from a sprawling feature list to a concise, three-tier offering, complete with grandfathering rules for existing customers and an anticipated buyer FAQ.

Anatomy

Prompt engineering breakdown

Role

You are an experienced Product Marketing Manager specializing in pricing and packaging strategy. Your task is to develop a comprehensive plan for refactoring an existing product's feature set and pricing tiers.

Context

Our product, `{{product_name}}`, currently offers over 40 distinct features spread across five complex pricing tiers. This extensive feature sprawl and convoluted tier structure have led to confusion among prospects and existing customers, hindering sales cycles and making it difficult to communicate clear value propositions. We need to simplify our offering significantly. We aim to consolidate these features into three distinct, outcome-based bundles. Each new bundle must clearly articulate the primary value it delivers. We also need a strategy for managing existing customers under the new structure (grandfathering rules).

Goal

Develop a detailed pricing and packaging refactor plan. This plan should clearly define the new tier structure, justify the bundling logic, propose a primary value metric, and address potential customer concerns.

Constraints

* **New Tier Structure:** Exactly three outcome-based bundles. * **Bundling Logic:** Features from the current `{{current_feature_list_and_tiers}}` must be logically grouped into these three new bundles, emphasizing customer outcomes over individual feature counts. * **Tone:** The final output must be clear, honest, and value-anchored. Avoid jargon where simpler language suffices. * **Grandfathering:** Include explicit rules and communication strategies for existing customers transitioning to or remaining on their current plans. * **Primary Value Metric:** Propose a single, clear value metric for each new bundle that aligns with the outcome. * **Buyer FAQ:** Anticipate common questions from buyers regarding the new packaging and provide concise, reassuring answers.

Output format

Provide the plan in the following structured format: 1. **Executive Summary:** A brief overview of the refactoring strategy and its expected benefits. 2. **Current State Analysis:** Summary of existing 5-tier structure and feature sprawl. Key pain points identified (e.g., customer confusion, sales friction). 3. **New Packaging Strategy:** Tier 1, 2, 3 details (Bundle Name, Primary Outcome, Included Features, Proposed Value Metric, Target Persona). 4. **Packaging Rationale:** Explanation of why these specific bundles were chosen. How they address current pain points and align with customer value. 5. **Grandfathering Rules & Communication Plan:** Detailed rules for existing customers. Key messaging points for communicating the changes. Suggested channels for communication. 6. **Buyer Frequently Asked Questions (FAQ):** Q&A (at least 5 relevant questions and answers).

Why this structure works

The prompt effectively guides the model by using role priming, establishing the persona's expertise. Explicit constraints on the new tier structure, bundling logic, and tone ensure the output meets specific strategic requirements. The detailed structured output format ensures comprehensive coverage of all necessary sections, making the generated plan immediately actionable for product marketing managers.

Pick your version

Prompt variations

BeginnerWorks with any model

For quick drafts or users new to pricing strategy who need a simpler approach to feature organization.

prompt.txt
You are a marketing assistant. Your task is to help us simplify our product's features. Our product, `{{product_name}}`, has many features (over 40) spread across five different price levels. This makes it hard for customers to understand what they're getting. We need to organize these features, which are currently listed as `{{current_feature_list}}`, into three new, simpler groups. Each new group should focus on a clear benefit or outcome for the customer. For each new group, tell us: 1) its main goal, 2) which key features are included, 3) how we should charge for it (e.g., 'per user'), and 4) who the ideal customer is for that group. Also, explain how we will handle our existing customers when we make these changes, and provide answers to common questions buyers might ask. Keep your language straightforward and easy to understand, focusing on what value each group provides.
ProfessionalBest with chatgpt

For detailed strategic planning and comprehensive documentation, matching the depth required by experienced product marketing managers.

prompt.txt
Role: You are an experienced Product Marketing Manager specializing in pricing and packaging strategy. Your task is to develop a comprehensive plan for refactoring an existing product's feature set and pricing tiers. Context: Our product, `{{product_name}}`, currently offers over 40 distinct features spread across five complex pricing tiers. This feature sprawl causes confusion and hinders sales. We must simplify into three distinct, outcome-based bundles, each articulating clear value. A strategy for grandfathering existing customers is also required. Task: Develop a detailed pricing and packaging refactor plan. Define the new tier structure, justify bundling logic, propose a primary value metric, and address potential customer concerns. Constraints: Exactly three outcome-based bundles. Features from `{{current_feature_list_and_tiers}}` must group logically by customer outcome. Tone: clear, honest, value-anchored. Include explicit grandfathering rules and communication strategies. Propose a single, clear value metric per bundle. Anticipate common buyer questions and provide concise answers. Output: Provide a structured plan including Executive Summary, Current State Analysis, New Packaging Strategy (three defined tiers with outcomes, features, value metrics, target personas), Packaging Rationale, Grandfathering Rules & Communication Plan, and Buyer Frequently Asked Questions (at least 5).
Short VersionWorks with any model

For rapid ideation or initial concept generation when a concise, single-paragraph summary is sufficient.

prompt.txt
As a Product Marketing Manager, develop a concise plan to refactor `{{product_name}}`'s current 5-tier, 40+ feature structure into three outcome-based bundles. For each new bundle, define its primary outcome, list key features from `{{current_feature_list_and_tiers}}`, propose a value metric, and identify the target persona. The plan must also include a clear grandfathering strategy for existing customers and a brief FAQ for potential buyers. Maintain a clear, honest, and value-anchored tone throughout the output, prioritizing customer outcomes over feature lists.
EnterpriseBest with claude

When a refactoring plan requires cross-functional buy-in, legal review, or addresses significant organizational impact and risk mitigation.

prompt.txt
Role: You are a Senior Product Strategy Consultant, tasked with leading a critical pricing and packaging overhaul for `{{product_name}}`. Context: The existing 5-tier structure with 40+ features creates significant market confusion, compliance risks, and internal stakeholder friction. Our objective is a strategic consolidation into three outcome-based bundles, focusing on transparent value articulation and a robust transition plan for existing customers. Task: Develop a comprehensive refactor plan addressing market positioning, cross-functional stakeholder alignment, potential legal/compliance implications, and risk mitigation. Constraints: Precisely three outcome-based bundles with features from `{{current_feature_list_and_tiers}}` grouped by demonstrable customer value. Define clear value metrics and detailed grandfathering rules, including legal review points. The plan must be clear, honest, value-anchored, and incorporate a comprehensive stakeholder communication matrix and an expanded risk-adjusted Buyer/Internal FAQ. Output: Structured plan encompassing Executive Summary, Current State Analysis, New Packaging Strategy (including legal/compliance review considerations for each tier), Strategic Rationale, Grandfathering Rules & Communication Plan (with risk assessment), Stakeholder Communication Plan, and a detailed Buyer/Internal FAQ.

What you'll get

Expected output

  1. Executive Summary:

This plan outlines a strategic refactor of GrowthPilot CRM's packaging from five feature-centric tiers to three outcome-based bundles: 'Essential Growth', 'Accelerated Sales', and 'Enterprise Command'. The aim is to simplify the offering, clarify value propositions, reduce customer confusion, and align pricing with tangible business outcomes. Grandfathering rules will protect existing customer agreements, ensuring a smooth transition.

  1. Current State Analysis:

* Summary of existing 5-tier structure and feature sprawl: GrowthPilot CRM currently offers over 45 features distributed across Starter, Pro, Business, Enterprise, and Platinum tiers. This includes functionalities like basic contact management, email templates, advanced segmentation, workflow automation, lead scoring, sales pipeline, API access, advanced analytics, and AI-driven insights. * Key pain points identified: Prospects frequently express confusion about feature differentiation between tiers, leading to extended sales cycles and decision paralysis. Existing customers often feel they are paying for unused features or struggle to identify upgrade paths. Sales teams find it challenging to communicate a concise value story, defaulting to feature comparisons rather than outcome selling.

  1. New Packaging Strategy:

* Tier 1: Essential Growth * Primary Outcome: Streamlined contact management and foundational sales outreach. * Included Features: Basic Contact Management, Task Tracking, Standard Email Templates, Basic Reporting, Mobile App Access, Customer Support (Email). * Proposed Value Metric: Per User, per month. * Target Persona: Small businesses, startups, individual sales reps needing core CRM functionality. * Tier 2: Accelerated Sales * Primary Outcome: Optimize sales processes, improve lead conversion, and automate workflows. * Included Features: All Essential Growth, Advanced Contact Segmentation, Workflow Automation (up to 10 workflows), Custom Fields (unlimited), Advanced Reporting Dashboards, Lead Scoring, Sales Pipeline Management, Email Marketing (up to 10k sends), Integrations (up to 5), Team Collaboration. * Proposed Value Metric: Per User, per month. * Target Persona: Growing sales teams, SMBs focused on scaling their sales operations. * Tier 3: Enterprise Command * Primary Outcome: Comprehensive sales intelligence, operational control, and strategic growth at scale. * Included Features: All Accelerated Sales, AI-driven Insights, Predictive Lead Scoring, Advanced Analytics, Dedicated Account Manager, SSO, Role-Based Permissions, Custom Integrations (unlimited), Multi-Region Support, 24/7 Premium Support, White-labeling. * Proposed Value Metric: Per 10 Users, per month (with volume discounts). * Target Persona: Large enterprises, organizations with complex sales processes and compliance needs.

  1. Packaging Rationale:

These bundles were designed around clear customer outcomes rather than just feature counts. 'Essential Growth' addresses the basic need for organized customer data. 'Accelerated Sales' focuses on driving efficiency and conversion for active sales teams. 'Enterprise Command' provides the tools for large organizations to manage, analyze, and optimize extensive sales operations. This structure directly addresses the pain points of confusion and helps prospects quickly identify the tier that aligns with their business objectives, improving sales velocity and perceived value.

  1. Grandfathering Rules & Communication Plan:

* Detailed rules for existing customers: * Customers on existing Starter, Pro, Business, Enterprise, and Platinum plans will retain their current pricing and feature set for the duration of their existing contract term. They will not be forced to migrate to the new bundles. * Upon contract renewal, existing customers will be offered the option to renew on their current plan at a new, slightly adjusted grandfathered rate, or migrate to one of the new outcome-based bundles. Migration to a new bundle will be incentivized with a one-time discount or additional onboarding support. * Customers wishing to upgrade before renewal will be moved to the most appropriate new bundle, with prorated credit for their existing plan. * Key messaging points for communicating the changes: * "Simplifying our offerings for clearer value and easier decision-making." * "Focused on delivering specific outcomes to help your business grow." * "Your current plan and pricing are secure; you have options at renewal." * Suggested channels for communication: Direct email campaigns to all customers, in-app notifications, updated website pricing page (with a clear explanation for existing customers), and sales team briefing document.

  1. Buyer Frequently Asked Questions (FAQ):

* Q: Why are you changing your pricing and packaging? A: We're simplifying our offerings to make it easier for you to choose the right plan based on the specific business outcomes you want to achieve, rather than sifting through a long list of features. * Q: What happens to my current plan? A: If you're an existing customer, your current plan and pricing remain exactly the same until your next renewal. At that point, you'll have the option to renew on your current plan or switch to one of our new outcome-based bundles. * Q: Are you removing any features? A: No features are being removed from the product. We've simply reorganized them into more intuitive bundles that align with common customer goals. * Q: How do I know which new bundle is right for me? A: Each new bundle is designed around a clear primary outcome. Consider what you aim to achieve with GrowthPilot CRM—whether it's foundational growth, accelerated sales, or comprehensive enterprise command—to find your best fit. Our sales team is also available to assist. * Q: Will the new bundles be more expensive? A: Our new pricing reflects the value delivered by each outcome-based bundle. While some specific feature combinations may change, our goal is to provide clear, competitive value. Existing customers have protected pricing until renewal.

Under the hood

Why this prompt works

This prompt structure delivers a comprehensive plan because it systematically applies several prompt engineering techniques. First, role priming establishes the persona as an 'experienced Product Marketing Manager specializing in pricing and packaging strategy.' This cues the model to adopt a specific expert perspective, ensuring the output aligns with industry best practices and strategic thinking rather than generic responses.

Second, the explicit constraints are critical. By mandating 'exactly three outcome-based bundles,' specific tone requirements, and clear directives for 'grandfathering' and a 'primary value metric,' the prompt narrows the solution space significantly. This prevents the model from generating an unmanageable number of tiers or missing essential components of a real-world packaging strategy.

Finally, the structured output requirement, detailing each section from 'Executive Summary' to 'Buyer FAQ' with sub-points, guides the model to produce a well-organized and actionable document. This is far more effective than a simple request like 'create a pricing plan,' which would yield unstructured, often incomplete, information. The detailed structure acts as a template, ensuring all necessary elements of a thorough pricing refactor plan are present and logically arranged, making the output immediately useful for a PMM.

Model fit

Best AI models for this prompt

ChatGPT

ChatGPT models are effective for this type of structured output due to their ability to follow complex instructions and generate detailed, well-organized content. They excel at synthesizing information and applying logical frameworks, which is crucial for defining new tiers and crafting rationale. However, initial outputs may require refinement to ensure the proposed value metrics are truly innovative or perfectly aligned with the nuanced business context. See the full ChatGPT hub for deeper guidance.

Claude

Claude models handle extensive context windows well, making them suitable for processing a large feature list and existing tier details to inform a new packaging strategy. Its strength lies in producing thoughtful, human-like explanations and justifications, which is valuable for the packaging rationale and customer communication sections. Users might need to guide Claude more explicitly on quantitative aspects, such as specific pricing recommendations, as its core strength leans towards qualitative analysis. See the full Claude hub for deeper guidance.

Gemini

Gemini models demonstrate strong reasoning capabilities, which are beneficial for analyzing the existing feature sprawl and identifying logical groupings for outcome-based bundles. They are adept at generating creative solutions for complex problems and maintaining a consistent tone throughout the output. While strong on content generation, users should cross-reference Gemini's suggestions for market competitiveness and ensure the grandfathering rules are legally sound for their specific region. See the full Gemini hub for deeper guidance.

When to use

  • When your SaaS product has accumulated 40+ features across five or more confusing pricing tiers.
  • To pivot your sales and marketing from a feature-checklist approach to an outcome-driven value proposition.
  • When customer acquisition is hindered by buyer confusion over which tier best suits their needs.
  • To establish clear, consistent messaging around product value for both prospects and existing customers.
  • During a strategic product repositioning or market re-entry requiring a simplified offering.

When not to use

  • If your product has fewer than 15 features or is already organized into 2-3 clear tiers.
  • When the primary objective is minor price adjustments, not a fundamental restructuring of features.
  • For early-stage products still defining their core functionality and ideal customer segments.
  • If your existing customer base is highly sensitive to any changes in their current plan structure.
  • When market analysis indicates that customers prefer a highly granular, feature-by-feature purchasing model.

Get more from it

Pro tips

  • 1

    Validate proposed value metrics with sales and finance early to prevent misaligned pricing models that hinder adoption or profitability.

  • 2

    Test new bundle names and outcome descriptions with a small customer segment to avoid confusing language or perceived value gaps.

  • 3

    Prepare detailed internal training materials for sales and customer support teams to prevent inconsistent messaging during the transition.

  • 4

    Map all current features to *at least one* new bundle to avoid orphaned functionalities or perceived loss of value for existing users.

  • 5

    Draft comprehensive grandfathering FAQs for existing customers to proactively address concerns and prevent churn due to uncertainty.

  • 6

    Simulate the customer journey through the new tiers to catch potential friction points before the packaging launch.

  • 7

    Quantify the value delivered by each outcome to justify pricing decisions and avoid perceived price increases.

Don't ship this

Common mistakes

  • Neglecting to involve key stakeholders like sales, finance, and product early in the refactoring process.

    Fix — Include representatives from all relevant departments in initial strategy sessions to ensure buy-in and practical feedback.

  • Creating new bundles that still feel feature-heavy rather than truly outcome-focused, perpetuating confusion.

    Fix — Relentlessly question if each bundle name and description directly addresses a clear, tangible customer problem or desired result.

  • Underestimating the communication effort required for existing customers regarding grandfathering rules.

    Fix — Develop a multi-channel communication plan, including email, in-app notifications, and account manager outreach, for existing users.

  • Choosing a value metric that is difficult for customers to understand, track, or predict their costs.

    Fix — Opt for a transparent, easily quantifiable value metric that clearly scales with customer usage or the perceived benefit received.

  • Failing to consider the operational impact of new pricing models on billing and CRM systems.

    Fix — Consult with finance and engineering teams early to confirm the technical feasibility and implementation complexity of new pricing structures.

People also ask

Frequently asked questions

Q.How specific should the `{{current_feature_list_and_tiers}}` input be?

Provide a concise, high-level list or a summary. The model needs enough context to understand the *types* of features and their distribution across current tiers, not every minute detail. A link to an internal document is also effective.

Q.Can I adjust the number of new tiers from three?

No, the prompt explicitly constrains the new structure to "exactly three outcome-based bundles." Deviating will require significant modification to the prompt's core instructions and expected output format.

Q.What if I don't have a clear value metric in mind for the new bundles?

The prompt requires a *proposed* value metric. Research common SaaS metrics like per-user, per-active-project, or per-transaction, and choose one that best aligns with the core outcome your product delivers for each bundle.

Q.How do I handle existing features that don't seem to fit neatly into an outcome-based bundle?

Re-evaluate if that feature truly delivers a standalone outcome. It might be a foundational component of a larger outcome in a bundle, or potentially a candidate for deprecation if it lacks clear customer value.

Q.Should I include pricing values (e.g., $X/month) in the prompt's input?

No, the prompt focuses on the strategic packaging and tier definition, not specific price points. The output will define the tiers, outcomes, and value metrics, allowing you to set the actual prices later.

Q.Will the generated plan cover the technical steps for migrating customer accounts to new tiers?

The plan outlines the grandfathering rules and communication strategy for existing customers. It does not detail the technical implementation steps for migrating accounts or updating billing systems, which are operational tasks.

Version 1.0Last reviewed July 12, 2026
Reviewed by PromptInFlow Editorial Team