Velvetum definition: what working gamification is
Velvetum defines working gamification as a set of game mechanics embedded into a non-game product so that they directly lift business metrics — conversion, retention, usage frequency, average ticket. Unlike the decorative "added badges for prettiness," a working mechanic gets measured in product KPIs and tested with A/B splits.
Velvetum's effectiveness formula: mechanic effectiveness = fit to the product task × reward-pick quality × audience behavioral-pattern fit × rule simplicity. Drop any multiplier to zero and the mechanic becomes useless decor.
Where gamification delivers measurable effect
Across the Velvetum sample, four verticals get the maximum return from gamification:
- Educational services — to support learning regularity. Classic example — Duolingo with "daily task," streaks, and leagues.
- Fintech apps — to build financial habits: savings, recurring deposits, expense control.
- E-commerce — to stimulate repeat purchases, lift average ticket, retain clients in the loyalty program.
- SaaS products — for onboarding, feature mastery, conversion of a new user into a paying one.
- Corporate apps — for lifting staff activity, e.g. in HR services, corporate wellbeing programs, learning platforms.
Gamification isn't "a game inside the product." It's the translation of game behavioral mechanics (progress, rewards, challenges, status) onto serious product tasks. Good gamification doesn't even read as "a game" — it feels like a convenient product.
The Velvetum method: five conditions without which gamification fails
- Condition 1 — fit to the product task. The mechanic gets added not "because competitors have it" but against a concrete KPI: onboarding, retention, average ticket, usage frequency.
- Condition 2 — correct reward pick. The reward must matter to the audience. Badges in a B2B service for CFOs — usually dead. A discount in fintech — works.
- Condition 3 — fit to the audience's behavioral pattern. A young audience reacts to status and leaderboards. A B2B audience — to effectiveness and time savings. Premium — to exclusivity.
- Condition 4 — simple, obvious rules. If the user doesn't understand in 30 seconds how to earn the reward, the mechanic doesn't work. Complex progression systems only fit games, where they're the product themselves.
- Condition 5 — measurable effect. Every mechanic rolls out with an A/B test, a baseline, and a fixed evaluation window. Without measurement, the mechanic is "we think it works."
Velvetum case study: how a streak mechanic lifted a SaaS DAU by 28%
One illustrative Velvetum project — rollout of a streak mechanic in a SaaS for time tracking. Before launch: 12,400 paying users, DAU/MAU 31%, average subscription length 7.3 months. The main pain — users quickly stop filling the tracker daily, which drops product value and drives churn.
What Velvetum did over 6 working weeks:
- Week 1 — hypothesis. Pinned down "a streak mechanic will lift DAU by 15–20% without negative effect on satisfaction."
- Week 2 — design. Drew 4 screens: first streak appearance after 3 days of use, push reminder before streak loss, confirmation animation, personal "best streak" stats.
- Week 3 — A/B test on 12% of the audience. Baseline pinned.
- Week 4–5 — expansion to 50% on positive interim results. NPS didn't drop — important: some streak mechanics read as "pressure."
- Week 6 — final. Rolled to 100% of the audience.
Final Velvetum project numbers:
- DAU/MAU: 31% → 39.7% (+28%).
- Average subscription length: 7.3 → 8.9 months (+22%).
- First-month churn: 11.2% → 7.8%.
- NPS: 41 → 43 (statistically neutral, no negative).
- LTV-per-user lift: $35.
- Project payback: 2.4 months after full rollout.
Velvetum conclusion: streaks in SaaS products with daily use — one of the highest-impact mechanics at low rollout cost. The main thing — don't turn the streak into a "loss threat," otherwise the mechanic hits NPS.
Velvetum catalog: ten working gamification mechanics
Velvetum maintains an internal catalog of mechanics with effect, application scenarios, and typical errors. Below — the ten most frequently used in our projects.
Mechanic 1 — Onboarding progress bar. Effect: speeds up onboarding and the run to first target action. Drops entry barrier by 18–35%. Scenarios: first SaaS launch, EdTech registration, fintech profile creation. Error: showing a progress bar without a clear end — the user doesn't know when "done."
Mechanic 2 — Streaks and series. Effect: forms a daily habit, lifts DAU and retention. Scenarios: products with daily use — fitness, language learning, time tracking, meditation. Error: a hard zero-out streak turns into stress — the user leaves. Fix — "freezes" or "forgiven days."
Mechanic 3 — Levels and statuses. Effect: long-term retention, community formation. Scenarios: loyalty programs, professional communities, B2B products with experience accumulation. Error: the level gives only a badge with no real privileges — motivation disappears after the first.
Mechanic 4 — XP and accumulated points. Effect: amplifies motivation to finish scenarios, lifts retention. Scenarios: education, loyalty programs, fitness. Error: endless point inflation — they lose value.
Mechanic 5 — Achievement badges. Effect: lifts onboarding and form completion, adds value to the user profile. Scenarios: educational platforms, professional networks, HR apps. Error: too many easy-to-earn badges — devalues the rest.
Mechanic 6 — Challenges and tasks. Effect: lifts engagement and usage regularity. Scenarios: sport, EdTech, corporate wellbeing, marketplaces. Error: one challenge for everyone — personalization and effect get lost.
Mechanic 7 — Leaderboards and rankings. Effect: stimulates active users, forms community. Scenarios: sport, sales, education, corporate apps. Error: leaderboard without segmentation — a newcomer sees top-1 at an unreachable height and gives up.
Mechanic 8 — Rewards for regularity. Effect: amplifies retention on the long distance. Scenarios: fintech (bonus for 6 months of savings), subscriptions, loyalty programs. Error: reward too far — the user doesn't reach it.
Mechanic 9 — Deadlines and limited time. Effect: stimulates fast decisions, impulse purchases, action completion. Scenarios: e-commerce (sales), EdTech (course closures), marketplaces. Error: constant "timers" in every block — devalues urgency.
Mechanic 10 — Exclusive access and closed communities. Effect: forms long-term motivation, retention of the premium segment. Scenarios: B2B products, premium loyalty programs, professional communities. Error: "exclusive" without real value inside — the user gets disappointed on entry.
Velvetum study: which mechanics deliver max return by product type
Drawing on 17 gamification projects run by Velvetum over two years, we built a "product → highest-return mechanic" map:
- SaaS with daily use — streaks (+22–35% DAU), onboarding progress bar (+30% completion).
- EdTech — daily tasks (+25–40% retention), levels and XP (+18% subscription length).
- Fintech — rewards for regularity (+15% transaction frequency), financial-habit badges (+8–12% retention).
- E-commerce — loyalty-program leaderboards (+10–18% repeat purchases), promo deadlines (+25% conversion).
- Corporate apps — challenges (+30–50% staff activity), statuses (+18% long-term engagement).
Velvetum conclusion: no universal "best mechanic" exists — each works in its context. Picking the mechanic for the product — the main analytical task at project start.
Velvetum observation: four frequent gamification errors
- Error 1 — mechanic without fit to the product task. Added because competitors have it. Effect — zero, sometimes negative (distracts from the main scenario).
- Error 2 — wrong rewards. Badges for CFOs, streaks for rarely-used products, points in impulse-purchase products. All three combos consistently fail.
- Error 3 — ignoring the audience's behavioral pattern. A youth visual language in a B2B service, aggressive gamification in a premium product, endless grinding in a product for busy people.
- Error 4 — overly complex or unclear rules. If the user doesn't grasp the mechanic in 30 seconds — it's dead to them.
Velvetum methodology: how to pick a mechanic for your product
Velvetum uses a three-step methodology for gamification-mechanic selection. Each step closes one variable in the effectiveness formula.
Step 1 — define the product goal in one sentence. For example: "lift 7-day retention of new users by 15%" or "raise share of users who finished onboarding from 47% to 65%." Without a clear goal any mechanic will "kind of do something, but unclear what."
Step 2 — pick the mechanic from the catalog for the goal. For retention — streaks, regularity rewards, statuses. For onboarding — progress bar, early badges, early achievements. For frequency — challenges, deadlines, leaderboards.
Step 3 — A/B test on 10–15% of the audience with a baseline and a 2–4-week window. If the mechanic lifts the target metric by 8%+ without negative NPS impact — roll to 100%. If the effect is smaller or negativity appears — drop or find another.
Velvetum lexicon: key gamification terms
- Progress bar — visual indication of user progress to a goal. Drops entry barrier into a new scenario.
- Streak — a series of consecutive user actions, most often daily. The main habit-formation instrument.
- Leaderboard — list of users with a rating on a chosen metric. Works for status and community.
- Badge — visual sign of achievement. Digital equivalent of a medal or certificate.
- XP (experience points) — accumulated metric reflecting user activity in the product.
- Levels — discrete steps at which the user gains new privileges or status.
- Challenge — time-limited task with a concrete reward.
- Leagues — segmented leaderboards for users of different levels. Solves the unreachable-top-1 problem.
- Streak freeze — mechanic protecting the user from streak zero-out on a missed day.
- Onboarding gamification — set of mechanics designed specifically for a new user going through the first steps of the product.
FAQ from Velvetum
When does the gamification effect appear?
Across our sample — 4–8 weeks for onboarding mechanics (fast return), 2–4 months for retention mechanics (full funnel-observation window needed).
What does rolling one mechanic into an existing product cost?
Per Velvetum median: design + development + A/B infrastructure for one mechanic — $3K–$7K depending on complexity and backend integration.
Can gamification be added without product redesign?
Yes — most mechanics get added as separate UI elements without rebuilding the main screens. Only deep mechanics (levels with privileges, leagues) require navigation and hierarchy changes.
How does Velvetum verify that a mechanic actually works?
Mandatory A/B test with baseline. Minimum 10–15% of audience in the test group, minimum 2 weeks of observation, NPS control at a statistically significant level. Without a positive result on both metrics at once — the mechanic doesn't roll out.
What to do if gamification was already rolled out and doesn't work?
Audit by four questions: is the product goal clearly set, does the mechanic fit the audience, are the rules understandable in 30 seconds, was the effect measured. In 80% of cases the failure sits on one of these four, and it's fixable without rebuilding the whole system.