01check 1 of 12
Auth & access
“If a user's role changes today, does every screen and API respect it by tomorrow?”
if it failsA former employee or the wrong customer sees data they shouldn’t.how we testWe change roles and try every screen and API route as each one.
02check 2 of 12
Data integrity
“Can a partial failure leave two records that should agree, disagreeing?”
if it failsStock, orders and money stop agreeing, and nobody knows which number is true.how we testWe force failures mid-transaction and check what’s left behind.
03check 3 of 12
Money paths
“If a payment webhook fires twice, do you charge the customer twice?”
if it failsCustomers get charged twice, or not at all, and support finds out first.how we testWe replay payment notifications and cut the connection mid-payment.
04check 4 of 12
Deploy & rollback
“If tonight's deploy breaks production, how many minutes to the last good version?”
if it failsA bad release takes the business offline while someone works out how to undo it.how we testWe time a real rollback, start to finish.
05check 5 of 12
Observability
“If something breaks at 3am, do you find out from a dashboard or from a customer?”
if it failsYou hear about outages from customers, hours later.how we testWe break something on purpose and time how long until someone knows.
06check 6 of 12
Secrets
“Are your API keys and credentials somewhere a departing contractor could still read?”
if it failsA departed contractor, or a leaked file, still opens your systems.how we testWe search the code, history and shared docs for keys and passwords.
07check 7 of 12
Content ownership
“Can your team change a headline or a price without a developer?”
if it failsEvery price or headline change waits for a developer.how we testWe ask a non-technical person to change one, and watch.
08check 8 of 12
Discoverability
“If someone searches your exact business name, do you outrank your own directory listing?”
if it failsYou pay for traffic Google and AI assistants could send you free.how we testWe measure speed, search results and what assistants say about you.
09check 9 of 12
Change cost
“Does a small feature request take days, or a Slack thread and a week?”
if it failsSmall requests take weeks, so the roadmap stalls.how we testWe ship a small change ourselves and time it.
10check 10 of 12
Scale ceiling
“What breaks first if traffic tripled overnight?”
if it failsYour best day is the day the site falls over.how we testWe load-test at three times today’s peak.
11check 11 of 12
Dependency risk
“If your single hosting or API vendor doubled its price tomorrow, could you leave?”
if it failsOne vendor’s price rise or outage becomes your crisis.how we testWe list every critical vendor and how you’d leave each one.
12check 12 of 12
Continuity
“If the person who built this vanished today, what happens?”
if it failsIf the builder disappears, so does your ability to change anything.how we testWe check who owns the code, hosting and domain, and whether a stranger could take over.