Process
Keep building. We find the bugs.
Structured testing, clear reports, priorities you can act on.
You send your build
Share your playable build and any specific areas you want tested.
Testing & documentation
Structured QA with clear steps to reproduce each bug, priorities, and organized reports.
Ship with confidence
Organized docs and clear priorities so you can focus on building.
What you get from a testing round
Every project ends with the same core deliverables, no matter which tier you pick.
- A bug spreadsheet with severity and priority, so you know what to fix first.
- Clear reproduction steps for each bug, written so your team can act on them without guessing.
- Screenshots, clips or recordings attached to the bugs that need them.
- An interactive kanban board you can use to track fixes as you go.
How a bug gets reported
Every entry in the spreadsheet follows the same structure: what we did, what we expected to happen, what happened instead, and how severe it is. That consistency is what makes a report something your team can act on the same day, instead of a list you have to interpret.
How long it takes
Turnaround depends on the tier and how long your game is to play through. A single bug pass can be back in 3 days; deeper QA with playtesting typically takes 5 to 10 days. See all tiers and timelines.
What we need to start
- A playable build (PC, mobile or Steam Deck) with access instructions.
- Any areas you specifically want us to focus on, if you have them.
- A short note on your target platform, so we test under the right conditions.