Lesson 15: Revenue Optimization & Analytics

After launch, you have something precious: real data. Sales, wishlists, playtime, and reviews tell you what is working and what is not. This lesson shows you how to use that data to optimize revenue and plan your next steps without drowning in spreadsheets.

What You'll Learn

By the end of this lesson you will be able to:

Interpret store dashboards: sales, wishlists, and conversion so you know where you stand
Choose a small set of metrics that matter for your goals (revenue, reach, or retention)
Decide when and how to use discounts and bundles without devaluing your game
Use data to plan pricing, DLC, or your next project instead of guessing
Avoid common traps: over-optimizing, ignoring qualitative feedback, or chasing every number

Why This Matters

Indie revenue is lumpy: a launch spike, then a long tail. If you do not understand the numbers, you cannot tell whether a dip is normal or a problem, or whether a discount actually helped. Good analytics help you control money instead of letting anxiety or hype drive decisions.

Step 1: Know Your Core Metrics

Sales and revenue

Units sold – Raw copies. Track by week or month so you see trends, not just totals.
Revenue – After platform cut (e.g. Steam ~30%, itch.io configurable). This is what you actually earn.
Revenue by region – Some regions have different price points and buying patterns. Use this to decide where to focus marketing or localization.

Wishlists and conversion

Wishlist count – On Steam, wishlists often predict launch and sale performance. Growth rate matters as much as the total.
Wishlist-to-sale conversion – At launch and during sales: what % of wishlisters buy? Industry ballpark for indies is often in the single digits to low teens at launch; it varies by genre and price.
Where wishlists come from – If your store dashboard or tools show traffic sources, use them to see which marketing (festivals, streams, social) actually drives wishlists.

Pro Tip: Pick one primary metric for "success" (e.g. "first 90 days revenue" or "wishlist conversion at launch") and track 2–3 supporting metrics. More than that leads to noise and second-guessing.

Common mistake: Checking dashboards every day and reacting to every small change. Review weekly or biweekly so you see trends, not daily noise.

Step 2: Use Store Dashboards Effectively

Steam

Sales and key activations – Units and revenue over time; filter by region if needed.
Wishlists – Total and trend; often broken down by source (e.g. discovery queue, direct link).
Traffic and conversion – Page views vs. wishlists vs. purchases. Tells you if your store page is converting or if you need better screenshots, trailer, or copy.
Reviews – Count and recent trend. Score affects visibility; read qualitative feedback for product decisions.

itch.io

Revenue and sales – Dashboard shows earnings and units. Use time filters to compare periods.
Views and downloads – If you have a demo or free version, views vs. purchases show conversion.
Referrers – Where visitors come from. Helps you double down on channels that send buyers.

Pro Tip: Export or screenshot key numbers once a month (e.g. total revenue, wishlists, units sold). You will thank yourself when planning the next game or talking to publishers or press.

Common mistake: Only looking at revenue and ignoring wishlists or conversion. Low conversion can mean price, positioning, or store page quality—fix that before spending more on marketing.

Step 3: When and How to Use Discounts

Why discount

Visibility – Steam and other stores often feature discounted games; a sale can boost visibility and wishlists even if margin per unit drops.
Long tail – After the launch spike, a planned discount (e.g. 3–6 months later) can bring a second wave of sales.
Bundles – Humble, Fanatical, etc. can reach new audiences. Negotiate carefully so you are comfortable with the effective price and volume.

When to avoid

Right after launch – Discounting too soon can train players to wait and can annoy early buyers. Many indies wait at least 3–6 months.
Permanent low price – If you start very low "to be fair," you have little room for meaningful sales later. Price for value, then use discounts as events.

Best practices

Plan in advance – Align with Steam seasonal sales (Summer, Winter, etc.) or your own anniversary. One or two big sale windows per year are easier to manage than constant small discounts.
Communicate – Announce the sale to your community and in your newsletter. People who wishlisted might be waiting for exactly this.
Track the result – Compare revenue and units in the sale week vs. a normal week. Did the discount pay off in volume, or did you just cut margin? Use that for the next decision.

Pro Tip: Consider a "launch discount" (e.g. 10% for first week) to reward early supporters, but keep it short and clear so it does not feel like the "real" price.

Common mistake: Discounting because sales are slow, without checking whether the problem is price or visibility. Sometimes a better trailer, more screenshots, or a festival feature helps more than a price cut.

Step 4: From Data to Decisions

Pricing

Compare your price to similar games in genre, scope, and quality. Too high and you lose wishlists; too low and you leave money on the table and signal "cheap."
Test carefully: small permanent price changes or short regional experiments can inform bigger decisions. Do not change price every week.

DLC or sequel

Engagement – If your platform gives playtime or completion data, use it. High completion or many hours can justify DLC or a sequel; low engagement might mean improve the core experience first.
Reviews and feedback – Repeated requests for a feature or more content are a signal. So is silence: if nobody asks for more, DLC might not be the priority.

Next project

Revenue and time – How much did you make per month of development? That sets realistic expectations for the next game.
What sold the game – Which trailer, stream, or festival drove the most wishlists or sales? Double down on that type of effort next time.

Pro Tip: Write a short "post-mortem" after 90 days: top 3 things that drove revenue, top 3 things that did not, and one change for the next project. Keep it to one page so you actually use it.

Common mistake: Letting one bad month or one viral tweet drive big decisions. Look at 4–12 weeks of data before changing strategy.

Mini Challenge

By the end of this lesson:

List your 3 core metrics – e.g. "Revenue (monthly)," "Wishlist conversion at next sale," "Review score." Decide how often you will check them (e.g. weekly or biweekly).
Export or note current numbers – Sales, revenue, wishlists (if applicable), and review count/score. Save them somewhere you can compare in 30 days.
Plan one discount – Pick a window (e.g. next Steam sale or your game’s 6-month anniversary) and a discount level (e.g. 20–30%). After the sale, compare revenue and units to a normal period and note whether it was worth it.

Share your 3 metrics with a dev friend and ask: "Do these match what you track?" You might pick up one more useful metric.

Troubleshooting

Problem: Our wishlist conversion at launch was very low.
Solution: Check store page quality (trailer, screenshots, description) and price vs. similar games. Low conversion often means mismatch between expectation and offer. Consider a small discount for the next sale and A/B testing key assets if the platform allows.

Problem: We do not know which marketing drove sales.
Solution: Use referral or source data from the store when available. For future campaigns, use distinct links or codes (e.g. itch.io sale codes, or different UTM parameters) so you can attribute traffic.

Problem: Revenue is fine but we are burning out.
Solution: Revenue optimization is not only about making more. It is also about sustainable pace. If the numbers are acceptable, consider reducing scope (fewer updates, less frequent discounts) so you can sustain the project or move to the next one without burnout.

Pro Tips

Tip 1: One Page Dashboard
Keep a single document or sheet with: current revenue, units, wishlists, review score, and the date. Update it monthly. Over time you will see trends without opening every platform daily.

Tip 2: Qualitative + Quantitative
Numbers tell you what happened; reviews and community tell you why. Read a sample of reviews and Discord feedback when you review metrics so you do not optimize in a vacuum.

Tip 3: Compare Yourself to Yourself
Do not fixate on other games’ numbers. Compare your last month to your previous months, and your launch to your first sale. That is what you can actually influence.

Recap

Core metrics – Choose 2–3 (e.g. revenue, wishlist conversion, review score) and review them on a set schedule.
Store dashboards – Use Steam and itch.io data for sales, wishlists, traffic, and conversion; export or note key numbers periodically.
Discounts – Use them for visibility and long-tail revenue; plan timing (e.g. seasonal sales), avoid discounting too soon after launch, and measure whether each sale paid off.
Decisions – Use data for pricing, DLC, and next project; balance with qualitative feedback and sustainable pace.

Next Lesson

In Lesson 16: Studio Expansion & Future Projects, you will use everything you have learned to plan your next steps: staying solo, growing a tiny team, or starting your next game with a clear picture of what worked and what to do differently.