01 / Engagements

Three ways in.

No 01 · DiagnosticStart here
$2,500
One week · fixed

One week of exploratory testing on the part of your product that worries you most. Scoped in a call on day one, written up by day five.

You receive
→A risk map of the areas most likely to produce customer-visible failures
→Write-ups of every bug found, with severity and suggested priority
→A 60-minute readout call with your team
→A recommendation on what to test next, if anything
Book the diagnostic→
No 02 · Investigation
$9,500
Three weeks · fixed

Three weeks on a release, migration, or launch that has to go well. Structured exploratory sessions across your critical flows, plus a review of your existing automated tests.

You receive
→Everything in the diagnostic, at release depth
→Reproducible bug reports your engineers can act on same-day
→A review of your existing test suite and what it actually covers
→A handoff plan your team can run without me
Discuss an investigation
No 03 · Retainer
$5,000/mo
Monthly · after a first engagement

Ongoing testing for teams that ship every month. I stay familiar with the product, test each release before it goes out, and review new automated tests as they're added.

You receive
→A monthly investigation cycle on whatever ships next
→A release-readiness read before every deploy
→A direct line to me
→Month to month; every report is yours to keep
Ask about capacity
How the diagnostic runs
Day 1Scope call. We agree what worries you, what I'll test, and what the report should answer.
Days 2–4Testing sessions. Bugs get written up and sent over as I find them, not saved for the report.
Day 5You get the written report, and we spend an hour walking through it.
The deliverable — every engagement ends with one
Risk report · excerptp. 3 of 11
Finding 04 — Silent failure in receipt retrieval
Risk: complianceWho cares: your counsel
Client content redacted. Each finding names the risk, who it affects, and what it costs to ignore.
Why fixed price?

So you know the cost before you commit. The calendar bounds the scope; how deep I get within it is my job, not a change order.

What if you find nothing?

Then the report says so: where I looked, what I tried, and why I'd be comfortable shipping. That's still an answer — the one you were hoping for.

Do you write automated tests?

I review them and tell you which ones give false confidence. Writing new ones is your team's job; the handoff plan tells them where to start.

Next step
Not sure which fits? That's what the call is for.
30 minutes, no slides. Worst case, you leave with a second opinion on your testing.
Book a 30-minute call→