Distribution & Publishing

The launch run as GTM engineering: store position, demo motion, wishlist mechanics, price discipline.

The standard indie launch inverts the effort: years on the build, weeks on the launch. The store page is written last, there is no demo, the price is picked by feel the night before, and wishlists are a number nobody managed. The result reads as market rejection and is usually a distribution no-show: the market was never asked in a form the algorithm could amplify.

The work is the same demand machinery the firm installs in founder-led companies, with a store page where the pipeline would be. Positioning excludes the wrong player on purpose: the page says what the game is for precisely enough to turn the wrong buyer away. The demo runs early enough to teach, on the demo-first motion the genre has proven. Wishlists are managed as pipeline against a threshold set before the go date — and held, so the launch waits for the number rather than the number excusing the launch. A festival is one lever inside that plan; it moves the median entrant far less than teams assume, so the discipline is to arrive with wishlists already banked or wait a cycle. Price sits inside the band the game’s own comparables hold, argued from the set rather than from nerve. Community runs as a channel with a cadence rather than a comment section with a mood.

This is where the developing practice says plainly that it leans on the firm’s established machinery rather than on shipped-title credits. The imports are specific: demand instrumentation, price-band comparables, and a weekly cadence that treats the launch as pipeline. What the developer gets is the decision most studios never get to make — a go date that is a consequence of the numbers, chosen with the evidence in hand instead of a wish about it.