Structured QA for funded indies and small studios

The same testers on every build.

Big vendors rotate juniors through your project and hand back reports nobody can act on. We are a small senior team. You get the same people each pass, and every bug reproduces on the first try.

Book a 20-minute call See a sample report
SEV-1 · BLOCKER BUG-0412

Save file is destroyed when quitting during an autosave

Build 0.8.14-rc2 Steam Deck Found at 1h 04m

Steps to reproduce

  1. Start a new run and play to the first checkpoint.
  2. Open the pause menu while the autosave icon is on screen.
  3. Choose Quit to Desktop.
  4. Relaunch and load the most recent save.
ExpectedRun resumes at checkpoint 1.
ActualSave slot is empty. The run is gone.
Rate5 of 5 attempts. Not seen on Windows.
Video and save file attached Pass 2 of 3

Every bug we send back looks like this.

What lands in your tracker

Not a spreadsheet of complaints. Work your developers can pick up and close the same afternoon.

Repros that hold

Numbered steps, hit rate across attempts, hardware and build noted, video and save files attached. If it only happens one time in nine, we say so.

Severity you can plan around

Everything triaged against your own definitions, agreed before we start. You get a list you can cut from, not one you have to re-sort.

Coverage on the record

Which platforms, which builds, which paths through the game, and which corners we did not reach. You always know what has not been looked at.

How an engagement runs

Four steps, no procurement theatre. Most projects go from first call to first report inside two weeks.

STEP 01

Scope call

Twenty minutes on your build, your platforms, and what is keeping you up at night. You get a fixed quote after it.

STEP 02

Test plan

We write what will be covered and how deep, and you sign off before anyone touches the game.

STEP 03

Passes

A fixed team works the build. Blockers reach you the same day. Everything else arrives in the report.

STEP 04

Handover

Findings in your tracker in your format, plus a call to walk through what we would fix first.

Who actually plays your game

Career testers, not a rotating bench. You meet them by name before the first pass, and you get the same names on the second.

Handle
Lead · Systems

Breaks economies and progression curves. Finds the exploit your designers argued was impossible.

ProgressionSave systemsBalance
—Builds
—Titles
—Years
Handle
Combat feel

Frame-level work on hit reactions, input buffering, and the difference between hard and unfair.

Input latencyHitboxesDifficulty
—Builds
—Titles
—Years
Handle
Controller & handheld

Steam Deck, Switch, and every gamepad nobody thought to try. Catches what a keyboard never will.

Steam DeckRemappingBattery
—Builds
—Titles
—Years
Handle
UI & accessibility

Menus, remapping, colour, subtitles, and scaling. The pass that keeps a storefront review from writing itself.

Screen readersColourScaling
—Builds
—Titles
—Years
Handle
Multiplayer

Runs full lobbies on demand. Desync, host migration, and the bugs that only appear at eight players.

DesyncHost migrationMatchmaking
—Builds
—Titles
—Years
Ask who would be on your project

Tell us what is breaking.

Twenty minutes, no deck. Bring a build or just describe the problem, and you will leave the call with a fixed quote.

Book a 20-minute call

Cannot make a call work? Send us the details instead.