A paid-feature demo should say who can access the feature before showing the action. If the recording uses a paid account while the caption invites a trial user to repeat it, the video is misleading even when every click is real. Put the plan and prerequisite beside the task, then show the result in the current product.
This guide uses a fictional workflow app called Cornerstone. Its feature names and accounts are examples, not Prolifik entitlements or customer results.
Define the account used in the recording
Cornerstone's team wants to show an advanced export view available to a paid team account. The presenter is signed in as an owner with access to that view. A new user on a trial may see a locked menu or a different limit.
Record the exact plan label, role, product version and workspace state privately. Use the name the product currently displays. Do not write “available on all plans” from memory, and do not infer a trial allowance from a paid account's screenshot.
| Source condition | Visible in the short | Private evidence note |
|---|---|---|
| Paid plan | A concise on-screen qualification | Current plan page or entitlement test |
| Owner role | Speaker or caption names the role | Test account and permission state |
| Sample data | Clean fabricated records | Source file/version |
| Result | Real exported view or file | Accepted source recording and output |
A gated feature can still be compelling when the gate is honest. Hiding it to make the video feel universal creates a support problem later.
Make the task specific
For Cornerstone, the short's task is “choose which project fields appear in a team export.” Start with the current selection, change one field, export a sample file and inspect the result. Do not advertise a general analytics or compliance capability because the export screen contains several settings.
The product may require an owner to enable the feature. Show that prerequisite or state it before the first action. If a trial user needs to upgrade, the video can name the paid requirement without turning every shot into a pricing pitch.
The product demo script guide helps keep the action and result complete. This page adds the access condition that must travel with both.
Keep the plan text attached to the claim
A small disclaimer at the very end may not reach someone who watches only the first seconds or sees a screenshot. Put “Paid team plan” or the current precise label near the feature demonstration. Do not reduce it to decorative gray text.
If the product's plan names differ by region or contract, use wording the sales and product teams approve. A video cannot establish a universal entitlement from one account. Check the current public plan page and the actual account access together, because marketing copy and implementation can drift.
For Prolifik itself, current pricing separates Content Studio videos, Clipper source minutes and AI Studio credits. Do not treat a credit allowance as a permission to use every model or feature on every plan. This Cornerstone example remains fictional.
Record a clean paid-account source
Use a sample workspace with invented records. If the export contains customer names, replace the source before capture rather than blurring one column in a long recording. Close unrelated tabs and notifications.
Capture the entire task: plan-qualified starting view, selection, export request and actual file or result. If the export takes time, keep the pending state or add an honest time bridge. Do not splice a different paid account's result into the recording.
The app export workflow guide covers selection scope and downloaded artifact proof. The paid-feature demo also needs the access gate.
Test the view a non-paying user would see
A product owner should confirm how the feature appears to someone without access. It may be hidden, disabled or visible with an upgrade path. Do not show a specific lock screen unless that is the current product behavior.
If the script says “start your free trial to use this,” test that claim with a real trial account. If the feature requires a paid subscription, write a different CTA and explain the condition plainly. A trial invitation can still be useful for exploring the product, but it should not promise this specific action on the trial.
The same standard applies to upgrade prompts. Do not claim a plan change happens automatically after clicking a pricing link. Keep feature access, checkout and completed upgrade as separate states.
Package the footage without changing its meaning
Prolifik Video Hook & Demo can build a short around supplied real footage. It does not grant Cornerstone plan access or create the paid screen from a URL. The current format replaces the recording's source audio with library music or silence, so a spoken plan caveat must appear in visible copy if this path is used.
Inspect the returned short at phone size. Check that the plan qualification, selected field and actual result all survive the crop and caption treatment. If the gate disappears, revise the source or overlay before publication.
Recheck after plan changes
Plans, trial terms and feature entitlements change. Keep the current source date, account type and approved copy beside the export. If the feature moves to another tier, update the video and public description together. Do not leave an old short promising access that a new user cannot obtain.
The accepted file, scheduled item and public post are distinct. Confirm the live item points to the current feature and plan before calling the demonstration complete.
Build a short from the permitted feature capture
Use a current paid-account sample recording and keep the plan condition visible in the returned video.
Explore Video Hook & DemoFacts checked 2026-11-02. Worked examples are illustrative unless a real source is identified.
- Prolifik: current pricing Checked 2026-11-02
- Prolifik: Video Hook & Demo Checked 2026-11-02