Applied The Lora Playbook

Storefront Revenue Simulator

Last reviewed

Beginner

What you'll learn

~30 min
  • Work with an AI agent in plan mode to build an interactive HTML and JavaScript pricing calculator
  • Model platform revenue splits for Steam, Epic Games Store, and console storefronts
  • Simulate launch discounts, seasonal sales, wishlist conversion, and refund rates
  • Calculate net revenue across regional pricing tiers for US, EU, and Asia markets

What you’re building

You have a working thesis from the Retro Remake Market Tracker: BloodRayne as a mid-budget cult revival. This lesson’s illustrative planning range is a $6M-$15M budget (the span of the tracker’s placeholder comparables) and 300K-700K units; replace both with your own figures. Great. But how much money actually lands in your bank account per unit sold?

The answer is: it depends on where the sale happens, when it happens, and at what price. A $30 game sold on Steam at launch nets you $21 (after Steam’s 30% cut). That same game at 50% off during the Steam Summer Sale nets you $10.50. Sold on Epic? $26.40 at 12%, which applies after the first $1M per product per year (Epic takes 0% on that first $1M). Using this lesson’s assumed 30% console cut gives $21. Wishlist conversion, refunds, and regional prices are editable planning inputs; replace the defaults with your own evidence.

None of this is complicated math. But doing it manually for every scenario — different base prices, different discount schedules, different platform mixes — is tedious and error-prone. You are going to build an interactive calculator that lets you adjust every variable and see the revenue impact in real time.

💬The platform cut is the cost of distribution

Seeing “Steam takes 30%” for the first time makes people angry. But the cut pays for Steam’s reach and discovery features. Epic’s 12% cut (0% on the first $1M per product per year, per Epic’s revenue-share announcement; confirm current terms) sounds better until you realize their install base is smaller and their discovery features are weaker. The right question is not “which platform has the lowest cut” but “what platform mix maximizes total revenue.” This calculator answers that question.

By the end of this lesson you will have an HTML+JavaScript pricing calculator that models revenue across Steam, Epic Games Store, and console storefronts. It includes sliders for base price, launch discount, seasonal sale depth, wishlist count, conversion rate, and refund rate. It calculates net revenue per unit, projected total revenue, and platform-by-platform breakdown with regional pricing adjustments.

ℹSoftware pattern: Multi-variable financial calculator with real-time output

Multiple input variables, each affecting the final calculation, with the output updating in real time as you adjust any input. This pattern appears in mortgage calculators, investment return estimators, and SaaS pricing tools. The key technique is binding UI controls to a calculation function that re-runs on every change.


The showcase

Here is what the finished calculator gives you:

  • Platform cards: Steam, Epic Games Store, PlayStation/Xbox — each showing the platform’s revenue split, your net per unit, and projected units
  • Input controls: Base price ($10-$60 slider), platform mix (percentage allocation across stores), wishlist count, launch discount %, seasonal sale depth %
  • Steam tiered cuts: 30% on the first $10M, 25% on $10M-$50M, 20% above $50M, per Valve’s 2018 update to the Steam Distribution Agreement as widely reported (confirm in your Steamworks partner agreement) (Valve announcement) — the calculator applies the right rate based on projected revenue
  • Discount modeling: Launch week discount, first seasonal sale (a planning default of 3 months post-launch), deep sale (6+ months), each with configurable depth and projected volume multiplier
  • Wishlist conversion: Input your wishlist count, apply a planning default of ~15% first-week conversion (replace it with your own numbers), model how wishlists decay over time
  • Refund modeling: Editable planning default of 5%, applied across platforms
  • Regional pricing: Editable regional price factors and volume shares; the defaults are illustrative
  • Summary dashboard: Total gross revenue, total platform fees, total net revenue, effective platform cut (weighted average), revenue per development dollar (if you input your budget)

Everything is a single HTML file. No server, no build step, no framework. Open it in a browser and start adjusting sliders.


Before you start

If your agent is still open from the previous lesson, exit that session first (/exit or Ctrl+D). Create a clean folder for this lesson and open it:

Terminal window
mkdir -p ~/retro-remake/07-storefront-simulator && cd ~/retro-remake/07-storefront-simulator

In Windows PowerShell:

Terminal window
mkdir ~/retro-remake/07-storefront-simulator; cd ~/retro-remake/07-storefront-simulator

Or open the folder directly in your desktop agent app. Start your agent the way Workbench Setup showed.

Switch to plan mode

Switch to Plan mode inside your session (Shift+Tab, /plan, or the mode picker) so the agent confirms the storefront tier math, discount phases, and regional pricing formula before generating the HTML file.

The conversation

Say what you want

Ask for the single-file storefront revenue calculator in plain English:

I am modeling game storefront revenue. Help me build a self-contained browser calculator called storefront-sim.html that models Steam, Epic, and console cuts, sale phases, wishlists, refunds, and regional pricing. Ask me what you need first.

Answer its questions

Guide the agent’s questions with the platform revenue rules, sliders, and summary metrics:

If it asksYou might say
How should Steam, Epic, and console platform cuts be calculated?Steam uses 30%/25%/20% revenue tiers; Epic takes 0% on the first $1M per year then 12%; consoles use 30%.
What interactive sliders and defaults should it provide?Base price $30, 400K units, 65% Steam/10% Epic/25% console, 200K wishlists at 15% conversion, 10% launch and 40% seasonal discounts.
How should the four sales phases split total unit volume?Launch week 25%, months 1-3 full price 30%, first seasonal sale 25%, and month 6+ deep 50% discount 20%.
How should regional pricing and refunds work?Weight average price across US 100% (45%), EU 95% (30%), and Asia 50% (25%), with an editable 5% refund rate.
What summary metrics and scenarios should appear at the bottom?Gross, fees, refunds, final net, blended cut, ROI against an $8M default budget, break-even units, and four preset scenarios.
ℹReference notes to hand the agent (or check against)click to expand
  1. Input Controls (all bound to oninput for real-time updates):

    • Base Price ($10-$60 slider, default $30), Total Unit Projection (default 400,000), Platform Mix (65% Steam, 10% Epic, 25% Console; warn if total != 100%), Wishlist Count (default 200,000), Wishlist Conversion Rate (5-30% slider, default 15%), Launch Discount (0-30%, default 10%), Seasonal Sale Discount (0-75%, default 40%), Refund Rate (0-15%, default 5%), Budget ($8M default), Regional Pricing (100% US at 45% volume, 80-110% EU default 95% at 30% volume, 30-70% Asia default 50% at 25% volume).
  2. Platform Revenue Models:

    • Steam: 30% on first $10M, 25% on $10M-$50M, 20% above $50M (planning assumption from Valve’s 2018 tiers; confirm in your Steamworks agreement; Valve announcement: https://steamcommunity.com/groups/steamworks/announcements/detail/1697191267930157838). Calculate blended effective cut on projected Steam gross revenue.
    • Epic Games Store: 0% cut on the first $1M of revenue per product per year (resets each 1 January), then 12% on the portion above $1M.
    • Console (PlayStation/Xbox): 30% platform cut (planning assumption; confirm with each platform holder; note console dev kit costs separately).
  3. Sales Phases, Wishlists, Refunds, and Regional Math:

    • Four Sale Phases: Phase 1 Launch Week (25% of units at base minus launch discount), Phase 2 Full Price Window months 1-3 (30% at base price), Phase 3 First Seasonal Sale months 3-6 (25% at base minus seasonal discount), Phase 4 Deep Discount month 6+ (20% at 50% of base price).
    • Wishlist Economics: First-week conversion (wishlistCount * conversionRate), sanity-checked against total units (note if >50% of total units), plus illustrative period conversion rates at month 1 (15%), month 3 (8%), month 6 (4%), month 12 (2%) labeled as editable planning defaults, not industry benchmarks or cumulative rates.
    • Regional Weighted Average Price: (US% * base) + (EU% * base * EU_factor) + (Asia% * base * Asia_factor), used across downstream revenue calculations.
    • Preset Comparison Table (Scenario | Price | Units | Steam % | Net Revenue | ROI): Conservative ($30, 200K, 70% Steam), Base Case ($30, 400K, 65% Steam), Optimistic ($35, 600K, 60% Steam), Illustrative Comparison Scenario ($40, 300K, 80% Steam).

Read the plan

Before approving the agent’s plan, check four details:

  1. Tiered Steam and Epic cuts: Steam applies marginal 30% / 25% / 20% tiers at $10M and $50M, and Epic applies 0% on the first $1M of Epic gross revenue per year and 12% only above $1M.
  2. Regional weighted price drives phase math: The weighted average regional price flows into all four discount phases (Launch Week, Full Price Window, First Seasonal Sale, Deep Discount) rather than using the raw US base price.
  3. Wishlist and refund caveats stay explicit: Wishlist conversion decay and the 5% refund rate are labeled as editable planning assumptions, and the platform mix warns if Steam + Epic + Console does not equal 100%.
  4. Single self-contained HTML file: All CSS and pure JavaScript live inside storefront-sim.html with oninput handlers updating the summary dashboard and four preset scenarios in real time.

If the plan applies a flat 30% on Steam or a flat 12% on Epic from dollar zero, steer it before approving:

Apply Epic's 0% cut to the first $1M of Epic gross revenue per year and 12% only to the portion above $1M.

Approve the plan once all four items are in place, and ask the agent to save a Git checkpoint after creating storefront-sim.html.

💡One file, zero dependencies

This is deliberately a single HTML file, not a React app. No npm install, no build step, no framework overhead. Open it in a browser and it works. This is the right tool shape for a financial calculator you want to pull up quickly during a meeting, share with a co-founder by email, or host on a simple web server.


What you get

After the LLM generates the file:

storefront-sim.html

That is it. One file.

Fire it up

Ask your agent to open the calculator in your browser:

Open storefront-sim.html in my browser so I can test the sliders and platform revenue scenarios.

If you prefer to open it yourself from a terminal or file manager:

Terminal window
open storefront-sim.html # macOS (Linux: xdg-open storefront-sim.html; WSL: explorer.exe . then double-click storefront-sim.html)
# or just drag the file into your browser

You should see a dark-themed calculator with sliders and input fields at the top, platform cards in the middle, and a summary dashboard at the bottom. Start moving sliders and watch the numbers update instantly.

If something is off

ProblemFollow-up prompt
Sliders don’t update calculationsMoving the sliders does not update the numbers below. Make every slider and number box recalculate all platform cards and summary totals immediately as I drag it.
Platform mix doesn’t enforce 100%When I move the Steam share slider to 80%, Epic and Console stay where they were. Either rebalance the other platforms automatically to total 100%, or show a red warning banner when the mix is not 100%.
Steam tiered cut is not appliedSteam revenue uses a flat 30% cut at every revenue level. Apply the marginal tiers: 30% on the first $10M, 25% on the next $40M, and 20% above $50M, and show the blended effective cut.
Regional pricing not affecting totalsChanging the EU and Asia regional price sliders does not change total revenue. Use the regional prices and volume shares to compute a weighted average unit price, and use that price across all four sale phases.

How it works (the 2-minute version)

  1. Every input binds to a single calculate() function. When you move any slider or change any number, the entire model recalculates from scratch. This is fast enough to feel instant because the math is trivial — just multiplication and addition. No API calls, no database queries, no waiting.

  2. Platform cuts are applied per-platform, then aggregated. Steam takes 30% (with tiered reductions at scale), Epic takes 0% on the first $1M per product per year and 12% after that, consoles take 30% (a planning assumption). The “effective platform cut” in the summary is the weighted average based on your platform mix. As an illustration, at 65% Steam / 10% Epic / 25% console, the blended cut is roughly 27% if Epic revenue stays inside its first $1M and up to about 28% once it is past it; the figure depends on the Epic tier.

  3. Discount phases model the real sales curve of an indie/mid-budget game. Games do not sell at one price forever. They sell a burst at launch (often with a small launch discount), hold full price for a few months, then cycle through seasonal sales at increasing discounts. Modeling these phases separately gives a much more realistic revenue projection than “400K units times $30.”

  4. Regional pricing matters more than most indie devs realize. If 25% of your sales come from Asia at 50% of your base price, your effective average price is not $30 — it is more like $26.25. The calculator makes this visible so you do not over-project.

  5. The comparison table at the bottom gives you scenarios without touching sliders. Conservative, base case, optimistic, and an illustrative comparison scenario. These are illustrative scenarios, not reported sales results.

🔍Steam's tiered revenue share explainedclick to expand

Steam’s standard cut is 30%, and Valve’s 2018 Steam Distribution Agreement update lowered it at revenue thresholds (confirm the current terms in your Steamworks agreement):

  • First $10M in revenue: Steam takes 30%, you keep 70%
  • $10M to $50M: Steam takes 25%, you keep 75%
  • Above $50M: Steam takes 20%, you keep 80%

For a BloodRayne remake projecting $12M-$36M in gross revenue (at the mid-budget range), most of your Steam revenue falls in the 30% tier with some spilling into the 25% tier. This means your effective Steam cut is very close to 30% — the tiered discounts mostly benefit large AAA titles.

However, if you hit the optimistic case and cross $10M on Steam alone, the marginal rate improvement adds up. On $15M Steam revenue, the tiered system saves you $250K compared to a flat 30%. Not life-changing, but not nothing either.

Epic’s 12% (0% on the first $1M per product per year) is genuinely cheaper per unit. The tradeoff is smaller audience reach. Your platform mix decision depends on whether Epic’s lower cut compensates for lower volume — and that depends on your genre and audience. Action games with a retro following tend to skew heavily Steam.


Customize it

Add a time-series revenue projection

See when the money arrives across months 1-24 using an illustrative distribution (Month 1 launch spike 35%, months 2-3 15%, months 4-6 first sale 20%, months 7-12 20%, months 13-24 10%):

Add a visual bar chart below the summary dashboard plotting projected monthly revenue for months 1-24 with a cumulative revenue line and a break-even marker.

Add Epic First Run modeling

Model the tradeoff of Epic’s First Run program (100% developer share for the first 6 months, then 0% on the first $1M per product per year and 12% after; verify current eligibility and terms with Epic before using the numbers):

Add an Epic First Run toggle that models 0% Epic fee for the first 6 months and compares total net revenue with and without First Run.

Add a Kickstarter backer pricing model

Model how tiered backer rewards ($20 digital at 60%, $35 deluxe at 25%, $60 physical at 10%, $100+ collector’s at 5%) offset your development budget after Kickstarter’s 5% fee and roughly 3-5% payment processing (per Kickstarter’s fee schedule):

Add a Kickstarter Pricing section that takes total backers, calculates weighted gross across $20, $35, $60, and $100 tiers, subtracts 5% platform and 3-5% payment fees, and shows net budget offset.

Try it yourself

  1. Open your agent in a clean folder, switch to plan mode, describe the calculator, approve the plan, and open storefront-sim.html in your browser.
  2. Set the base price to $30 and total units to 400K. Note the final net revenue and ROI at the $8M default budget (an illustrative figure inside the market tracker’s placeholder range, not your plan; once the Studio Runway Planner gives you a total, enter that instead).
  3. Change the platform mix: slide Steam down to 50% and Epic up to 25%. Watch the effective platform cut drop because Epic’s 0% first-$1M tier and 12% rate above it pull the weighted average down. Notice whether the lower cut compensates for potential volume differences.
  4. Set the Asia regional price to 40% of base and the Asia volume to 30%. See how much the effective average price drops and what that does to total revenue. Regional pricing is a lever most indie devs do not think about carefully enough.
  5. Look at the comparison table. The “Conservative” scenario is your downside case — can you survive that? Compare the illustrative scenarios, and replace their inputs with cited comparable-title data before using them in an investor presentation.
  6. Try the monthly revenue projection customization. Seeing the launch spike vs. long tail makes it viscerally clear why first-month performance matters so much.

Key takeaways

  • Platform cuts vary significantly and your mix matters. The difference between 65% Steam (blended cut of roughly 27-28% in this lesson’s illustration) and a heavier Epic mix could mean hundreds of thousands of dollars on a mid-budget title.
  • Discount phases are reality, not optional. Modeling revenue at a flat base price overstates what you will actually collect. Most units sell during sales, not at full price.
  • Wishlists are your best leading indicator. At the 15% planning default, 200K wishlists means 30K first-week units. If your total projection is 400K, that means first week is only 7.5% of lifetime — which is conservative and healthy. If first week were 50% of lifetime, your game has no legs.
  • Regional pricing changes your effective price. Calculate its effect from your configured regional prices and sales mix. Ignoring it means your revenue projections are too optimistic. This calculator makes the impact visible.
  • One HTML file, zero dependencies, instant scenario modeling. Pull it up in any meeting, adjust the sliders, and have a real conversation about pricing strategy backed by math.

What’s next

You know what the market looks like and how storefront economics work. But making a game costs money every month, and money runs out. In the next lesson, you will build The Studio Runway Planner — a React cashflow tool that tracks monthly burn rate across salaries, contractors, tools, and marketing, models different funding scenarios, and tells you exactly how many months you have before you need revenue. The question shifts from “how much could we make” to “how long can we survive while we make it.”

intellimetrics · Arlington, VA
© 2026 intellimetrics.net
Search lessons