MarketingProduct DescriptionsAdvanced68 minSaves 2+ hours

Design Usage-Based Add-On Catalogs with Finance Alignment

Product Marketing and Finance teams can structure usage-based add-ons, defining in-tier vs. metered components, pricing, and margin bands to accelerate market entry and revenue growth.

Develop a comprehensive pricing document for usage-based add-ons. This prompt guides Product Marketing and Finance through defining value metrics, packaging rationale, tier structures, and buyer FAQs, ensuring alignment with finance-approved margin bands and market needs.

READY-TO-USE PROMPT

Copy Prompt

prompt.txt
As a seasoned Pricing Strategist and Product Marketer, your objective is to create a detailed pricing and packaging document for new usage-based add-ons. This document will serve as a foundational resource for product, sales, and finance teams.

### Context

Our company is introducing new usage-based add-ons for our existing {{product_name}} product, targeting the {{target_customer_segment}} segment. The goal is to offer flexible, value-aligned options that allow customers to scale their usage beyond core tiers while maintaining predictable costs. These add-ons must be financially viable, aligning with predefined margin bands set by our finance department.

We need to clearly define what functionality or consumption metrics belong within existing core tiers versus what will be metered as an add-on. For metered components, we must establish a clear price per unit and consider various cap options to manage customer spend and internal risk. The overall packaging rationale needs to clearly articulate the value proposition to the buyer.

### Task

Generate a comprehensive pricing document that outlines the strategy for our new usage-based add-ons. This document should address the following key areas:

1.  **Tier Definitions**: Clearly delineate which functionalities or usage levels are included in the base {{product_name}} product tiers and which components are exclusively offered as usage-based add-ons. Provide a rationale for these divisions.

2.  **Value Metric Identification**: Define the primary value metric(s) for each usage-based add-on. Explain why this metric was chosen and how it directly correlates to customer value and our business objectives.

3.  **Packaging Rationale**: Detail the strategic thinking behind the packaging of these add-ons. Explain how they complement the core product, address specific customer pain points, and contribute to overall revenue growth. Include considerations for bundling or standalone offerings.

4.  **Pricing Structure**: For each identified add-on, propose a clear pricing structure. This must include:
    *   **Price Per Unit**: The specific cost for each unit of the defined value metric.
    *   **Cap Options**: Discuss potential soft or hard caps on usage, including pricing implications for exceeding these caps, or tiered pricing based on usage volume.
    *   **Finance Alignment**: Confirm how the proposed pricing and cap options adhere to our finance department's approved margin bands and revenue targets. Provide a high-level explanation of the financial modeling considered.

5.  **Buyer FAQ**: Develop a list of anticipated questions from potential buyers regarding these new add-ons. Provide clear, concise, and value-anchored answers. Focus on common concerns about cost predictability, billing, and value realization.

### Constraints

*   The output must be a single, cohesive pricing document.
*   Maintain a clear, honest, and value-anchored tone throughout the document.
*   Ensure all pricing and packaging proposals are grounded in financial prudence and market understanding.
*   Avoid jargon where plain language suffices, especially in the buyer FAQ section.
*   The document must be easily digestible for both technical and non-technical stakeholders.

### Output Format

The output should be a structured document with distinct sections for each of the task items (Tier Definitions, Value Metric Identification, Packaging Rationale, Pricing Structure, Buyer FAQ). Use clear headings and bullet points where appropriate for readability.

Estimated results

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

Editor's note

Why this prompt matters

Introducing usage-based add-ons presents a common challenge for product marketing and finance teams. Defining what elements of a service should remain within core product tiers versus what should be metered as an add-on often leads to internal debate and external confusion. Without a clear framework, companies risk mispricing, alienating customers with unpredictable bills, or failing to meet financial targets.

This workflow is designed for Product Marketing Managers and finance professionals tasked with structuring these new offerings. It provides a systematic approach to delineate features, identify appropriate value metrics, and establish pricing that aligns both with customer perceived value and crucial financial objectives. By front-loading the strategic thinking, teams can avoid common pitfalls and accelerate their go-to-market efforts.

Reach for this prompt when you are developing new usage-based extensions to an existing product and need to generate a comprehensive, finance-approved pricing document. It's particularly useful for ensuring internal alignment and preparing clear communication for sales and customers before launch.

Anatomy

Prompt engineering breakdown

Role

Seasoned Pricing Strategist and Product Marketer

Context

Our company is introducing new usage-based add-ons for an existing product. The task is to define what functionality belongs in core tiers versus what will be metered as an add-on, establish a clear price per unit, consider cap options, and align all proposals with finance department margin bands. The target customer segment for these add-ons is specified.

Goal

To create a comprehensive pricing and packaging document for new usage-based add-ons that will serve as a foundational resource for product, sales, and finance teams.

Constraints

The output must be a single, cohesive document, maintaining a clear, honest, and value-anchored tone. All proposals must be financially prudent and market-understood. Jargon should be avoided, especially in the buyer FAQ. The document must be easily digestible for both technical and non-technical stakeholders.

Output format

A structured document with distinct sections for Tier Definitions, Value Metric Identification, Packaging Rationale, Pricing Structure, and Buyer FAQ. Clear headings and bullet points should be used for readability.

Why this structure works

This prompt effectively uses role priming, assigning the model the persona of a 'Seasoned Pricing Strategist and Product Marketer' to ensure an expert perspective. Explicit constraints on tone and content quality guide the model to produce a professional, coherent output. The structured output format, with specific section requirements, guarantees that all critical aspects of usage-based add-on design are covered in an organized and digestible manner.

Pick your version

Prompt variations

BeginnerWorks with any model

For initial concept exploration or when you need a high-level overview of add-on pricing without requiring deep financial modeling details.

prompt.txt
As a Product Marketing Specialist, your task is to outline a basic pricing plan for new usage-based add-ons. This plan will help our team understand how to sell these new features.

### Context
We are adding new pay-as-you-go features to our {{product_name}} product for {{target_customer_segment}} customers. We want to give customers more choices and ensure they pay fairly for what they use. We also need to make sure these add-ons make financial sense for us.

Decide which parts of our product stay in the main subscription and which become separate add-ons. For add-ons, suggest a price per unit and think about how to limit costs for customers. The overall plan should explain why these add-ons are good for customers.

### Task
Create a simple document explaining our strategy for new usage-based add-ons. Focus on:

1.  **What's Included**: Clearly state what is part of the main {{product_name}} product and what is an add-on. Explain why.
2.  **How We Measure Value**: Identify what customers will pay for (e.g., per GB, per user, per transaction). Explain why this makes sense.
3.  **Why This Packaging**: Describe the main reasons for offering these add-ons this way.
4.  **Simple Pricing**: For each add-on, propose a price per unit. Suggest ways to cap usage to help customers manage spending.
5.  **Customer Questions**: List a few questions customers might ask and provide simple answers about cost and value.

### Constraints
*   The document should be easy to understand.
*   Use clear and straightforward language.
*   Focus on customer value and basic financial viability.

### Output Format
Use clear headings for each section: What's Included, How We Measure Value, Why This Packaging, Simple Pricing, Customer Questions.
ProfessionalBest with chatgpt

When you require a comprehensive, detailed pricing and packaging strategy document for new usage-based add-ons, aligning product marketing and financial considerations.

prompt.txt
Act as a seasoned Pricing Strategist and Product Marketer. Your objective is to develop a comprehensive pricing and packaging document for new usage-based add-ons. This document will inform product, sales, and finance teams.

### Context
Our company is introducing usage-based add-ons for our {{product_name}} product, targeting the {{target_customer_segment}} segment. The goal is to provide flexible, value-aligned options, enabling customers to scale usage beyond core tiers while maintaining cost predictability. These add-ons must be financially sound, adhering to margin bands set by our finance department.

Clearly define which functionalities or consumption metrics reside within existing core tiers versus those metered as add-ons. For metered components, establish a clear price per unit and consider various cap options to manage customer spend and internal exposure. The packaging rationale must articulate the value proposition to the buyer.

### Task
Generate a detailed pricing document outlining the strategy for our new usage-based add-ons. Address these key areas:

1.  **Tier Definitions**: Delineate functionalities/usage in base {{product_name}} tiers vs. usage-based add-ons. Provide a clear rationale for these distinctions.
2.  **Value Metric Identification**: Define primary value metric(s) for each add-on, explaining selection and correlation to customer value/business objectives.
3.  **Packaging Rationale**: Detail strategic thinking behind add-on packaging. Explain how they complement the core product, address customer needs, and drive revenue growth. Include bundling/standalone considerations.
4.  **Pricing Structure**: For each add-on, propose a clear pricing structure:
    *   **Price Per Unit**: Cost per unit of the defined value metric.
    *   **Cap Options**: Discuss soft/hard caps, pricing for exceeding caps, or tiered pricing.
    *   **Finance Alignment**: Confirm how pricing aligns with financial targets.
Short VersionWorks with any model

For quick ideation or when you need a concise summary of add-on pricing considerations to kickstart a discussion or provide a brief overview.

prompt.txt
As a Product Marketer, quickly outline a pricing strategy for new usage-based add-ons for our {{product_name}} product, targeting {{target_customer_segment}}. Define what features belong in core tiers versus metered add-ons, propose a clear value metric and price per unit for each, and consider basic usage caps. Briefly articulate the packaging rationale and anticipate common buyer questions about cost and value. The goal is a concise plan that ensures financial viability while offering flexible, value-aligned options for customers.
EnterpriseBest with claude

For large organizations needing to factor in regulatory compliance, cross-functional stakeholder buy-in, and detailed risk mitigation strategies for new usage-based add-ons.

prompt.txt
Act as a Principal Pricing Strategist and GTM Lead. Your objective is to architect a comprehensive pricing and packaging framework for new usage-based add-ons, ensuring alignment across all enterprise functions. This framework will serve as a definitive blueprint for product development, global sales enablement, finance, legal, and operational teams.

### Context

Our organization is launching new usage-based add-ons for our flagship {{product_name}} platform, targeting the {{target_customer_segment}} enterprise segment. The imperative is to deliver highly flexible, value-aligned consumption models that empower large customers to scale their operations beyond core platform entitlements while maintaining predictable cost governance. These add-ons must adhere to strict financial viability mandates, including predefined margin bands and revenue recognition standards set by our corporate finance and legal departments.

We must precisely define functionality and consumption metrics, delineating what remains within existing core enterprise tiers versus what constitutes a metered add-on. For metered components, establish clear unit economics and evaluate sophisticated cap mechanisms, including spend guardrails, commitment tiers, and overage policies, to manage both customer budget predictability and our internal financial risk exposure. The overarching packaging strategy requires robust justification, articulating differentiated value propositions for diverse enterprise buyer personas and use cases, while also considering global regulatory compliance.

What you'll get

Expected output

Pricing and Packaging Document: DataInsight Pro - Advanced Analytics Add-ons

Product Name: DataInsight Pro Target Customer Segment: Mid-market analytics teams

1. Tier Definitions

Core DataInsight Pro Tiers (Standard, Premium, Enterprise) Include:

  • Standard: Up to 10 active users, 50 GB data storage, basic reporting, 100 monthly query executions.
  • Premium: Up to 50 active users, 250 GB data storage, advanced reporting, 500 monthly query executions.
  • Enterprise: Unlimited users, custom data storage, executive dashboards, 2,000 monthly query executions.

Usage-Based Add-ons Exclusively Offered:

  • Advanced Query Credits: For query executions beyond core tier limits.
  • Historical Data Retention: For storing data beyond the standard 1-year retention period included in core tiers.
  • Premium API Access: For integrations requiring higher throughput and dedicated API support beyond the basic API calls included in Premium/Enterprise tiers.

Rationale for Division: Core tiers provide foundational analytics capabilities suitable for general use. The add-ons address specific, higher-volume, or specialized needs of power users and larger organizations, allowing them to scale consumption without forcing an upgrade to an entire new tier. This ensures customers pay only for the incremental value they consume beyond the base offering.

Under the hood

Why this prompt works

This workflow produces a structured, actionable pricing document by applying several prompt engineering techniques. First, role priming establishes the persona of a 'seasoned Pricing Strategist and Product Marketer.' This directs the model to generate content with the appropriate expertise, tone, and strategic perspective, moving beyond generic descriptions to deliver practical business recommendations.

Second, the prompt utilizes explicit constraints for tone and content, such as 'clear, honest, and value-anchored' and 'grounded in financial prudence.' These constraints guide the model to produce output that is not only informative but also credible and aligned with real-world business requirements.

Third, a detailed task breakdown combined with structured output instructions is crucial. By breaking the complex problem of add-on catalog design into distinct, numbered sections (Tier Definitions, Value Metric, Packaging Rationale, Pricing Structure, Buyer FAQ), the prompt guides the model through a logical thought process. This ensures all critical aspects are addressed systematically, preventing omissions and producing a comprehensive document ready for review. This approach yields a far more complete and usable output than a single, open-ended request.

Model fit

Best AI models for this prompt

ChatGPT

ChatGPT excels at generating structured documents and handling complex data relationships. It can effectively map out tier definitions and pricing structures, ensuring logical consistency. However, a user may need to refine the language to ensure the tone remains consistently value-anchored and avoids generic corporate phrasing. See the full ChatGPT hub for deeper guidance.

Claude

Claude is particularly strong in producing detailed, nuanced content with excellent tonal control. Its ability to process longer contexts makes it suitable for developing comprehensive packaging rationales and thoughtful buyer FAQs. Users might find Claude's output requires less editing for clarity and empathetic communication. See the full Claude hub for deeper guidance.

Gemini

Gemini offers a good balance between analytical structure and creative problem-solving, which is beneficial when exploring different cap options or articulating the value proposition. It can help brainstorm various pricing scenarios and explain their financial implications. Users should review the output for precision in financial details, but it's a solid choice for initial strategy development. See the full Gemini hub for deeper guidance.

When to use

  • When launching new usage-based features or modules for an existing SaaS product.
  • To clearly separate core product functionality from metered add-on usage for existing offerings.
  • For product marketing and finance teams needing a unified strategy on add-on pricing.
  • When preparing clear internal and external communication on new usage-based models.
  • If expanding product reach into segments requiring flexible, usage-aligned consumption options.

When not to use

  • When developing initial pricing for a brand-new product without established tiers.
  • If your product exclusively uses a flat-rate subscription model with no usage component.
  • For simple, fixed-price feature add-ons that do not require metering or value metric definition.
  • If market research on customer willingness-to-pay for metered usage is incomplete or missing.
  • When your finance department has not yet provided acceptable margin targets for new offerings.

Get more from it

Pro tips

  • 1

    To prevent vague value metrics, clearly define how each unit of usage delivers tangible customer benefit, linking it to operational or strategic outcomes.

  • 2

    Avoid misaligning add-on value with core product; ensure the prompt explicitly defines the distinction to prevent customer confusion or perceived feature stripping.

  • 3

    To prevent financial miscalculations, explicitly state the finance-approved margin bands and specific revenue targets for the add-ons in your input.

  • 4

    Ensure all cap options are clearly articulated, including pricing implications for exceeding them, to prevent unexpected customer billing or internal risk.

  • 5

    To prevent generic buyer FAQs, anticipate common customer anxieties about cost predictability, usage spikes, and the billing cycle.

  • 6

    Detail specific target market segments for add-ons to prevent broad, ineffective targeting and ensure value alignment.

  • 7

    Clearly differentiate add-on functionality from core features to prevent customer perception of feature removal from base tiers.

Don't ship this

Common mistakes

  • Providing a vague or absent definition of existing core product tiers.

    Fix — Supply a concise, clear summary of current {{product_name}} tiers and their included functionalities.

  • Not specifying the target customer segment's pain points addressed by add-ons.

    Fix — Briefly list 2-3 key customer pain points the new usage-based add-ons directly solve.

  • Overlooking potential cannibalization of existing core product revenue streams.

    Fix — Instruct the model to analyze and propose strategies to mitigate any cannibalization risks.

  • Omitting specific financial constraints like desired margin percentages or revenue goals.

    Fix — Include precise financial parameters (e.g., "maintain 70% gross margin") for better alignment.

  • Requesting "cap options" without considering the internal operational impact or feasibility.

    Fix — Specify operational capabilities for tracking and enforcing various cap types, like hard or soft limits.

  • Failing to provide context on current market pricing for similar usage-based features.

    Fix — Briefly mention relevant competitor pricing models or industry benchmarks for comparative analysis.

People also ask

Frequently asked questions

Q.Can this prompt handle multiple distinct usage-based add-ons simultaneously within one document?

Yes, the prompt is designed to structure a comprehensive document for multiple add-ons. Ensure you clearly list each add-on and its specific parameters in your input context.

Q.How detailed should my input be regarding the "finance-approved margin bands"?

Provide specific percentages or ranges, like "gross margin between 65-75%" or "target incremental revenue of $X million," to guide the model accurately.

Q.What if I don't have a fully defined target customer segment or their specific pain points yet?

Define the segment as best as possible. The model can help articulate potential pain points, but clearer input yields more targeted and useful output.

Q.Can I use this prompt to develop pricing for non-SaaS products, like hardware or professional services?

While focused on usage-based software, the core principles of value metric, packaging, and finance alignment are applicable. Adapt the inputs to your product's specific context.

Q.How long should the input for {{product_name}} and {{target_customer_segment}} be?

Keep them concise. A brief, descriptive name for the product and a clear, 1-2 sentence description of the target segment's key characteristics are sufficient.

Q.Does this prompt provide actual pricing numbers, or does it focus more on the pricing structure?

It focuses on defining the structure and rationale. While it proposes "price per unit," the actual numerical value will reflect your input and financial constraints.

Q.Is this adaptable for various usage-based models, such as tiered usage, volume discounts, or pure pay-as-you-go?

Yes, it supports discussion of various cap options and tiered pricing. Clearly specify your desired model variations within the "Cap Options" instruction for best results.

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