ShortMax Clone Business Model: Retention Paid in Inventory
A growth-led operator earns in a specific order. The expensive part is not producing the next title, it is buying the next viewer, so the levers that matter first are the ones that make a returning viewer cheaper than an acquired one. Here that is done by paying retention in coins you issue rather than cash you spend, and the reason it can be measured at all is that every coin movement carries one of seven typed ledger codes.
Design My Revenue Model →See PricingWhy Retention Paid in Inventory Changes the Model
The whole argument for a growth-led short-drama platform sits in one comparison.
Acquiring a viewer costs cash and the price rises every quarter. Returning a viewer costs coins, and coins are inventory you issue at a price you set. A check-in ladder that pays a viewer to come back on day four is buying a return visit for the wholesale cost of an episode unlock rather than the retail cost of a click, and that arithmetic is the reason the reward surfaces exist at all.
What makes it a business model rather than a hope is the ledger. Every coin movement is written with one of seven typed codes, so a coin sold, a coin issued for a check-in, a coin paid for a referral and a coin spent on an unlock stay distinguishable forever. Without that separation the console can tell you a balance and nothing else, and a balance cannot answer the only question that matters here: what did retention cost, and did it come back.
This is also why the reward caps are operator settings rather than constants. The first month of real behaviour will tell you the ladder is too generous or too thin, and you need to be able to move it that week.
Five Revenue Lines and One Growth Loop
What the platform can charge for, and what feeds it.
Coin pack sales
Coin SKUs with bonus coins and an offer price, sold through hosted checkout or store billing and credited to a purchased balance that does not expire. This is the primary cash line, and the ledger keeps it separate from every coin you gave away.
VIP subscription windows
Plans priced by validity and validity type, granting an entitlement window that opens locked episodes while it runs. On a growth-led launch VIP usually arrives after the reward loop, because it converts your best payers onto your cheapest tender if it lands too early.
Rewarded ad inventory
Ads as a third tender for viewers who never spend cash, under an operator-set daily cap. AdMob on the Flutter store build is the live path; the web surface is a simulated timed preview, so model ad revenue against the store build.
Per-episode coin unlocks
Coins spent against locked episodes are where issued coins and sold coins finally meet. Because both are ledgered, you can see what proportion of your unlock volume was paid for in cash and what proportion you funded yourself.
Campaign-driven repeat spend
The campaign desk with templates, audiences, scheduling and statistics writes an in-app inbox row per targeted user, working with no external service configured. Reaching your existing audience is the cheapest revenue in the building.
The loop that feeds all five
Seven day check-in ladder with streak, ad reward tasks under a daily cap, social follow bonuses, an email bonus, a login bonus, and a referral reward credited on signup. None of these are revenue lines; they are what makes the five above cheaper to fill.
Miracuves takes no percentage of any of these. The gateway you connect is yours, the AdMob account is yours, and the licence is one-time.
How the Category Itself Makes Money
The shapes that recur across short-drama operators, and where each one breaks.
| Approach | How it earns | Where it breaks |
|---|---|---|
| Coin unlocks per episode | Viewer buys coins, spends them at the lock | Dies if the lock lands before the story hooks |
| Reward-funded unlocks | Operator issues coins to return a viewer | Farmed within a week if the daily cap is loose |
| Subscription window | Flat fee opens locked episodes for a period | Cannibalizes coin revenue on a thin library |
| Rewarded advertising | Ad view becomes a third tender for the unlock | Needs store-build volume before it is material |
| Referral-led growth | Existing viewers acquire the next ones | Stops instantly if the reward is not visibly credited |
| Paid acquisition | Buy the viewer, recover through unlocks | Unmeasurable here, because there is no attribution |
The last row is the honest one. This build has no attribution, deep linking or UTM tracking, so a paid acquisition strategy needs tooling bought alongside it rather than assumed inside it.
Monetization Approaches, Ranked by Acquisition Cost
Cheapest viewer first. The order matters more than the mix.
| Source of the next viewer | What it costs you | Switch it on |
|---|---|---|
| A viewer you already have, returning | Coins you issue, at your wholesale cost | Day one, with the check-in ladder |
| A viewer brought by a referral | One operator-set reward, credited on signup | Day one, alongside the ladder |
| A lapsed viewer reached by campaign | Staff time, and nothing else | Week two, once there is a lapsed cohort |
| A viewer who watches an ad instead of paying | Nothing, and it earns ad revenue | With the store build, under a daily cap |
| A viewer from an organic social follow | One follow bonus, paid once | Once the social accounts exist |
| A viewer bought through paid media | Cash, rising, and unattributable here | Last, and only with external tooling |
Most operators run this list backwards, starting with paid media because it is the fastest to switch on, and discover the retention loop only after the acquisition budget is gone.
What a Coin Actually Costs You
Six things worth modelling before you set a single reward value.
All six are visible in the coin economy analytics because they are ledger codes rather than derived estimates. That is the difference between modelling and guessing after launch.
Which Lever to Switch On First
A launch order that assumes the library is small and the audience is smaller.
| Stage | Turn on | Leave off |
|---|---|---|
| Launch week | Coin packs, per-episode locks, check-in ladder, referral | VIP, rewarded ads, paid media |
| Weeks two to four | Campaign desk to lapsed viewers, social follow bonuses | VIP, until the library has depth |
| Store build live | Rewarded ads under a daily cap, device push via Firebase | Web rewarded ads, which are simulated |
| Library has depth | VIP windows priced against typical monthly coin spend | Nothing, but watch the cannibalization |
| Loop is measured | Paid acquisition, with external attribution tooling | Assuming console counts are attribution |
| Any stage | Tightening the daily cap and the ladder values | Waiting for a release to change them |
Every entry in the middle column is an operator setting in the console, which is why this sequence is a decision rather than a development schedule.
Three Ways Operators Run This Platform
The same build, configured around three different constraints.
The referral-led launcher
An operator entering a new market with almost no acquisition budget, using the reward ladder and the referral loop as the growth channel. Growth is slow at first and then compounds, and the whole plan depends on the reward being visibly credited.
- Referral reward set high enough to be worth mentioning to a friend
- Five login types, because sign-up friction is the whole funnel
- Daily cap set tight, then loosened once behaviour is known
The reactivation operator
An operator with an existing audience that has gone quiet. The campaign desk and in-app inbox are the main surface, and the reward ladder is what turns a single reopened session into a habit rather than a visit.
- Campaigns scheduled against lapsed cohorts, no external service needed
- Check-in ladder tuned so the streak reward lands on day seven
- Firebase configured so campaigns reach the device, not just the inbox
The multi-market operator
An operator running several locales at once, where the same library is monetized differently by market. The coin economics diverge sharply between markets, and the ledger is what keeps them separable.
- Five locales with right-to-left layout verified before launch
- Reward values and caps set per deployment rather than globally
- Revenue read per title and per episode, never per channel
The first shape is the one the platform was clearly designed around, which is why the reward and referral surfaces are more developed than the analytics that would measure a paid campaign.
Common Growth-Loop Mistakes
Five that are expensive to undo
An uncapped reward economy. It is farmed within a week, the coin stops meaning anything, and your paid tender dies alongside the free one. Set the daily cap before launch and tighten it early rather than late.
A referral that pays on a later event. A reward the referrer cannot see arriving is a reward nobody mentions to a friend. Crediting on signup costs more per referral and returns far more of them.
VIP launched on a thin library. An unlimited window on a small catalog moves your highest-paying viewers onto your cheapest tender and gives them very little back. Wait for depth.
Treating console counts as attribution. Signups and revenue by title are operational counts. They cannot tell you which campaign produced a viewer, and planning paid media as though they can is how budgets disappear without a finding.
Modelling ad revenue on the web build. The web rewarded-ad path is a simulated timed preview. AdMob on the store build is the live path, so ad revenue projections belong against store installs.
Four of these are configuration decisions you can correct in an afternoon. The attribution one is not, which is why it appears on every page of this bundle.
See the modelled deployment and the stated limitations
A modelled reference deployment for a referral-led launch, the six-step build process, and every limitation named in writing - on the Development Company page.
Frequently Asked Questions
How do I decide what the check-in ladder should pay?
Does Miracuves take a percentage of revenue?
Can I run different reward values in different markets?
What stops users from farming the rewards?
Can I measure which campaign brought a viewer?
When should VIP go live?
Model it against your own coin economics
Bring what an episode costs you and what you currently pay for a viewer. We will map the ladder, the cap and the referral amount against those numbers rather than hand you a projection we invented.
Explore the ShortMax Clone
Retention you pay for in inventory, not cash
Coin packs, VIP windows, rewarded ads and per-episode unlocks, fed by a check-in ladder, a referral loop and a campaign desk, all operator-set and all ledgered against seven typed codes on source you own outright.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by ShortMax.
“ShortMax Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to ShortMax, and how clients search for it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the ShortMax website or applications.
ShortMax and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
