How to Explain a Pricing Plan with Motion Graphics
Two plans both say “from $6.” One charges every unit at the rate of the final tier. The other charges each portion of usage at its own rate. A video can display the same attractive starting price for both and leave the viewer with two very different wrong ideas about the bill.
A pricing explainer video should leave someone able to calculate a bill: identify the counted units, apply the pricing rule, and recognize the payment period. The useful story is therefore a calculation: what is counted, which rule applies, and how that produces the amount due.
Motion can reveal this calculation gradually. It can also conceal it. A low monthly equivalent may arrive first while an annual commitment appears too late to read. A counter may race through quantities without showing when the rule changes. A discount may dominate the screen while its expiration disappears into a transition.
Start with a complete bill and work backward to the sequence: identify the quantity, apply the rate, and keep the payment period beside the total.
Begin with the question the viewer actually needs answered
“Explain our pricing” can mean several things. A prospective buyer might need to choose between plans, estimate a usage bill, understand annual payment, or find out what happens after an allowance is exhausted. These are related questions, but they need different demonstrations.
Choose one primary question for the video. For a usage plan, it could be: “What would six units cost this month?” For an annual subscription, it could be: “Why does the page say $29 per month if I pay $348 today?” For a seat-based plan, it could be: “Which people count as paid seats?”
A narrow question is not a license to omit conditions that change its answer. Instead, it makes those conditions easier to identify. If the amount depends on currency, billing period, active seats, or a minimum commitment, those facts belong in the calculation. A decorative product feature list does not.
Write the expected answer before making the storyboard. If the team cannot agree on the calculation in plain text, animation will amplify the disagreement. Resolve the pricing rule with the responsible product or billing owner, then decide how to explain it visually.
Explain volume and graduated pricing with Stripe’s tier example
Stripe’s tiered-pricing documentation uses a hypothetical font business to distinguish two models. Its example tiers are $7 for units one through five, $6.50 for six through ten, and $6 beyond ten. At six units, volume pricing totals $39; graduated pricing totals $41.50.
The difference is where the rate applies. Volume pricing uses the reached tier’s rate for all six units. Graduated pricing charges the first five at $7 and the sixth at $6.50. The same quantity and rate table therefore require different visual explanations.
For a volume-pricing animation, a single rate can connect the complete quantity to the total. For graduated pricing, separate groups should remain visible long enough to show why earlier units retain their earlier rate. Simply replacing “$7” with “$6.50” above the whole group would communicate the wrong model.
This is an editorial consequence of the arithmetic. It does not require a complicated animation. Six marks, a visible tier boundary, and a persistent subtotal can explain more than a spinning pricing card if their relationships are accurate.
Make a bill small enough to understand but complete enough to trust
A worked example should have a defined quantity, a counted unit, a period, a currency, and a total. State any exclusions that would otherwise change the viewer’s interpretation, such as taxes excluded from an illustrative subtotal. Do not introduce unrelated exceptions merely to make the screen look comprehensive.
For the six-unit graduated example, the visual sequence can begin with six labeled units. Group five together and leave one separate. Show “5 × $7 = $35” beside the first group and “1 × $6.50 = $6.50” beside the second. Then bring both amounts into “$41.50 for six units this month.”
The final state is important. If the subtotals vanish before the total appears, the viewer has to remember the numbers while also following the movement. Keep the basis of the calculation visible when introducing the result. A complete equation gives someone a chance to check the explanation rather than simply accept it.
Avoid adding a fee or discount to this example unless it serves the video’s main question. Every additional term introduces another relationship to understand. When the actual product has a mandatory base fee, it must be included; when a complicated edge case is optional, it may belong in a separate example beside the video.
Show the boundary where intuition can fail
A single quantity can demonstrate arithmetic without revealing how the plan behaves. A useful second scene changes the quantity across a boundary. The question becomes: what changes in the rule, and what stays the same?
For graduated pricing, moving from five to six units adds one unit in the next tier. The first five remain in place at their original rate. Animate the new unit into the second group rather than recoloring every unit. The movement reinforces the fact that the earlier subtotal is preserved.
For volume pricing, crossing the boundary can change the rate applied to the whole quantity. In a separate fictional example, suppose up to 100 units cost $10 each and 101 or more cost $8 each. One hundred units would total $1,000; 101 would total $808. The extra unit lowers this example’s total because the lower rate applies to every unit.
Do not silently interpolate a cost curve between discrete quantities. A smooth curve can imply fractional units or a continuous rule the plan does not support. If the product counts whole seats, show whole seats. If usage can be fractional, state the actual unit and rounding behavior before designing the counter.
The five-to-six transition makes the difference especially clear. Both models start at $35 for five units. Volume pricing then reaches $39, an increase of $4, even though the sixth unit’s displayed rate is $6.50. The reason is that the first five units also receive the lower rate. Graduated pricing reaches $41.50 because only the new unit receives that rate. At seven units the totals become $45.50 and $48 respectively.
These are good storyboard checkpoints: show five units with their current total, reveal the sixth, and then show exactly which rate labels change. In the volume version, change all six rate labels together. In the graduated version, leave the first five untouched and add a separate subtotal for the sixth. The viewer can then see the billing rule instead of having to reconstruct it from the final amount. Hold the two subtotals beside the grand total long enough for someone to add them.
Keep price, unit, and payment timing together
The fictional annual subscription is simpler: $348 paid annually, equivalent to $29 per month. Yet it is easy to animate badly. Displaying a large “$29” for several seconds before revealing the annual payment creates an incomplete impression during most of the scene.
Treat the number, unit, and payment condition as one information group. They can have different visual emphasis without arriving as unrelated facts. The monthly equivalent may be the largest type, while “$348 billed annually” sits immediately below it and shares its entrance and stable hold.
Our fictional subscription scene uses this relationship: both lines settle at 0.8 seconds and remain stable through 4.8 seconds. A more complex bill may need a longer hold or a staged calculation.
Do not let a pricing transition erase the condition while the headline number remains. If a card shrinks into a corner and only “$29” survives, the small version has become a different communication. Review every composition state, including the end card and any social crop, as a pricing statement in its own right.
Animate explanation, not the amount due
A counting number often looks polished, but its meaning is ambiguous. Is it live usage, a running subtotal, an estimate, or simply a reveal effect? The viewer should not have to guess which of these is happening.
When the amount is fixed, revealing a stable value may be clearer than counting through intermediate prices that no one will pay. When the purpose is to explain accumulation, a running total can help, but it should stay connected to the units being added. The counter is then a calculation rather than a visual flourish.
Be especially careful with discounts. Animating from $100 down to $60 can communicate a comparison, but the basis of that comparison must be visible. Is $100 the previous price, a monthly alternative, or a price before an introductory offer? The typography and motion cannot supply a definition the underlying offer does not contain.
Avoid using a dramatic movement to compensate for an unclear label. If a viewer cannot explain what “usage” counts, adding a thousand moving dots does not solve the problem. Replace the abstract label with a concrete unit or show one representative event being counted before scaling to the total.
Make uncertainty visible when the bill is an estimate
Some pricing videos demonstrate an exact bill under fixed assumptions. Others show an estimator whose result changes with future behavior. These are different promises. A precise-looking number can make an estimate feel more certain than it is.
Label the inputs that are assumed rather than observed. For example, an estimate might assume 12 active seats throughout one month with no mid-period changes. Showing that assumption near the calculation helps the viewer understand what would make their own amount differ.
If the real system includes variable usage, consider a small number of meaningful scenarios instead of one falsely universal answer. Low, typical, and high examples can be useful when their definitions are explicit. They should not be presented as measured customer distributions unless such data exists.
Do not invent rounding, proration, tax, or exchange-rate behavior to make the example more realistic. Either verify the relevant rule or keep the teaching example within a boundary where it is not needed. A smaller exact explanation is more useful than a detailed fictional invoice presented with real-product confidence.
Design the screen for comparison and checking
A price scene often has at least three reading levels: the amount, the rule that explains it, and context that limits the example. Their hierarchy should guide attention without making the lower levels effectively unreadable.
Use proximity to show which labels belong to which number. Keep the unit adjacent to the amount, not in a distant legend. Use repeated alignment for comparable tiers. If the viewer is comparing two plans, keep shared assumptions in the same position so differences are easy to inspect.
Color can distinguish the active tier or newly added quantity, but do not make color the only way to identify a group. Labels, brackets, or consistent spatial grouping can preserve the explanation in a still frame and for viewers who perceive color differently.
Check the result at the actual distribution size. A qualification that is readable in a full-screen editor may disappear when the video is embedded in a small card. If the condition is necessary to understand the price, the composition must protect it. Making the number smaller may be the correct tradeoff.
Keep later edits attached to the pricing rule
Pricing assets often change because a campaign changes, not because the production team decides to revisit the calculation. Someone replaces the headline amount and assumes the remaining animation is still valid. The old quantity, subtotal, billing period, or end-card condition can survive unnoticed.
Keep the inputs and displayed totals together in the project. A change from annual to monthly billing should trigger a review of the amount due, the comparison basis, the payment label, and every scene that reuses the offer. Treat a visible equation as a dependency, not a collection of unrelated text layers.
A quick regression exercise is to select one ordinary quantity and one boundary quantity, calculate both independently, and compare them with the export. Check the ordinary and boundary quantities again after any price edit.
Review by asking someone to calculate, not to approve the style
After watching, a reviewer should be able to answer the video’s original question. For the graduated example, ask what seven units would cost. The expected result is $48: five at $7 and two at $6.50.
An incorrect answer gives useful diagnostic information. If someone applies $6.50 to all seven units, the grouping or transition may have implied volume pricing. If they cannot identify the billing period, the period label may have appeared at the wrong time or been visually subordinate beyond usefulness.
Also inspect the exported video at the boundary frames. Read the last stable frame before an exit. Read the first frame after a plan switch. If a condition briefly disappears while its amount remains, the animation has created a misleading intermediate state even if the final card is correct.
The goal is not to make pricing feel simple by hiding its structure. It is to make the relevant structure understandable. A successful pricing explainer leaves the viewer with a method for predicting a bill and a clear sense of the assumptions behind that prediction. The animation has earned its place when it helps that reasoning happen.