How to sell your first 1,000 copies of an indie game
A thousand copies is the first number in indie development that feels real. It will not pay for the year and nobody will call it a hit, but it is enough to prove that strangers — not friends, not a game jam audience, not people being nice — will hand over money for the thing you made. It is also enough data to tell you something true about what to do next.
Most people try to get there by hoping. They ship, they post about it, and they refresh the sales page. A better approach is to decide in advance where those thousand copies are supposed to come from, because a plan you can write down is a plan you can compare against reality — and when it goes wrong, you can see which part went wrong instead of concluding vaguely that nobody wanted the game.
What follows is a way to break the number into parts, the moves that tend to matter at each stage, and one structural idea that solo developers usually arrive at late: it is often easier to sell a hundred copies in ten countries than a thousand in one.
Break 1,000 into parts you can act on
Sales in a small game's first year arrive from a handful of distinguishable places. Launch week, which is mostly people who already knew about the game and were waiting. A slow trickle from store browsing, search and related-game recommendations. Spikes from coverage, streams and word of mouth. Discount events, which for many small games keep producing long after launch week is forgotten. And underneath all of them, the regions you are and are not reachable in.
Write down your own guess for each line. The numbers will be wrong — that is fine and expected. The point is the shape of the plan, not its accuracy. If nine hundred of your thousand copies depend on a single line, you do not have a plan, you have a bet.
- Before launch, the only line you can substantially move is the pre-launch interest line — so that is where effort belongs
- After launch, that line is fixed forever and everything else is still open
- Any line you cannot describe a concrete action for is not a plan line, it is a wish
Where are my first 1,000 copies coming from? Wishlists / followers at launch ______ Launch week sales ______ (my assumption: ____% of wishlists convert) First 3 months, store browsing + search ______ Coverage and streams ______ First major sale event ______ Second sale event ______ ------------------------------------------------ Total ______ Which of these lines can I still change with the time I have left? Which single line is more than half the total?
The largest lever happens before launch
Getting your store page up early is the cheapest high-value thing you can do, and it is regularly delayed for months because the game is not finished. That reasoning is backwards. The page is not a receipt for a finished game; it is an accumulator that collects interest for every week it exists, and it also makes your game findable in store search during all that time.
Wishlists and follows pay out twice. They notify a set of already-interested people the moment you launch or discount, and storefronts generally take pre-launch interest into account when deciding how much to surface a new release. The exact mechanics are not published in detail and change over time, so treat that as directional rather than a formula — but the direction is consistent enough to plan around.
The page itself has a job to do in the first few seconds. The opening lines have to say what the game is rather than how it feels to the person who made it, the tags need to match what the game actually is so that browsing players who want this kind of game find it, and the trailer has to show gameplay early. Your supported-languages list belongs in this conversation too — it is part of how people filter, not just information for after the purchase.
A demo gives people a reason to decide now instead of later, and festivals concentrate a large amount of attention onto a specific date, which is exactly what a small game lacks. Both are worth building your schedule around rather than fitting in if there is time.
Launch week
Launch week is where everything you did beforehand cashes out, and there is not much you can invent during it. What you can do is avoid losing the parts you have already earned.
Tell everyone who ever covered the demo, individually. Post in the communities you have actually been part of, rather than dropping a link into ten places you have never contributed to. Reply to every comment and message for the first several days, in whatever language you can manage — this is the week when the number of people paying attention to you is at its highest, and being visibly present is free.
Watch for a blocking bug and fix it within hours, not days. Early reviews are disproportionately durable: they sit at the top of the page and shape the score at exactly the moment your game is most visible, and a refund caused by a crash in the first hour is much harder to undo than the crash itself.
On the launch discount question, a modest launch discount is a normal and low-risk choice. A very deep one is a different decision, because it sets the reference price in people's heads and gives away the strongest discount you will ever have available before you need it. Prices can be raised later, but doing so is awkward and visible; discounts are easy at any time.
Finally, watch where traffic is coming from during that week. It is the clearest read you will ever get on which of your channels actually works, and it should quietly rewrite your plan for the next game.
Reviews and the discount cycle
Reviews are the conversion asset that keeps working while you sleep, and they compound: a page with a visible positive score converts better, which produces more players, which produces more reviews. Getting the first batch matters more than any individual review does later.
Ask, but ask without pressure. A short line in an end-of-game screen or in an update note asking players who enjoyed it to leave a review is normal and effective. Anything that reads as begging, or that offers something in exchange, damages the thing you are trying to build.
Then read them as data rather than as feedback on your worth. Which language are they written in? Which complaint repeats? Recurring complaints about not being able to read the game, or about text that reads strangely, are a market signal wearing a costume — they are telling you both that people in that language found you, and that something is blocking them.
Plan as though your game has a two-year life rather than a two-week one. Seasonal sale events keep introducing your game to people who never saw it at launch, and for many small games the accumulated result of those events eventually matters more than launch week did. That argues for discount discipline: escalate gradually over time, keep your deepest discount for a moment when the store is sending a lot of traffic anyway, and do not train your audience to expect that waiting two weeks always pays.
Do not stake all 1,000 copies on one market
Here is the arithmetic that changes how the goal feels. To sell a thousand copies in one country, you have to beat everything else competing for attention in that country — its front pages, its creators, its news cycle. To sell a hundred copies in each of ten countries, you mostly have to be visible and legible in each of them. The second is not easy, but it is a far less crowded fight, and it does not require you to win anything.
Language is the gate on that door. This is where localization — translating your text and making the game able to display and switch between languages — stops being a nice-to-have and becomes a distribution decision. And the cheap version of it is real: translating the store page alone, a few hundred words, changes whether people in that language can evaluate your game at all, long before the game itself is translated.
Two things travel together here. A page someone can read, and a price that makes sense where they live. Storefronts let you set regional prices, and a price converted mechanically from your home currency can land as absurd in another economy. Neither lever works well without the other: a game nobody can read will not sell at any price, and a legible page at an implausible price converts poorly too.
Choose languages from your own data, not from lists of large markets. The countries already appearing in your wishlist and traffic numbers without any effort from you are telling you where demand exists for your specific game. Then commit to one or two properly rather than five badly — five machine-dumped pages can perform worse than one careful page, because text that reads badly is taken as a preview of a game that reads badly.
Keep the causality honest with yourself. Adding a language does not create demand; it removes a reason to skip and widens the set of people who can even consider you. That is a modest claim, and it is also one of the few levers available to a developer with no marketing budget at all.
When you do reach a thousand, the most valuable thing you own is not the revenue — it is the composition. Where those buyers came from, which languages they reviewed in, which channel produced them. Let that decide the second thousand, and the second game.