Culprit

6 questions · ~3 min

Flaky CI cost & tooling survey

We're building a tool that finds the exact commit that introduced a flaky test — no manual git bisect needed. Before we set pricing, we want to understand real costs and willingness to pay.

1. What best describes your role? *
2. How many engineers regularly commit to your main CI pipeline each week? *
3. How many hours per week does your team collectively lose to flaky CI tests? *

Include reruns, investigations, and developer context-switching.

4. Which tools does your team currently use to detect or manage flaky tests? (Select all that apply)
5. Imagine a tool that automatically posts the introducing commit of every new flaky test as a PR comment — no manual git bisect needed.

Reference anchors: $10 · $18 · $30 · $50 per committer/month. Enter the per-committer/month price where...

$/committer/mo
$/committer/mo
$/committer/mo
$/committer/mo
6. If this tool offered a 14-day free trial (no credit card required), how likely would you be to sign up? *