# Paywalls, upgrade prompts, and pricing

This is a SaaS application of *Building a StoryBrand* (2017), chiefly its chapters on the customer's desire, guide, plan, action, failure, and success. The book does **not** prescribe paywall layouts, billing language, or tier structures.

## Start with the interrupted goal

At a product paywall, the customer usually has a task in progress. Identify that task before writing. The smallest useful story is: **what they want to finish → what paid access adds → how to continue**. A broad brand slogan is weaker than wording tied to the action they just tried.

Choose the message for the trigger:

| Trigger | Main question to answer |
|---|---|
| Feature gate | What useful result does this paid feature unlock for my current task? |
| Usage limit | What limit did I reach, and what additional capacity does the paid plan actually provide? |
| Trial ending | What work can I continue with a paid plan, and what happens if I do nothing? |
| Upgrade after a success | How does the next tier help me get the next result? |
| Pricing or checkout | Which plan fits my need, what exactly is included, and what will I pay? |

Lead with a concrete outcome. Connect each listed feature to a customer benefit; do not just enumerate entitlements. Use one primary action that accurately describes what the click does: opening checkout, starting a trial, changing a plan, or completing a purchase. If purchase is a separate step, do not imply that clicking the button immediately unlocks the feature. Offer a less committed path only when it helps the user decide, such as comparing plans or returning to their work.

## Reduce the buyer's uncertainty

The book's **process plan** clarifies the path. On a paywall, this may be one line: choose a plan, complete checkout, then resume the original task—only if the product supports that flow. Its **agreement plan** resolves fear through a real commitment: a genuine trial, published cancellation policy, support promise, or refund policy. State such terms precisely and verify them in the current product.

Show the information needed to make an informed decision at the point of choice: price, currency, billing interval, trial length and what follows it, relevant usage limits, and any meaningful plan restriction. On pricing pages, distinguish tiers by the customer need and outcome each serves, then make their included features and limits easy to compare. If billing can be monthly or annual, make the selected interval and total charge clear. Avoid a vague “best value” label without a real basis.

Use proof in proportion to the commitment. A small feature gate may need a truthful example of the result; a high-cost plan may need verified customer outcomes, a product walkthrough, or a clear explanation of setup and support. Use empathy in plain language about the task, and let verifiable facts demonstrate competence.

## Write for the surface

- **Compact modal:** outcome headline; one sentence explaining the paid value; the few benefits that matter to this trigger; accurate terms; primary CTA. Keep the user's current task visible in the wording.
- **Full paywall:** add proof, a simple process, and answers to the main objections when the decision warrants the space.
- **Pricing page:** help customers choose among plans, show what's included and what costs extra, and keep each plan's CTA aligned with its actual flow.
- **Trial-ending message:** state the real consequence of expiry and the benefit of continuing. Do not imply data deletion, lost work, or a deadline unless true.

The negative stakes should be factual and light. Never invent scarcity, countdowns, savings, testimonials, outcomes, or a policy promise. Avoid guilt-driven decline links. A guide helps the customer decide confidently, including when staying on a free plan or leaving is reasonable.

Before shipping, inspect the actual entitlement and checkout behavior. Verify that the paid plan unlocks the named capability, the displayed terms match configuration, and the button destination does what the copy promises. If a claim cannot be checked, remove it or flag the exact missing fact for the user.