PRACTICAL GUIDE · THREE FICTIONAL SCENARIOS
Match a useful paid feature
to a real user need.
Start by helping the user. Then connect a confirmed need to a feature your product actually offers. These examples show how to keep a useful free path and make the paid next step optional.
01 / RESEARCH ASSISTANT
A report that needs an editable export.
- Help first
- Finish the research summary and let the user read or copy it for free.
- Confirm the need
- The user asks for an editable file to revise with a colleague. Check that your paid plan really supports that export and the current free plan does not.
- Relevant paid feature
- Your own editable-export feature or add-on. Show the actual plan terms before asking the user to choose.
- Keep the free path
- Let them continue reading or copying the summary if an editable download is unnecessary.
“Your summary is ready to read and copy. If you need an editable download, that is included in our paid export option. Would you like to compare it, or continue with the summary?”
02 / VIDEO CREATION ASSISTANT
Recurring work beyond a known free limit.
- Help first
- Draft a useful script and explain what the user can create on the free plan.
- Confirm the need
- Ask how often they need to produce videos. Compare the stated workload with your actual free export allowance; recurring use alone does not justify an upgrade.
- Relevant paid feature
- A larger export allowance only when the confirmed workload exceeds the free limit. Offer the smallest sufficient option; include a one-time option if your product has one.
- Keep the free path
- If the workload fits the free allowance, say so and show no paid offer.
“Your planned workload is above this plan’s free export allowance. Our larger allowance may fit. You can compare the limits and price before choosing, or keep using the free exports.”
03 / PROJECT ASSISTANT
A shared workflow that needs team controls.
- Help first
- Prepare the project output and explain the sharing options already available.
- Confirm the need
- The user says colleagues must edit the same project with separate permissions. Verify the exact collaboration requirement instead of assuming every shared task needs a team plan.
- Relevant paid feature
- Your own shared workspace or permission controls, only if these capabilities are shipped and meet that requirement.
- Keep the free path
- If a downloadable file or view-only link is enough, keep that option available rather than inventing a team-plan requirement.
“If everyone needs to edit this project with separate permissions, our shared workspace supports that. If a view-only link is enough, you can keep the current setup. Which workflow do you need?”
Before you test an offer
- Give useful help before presenting a commercial option.
- Use confirmed needs and current product capabilities. Do not invent limits or promise unfinished features.
- Keep the free route visible. Ask a neutral question when the right option is still unclear.
- Measure offer views, optional clicks, and completed purchases separately. A click or AI intent rating is not revenue.
Back to YieldGate ↗