Pipeline Debugger
Ten broken GTM systems. Find what broke, then fix it.
Each level is a real failure shape: a symptom the team can see and a diagram of the system behind it. Pick the root cause, then the fix. Every fix is a named pattern from the GTM systems pattern library.
Every scenario in this game is also published as a field guide at /resources/pipeline-debugging-scenarios/
Level 1 of 10 · Slow lead response
The unanswered demo request
Demo requests reach the CRM within seconds of the form submit, but the first human reply often lands the next business day. Reps say they never saw the lead, and every tool in the chain shows green.
Scenario inputs
- Inbound leads per month
- 400
- Average contract value (ACV)
- $25,000
- Opportunity win rate
- 20%
- Website visitors per month
- 20,000
- Outbound SDR seats
- 2
- MQLs never worked per month
- 20
Fictional inputs shared with the free diagnostic at /engineer/, not measurements.
How to play
- Read the symptom and the diagram.
- Pick the root cause from four options.
- Pick the fix from four options.
- Each level is worth 10 points, minus 3 per wrong pick and 2 per hint, never below zero. The timer is shown but not scored.
How the scoring and ranks work
The ten-level run is worth 100 points. Each level starts at 10, loses 3 for every wrong pick and 2 for every hint, and never drops below zero. The weekly scenario is one level from the same set, picked by the ISO week, and is ranked on the same percentage.
- Apprentice: 0 to 39
- Operator: 40 to 69
- Systems Engineer: 70 to 89
- Architect: 90 and up
Ranks are self-reported. Your score is never sent to or stored on artemisgtm.ai; progress stays in this browser, and a shared result lives only in the link you choose to send.
The scenario inputs are the fictional worked-model inputs of the free AI GTM Engineer diagnostic, not measurements of any company. To score your own system instead, use the teardown rubric self-check.