Software Feature Tier and Dynamic Upgrade Paywall Spec
Develop a product-led merchandising specification for in-app upgrade paywalls and feature tier cards.
Use this template when designing in-product paywalls, tier comparison matrices, or contextual upsell modals in cloud software. It ensures pricing psychology, trigger conditions, and tier differentiation are cleanly specified.
Role: Lead Digital Product Merchandiser specializing in PLG monetization surfaces and in-app checkout placement architecture.
Context
- Base Product Tier: {{base_product_tier}}
- Upsell Target Tier: {{upsell_target_tier}}
- Paywall Trigger Event: {{paywall_trigger_event}}
- Promotional Discount Structure: {{discount_structure}}
- Key Differentiator Features: {{key_differentiator_features}}
Task
Deliver an in-product merchandising specification for an upgrade paywall triggered by {{paywall_trigger_event}}, designed to seamlessly convert {{base_product_tier}} users into {{upsell_target_tier}} subscribers utilizing {{discount_structure}}.
Method
- Detail the contextual modal trigger criteria for {{paywall_trigger_event}} without degrading user workflow.
- Construct the visual hierarchy for the upgrade modal, highlighting {{key_differentiator_features}}.
- Define the pricing display architecture, showing annual vs. monthly billing toggles and {{discount_structure}}.
- Draft the comparative feature matrix pitting {{base_product_tier}} limits against {{upsell_target_tier}} capabilities.
- Specify trust signals, security compliance badges, and money-back guarantee placements.
- Formulate fallback and dismissal handling, including soft downsell offers and reminder cadences.
- Outline telemetry and analytics tagging requirements for click-through, dismissal, and conversion events.
Constraints
- Must clearly contrast features between {{base_product_tier}} and {{upsell_target_tier}}.
- Must provide explicit copy guidelines that focus on workflow value rather than generic sales jargon.
- MUST NOT allow misleading price framing; total annual cost must be clearly stated alongside monthly equivalents.
- MUST include a dismiss action that preserves the user's unsaved session state.
Output format
- Modal UX & Merchandising Structure (section-by-section component layout with character limits)
- Feature Comparison Matrix (markdown table: Feature, Base Tier Limit, Target Tier Value, Value Proposition)
- Price Framing & Discount Specification (pricing string examples, {{discount_structure}} rules, toggle states)
- Behavioral Triggers & Telemetry Schema (trigger condition, cooldown period, event tracking tags)
Self-review
- Does the paywall clearly highlight {{key_differentiator_features}} relevant to {{paywall_trigger_event}}?
- Are the calculations and presentation for {{discount_structure}} unambiguous?
- Can a frontend engineer and product designer build the paywall directly from this specification?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.