I run fixed-price testing investigations for software teams of ten to sixty people. At the end you get a written report: what I found, how bad it is, and what I'd do about it. I work alone, by choice.Fixed-price testing investigations for teams of ten to sixty. You get a written report: what I found, how bad it is, what I'd do about it.
I investigate software to find problems that matter, designing experiments under uncertainty and applying heuristics to evaluate behavior.
Rapid Software Testing treats testing as skilled human investigation, not a scripted process. Every session has a charter, oracles, and heuristics. Every bug report tells a story. I'd rather delete a weak test than pretend it covers something.
I audit my team's checks the same way I'd audit my own: ruthlessly, quietly, on paper. Recent work includes a credit-union core transformation covering migrated APIs, replacement services, and post-migration member data.
Every bug report tells a story. The story I tell is the one stakeholders can act on, not the one the test tool happens to print.
Every engagement ends with a written report. Rather than describe it, I published one. Two hours of exploratory testing against Cal.com, written up exactly the way a client receives it.
Nobody hired me to write it. I picked a product I use, spent two hours on it, and published what I found. A sample is only worth reading if the findings are real ones.
Read the full report→Send me the shape of what you're building: the stakes, the timeframe, where it hurts. I'll come back with how I'd investigate it.