Indie Game Studio Tools: Press Kit Site, Playtest Portal and Creator CRM

Mythex lets a small game studio build the tools that sit around the game: a studio site with a press kit and devlog, a tester portal where every report is tied to a build version, a CRM that tracks which streamers got keys and covered you, and invoices for publisher milestones. Describe it in chat, check the live preview, and publish it with a real database.

Where a small studio drowns

The engine and task tracker handle the game itself. The flood is everything else. Playtest feedback arrives through a form, Discord, email and store reviews, much of it about a build that has already been patched. Press and creators ask for keys, and nobody remembers who covered the last demo. Testers sign up by the hundred but are not spread across hardware or play styles. Publisher milestones wait on sign-off while invoices sit in a folder. Before a demo festival or launch, the team needs to know which crashes are new, who to send keys to first, and that the press kit is complete.

• Feedback tied to the build it came from
• Bug reports triaged by severity with a visible status
• Testers chosen by platform, input device and taste
• Keys sent to creators, with coverage logged
• A press kit journalists can use without emailing
• Milestone invoices linked to deliverables

What you can build for game studios

A tester portal where reports go somewhere

Testers log in to see the build they have, its known issues and the playtest terms they accepted. Each report is stamped with that build version automatically, and testers can see whether theirs was confirmed or fixed. The team filters by version, severity and category.

Build a playtest portal for my game studio. Testers log in, accept the playtest terms, see their assigned build version and its known issues, and submit bug reports or feedback with category, severity and a screenshot. Each report is tagged with the tester's build automatically, and testers can see its status: new, confirmed, fixed.

A studio site with a press kit that saves emails

One page per game with trailer, screenshots, platforms and wishlist links. A press kit page with a fact sheet, release window, logos and key art downloads. A devlog, and a single signup that feeds both the newsletter and the playtest list.

Build a website for my indie game studio with a page for our game (trailer, screenshots, platforms, store links), a press kit with fact sheet, logos and key art downloads, a devlog section, and one signup form for newsletter and playtests.

A creator and press list that learns from each launch

One record per creator or outlet with platform, audience size, genres they cover, keys sent and links to coverage. Filter by genre before the next key wave. Publisher and platform contacts sit alongside with notes from each pitch.

Create a CRM for a game studio to track press and content creators: name, outlet or channel, platform, audience size, genres, keys sent with date and key type, and coverage links. Add publisher contacts with pitch notes. Let me filter creators by genre and whether they covered our last release.

A playtest signup that picks a useful spread

The trailer high up, the playtest dates, what testers will do, and a form asking platform, input device and similar games they play, so you choose a mix instead of the first hundred.

Make a playtest signup landing page for our game with the trailer at the top, playtest dates, what testers will be asked to do, and a form for email, platform, controller or keyboard, three similar games they play, and an optional Discord username. Save applicants with an admin view to select testers.

Open bugs by severity, per build

Chart reports by category and severity for each build, bugs opened versus closed per week, and wishlist numbers from a CSV export, so a creeping crash rate shows before the demo goes live.

Make a dashboard for my game studio showing playtest reports by severity and category per build version, bugs opened versus closed per week, and wishlist counts over time imported from a CSV.

Milestone invoices a publisher can approve

Set up milestones from the contract, raise each invoice when the build or deliverable is signed off, reference it on the invoice, and bill in the publisher's currency.

Build invoicing for a game studio with publisher contracts split into milestones, each with a deliverable and build reference, invoices raised on approval in the client's currency, and a status per milestone.

From a feedback form nobody reads to triage

Point your existing playtest form at the portal instead of a spreadsheet, and add one field: build version. For the first week, spend twenty minutes a day setting severity and status on new reports. Testers who see their reports move write better ones, and the dashboard starts telling you something real before the next milestone.

Tester data and NDAs

Playtest signups include emails, sometimes ages and hardware details. Ask for tester logins, private storage for screenshots and builds, and a record of which terms each tester accepted. If your playtest is open to younger players, check the rules where you operate on collecting their data first.

• Terms acceptance stored per tester
• Private storage for screenshots
• Only staff see all reports

Questions

By kind of app

• AI website builder for every kind of business
• AI landing page builder for every kind of business
• AI booking system builder for every kind of business
• AI client portal builder for every kind of business
• AI crm builder for every kind of business
• AI online store builder for every kind of business
• AI invoicing app builder for every kind of business
• AI dashboard builder for every kind of business
• AI inventory management app builder for every kind of business
• AI staff scheduling app builder for every kind of business
• AI directory website builder for every kind of business
• AI course platform builder for every kind of business

Build with AI · Templates · Start building free