Software testing consultancy

Senior software testing, without the full-time hire.

Two weeks of hands-on product testing every few months, done out of hours, ending with a prioritised list of what's broken and what to fix first. Four rounds a year cost a fraction of a full-time tester.

round 3 · findings

  1. $ protesting round --weeks 2
  2. sign-up works on a slow 3G connection
  3. password reset links actually work
  4. file upload copes with a 9MB PDF
  5. search rejects short terms with an error
  6. fix first: it blocks real searches
  7. filters survive the back button
  8. emails render in Outlook. Yes, Outlook.
  9. screen reader can reach every button
  10. 6 passed · 1 caught, ranked, fix first

Test rounds

Regular testing, without the full‑time hire

Rather than a permanent hire, or before one, book a round of testing every few months. Your product gets a senior tester's full attention, and you only pay for the weeks it's being tested.

Two weeks on, the rest of the quarter to fix what was found.
  1. 1

    Two weeks of hands-on testing

    Real journeys, real devices, the odd edge case nobody thought of. Everything a careful user, a careless user and an impatient user would do.

  2. 2

    Done out of hours

    Testing happens in the evenings and at weekends, so nobody on your team loses a day to it. No onboarding, no desk, no laptop to order.

  3. 3

    A prioritised list at the end

    What's broken, how to reproduce it, and what to fix first. Ranked by how much it hurts your users, so your developers know where to start.

The problem

The cost of getting QA wrong

  1. Too expensive

    Traditional consultancies charge premium agency rates for junior testers hidden behind an account manager. You're paying for their overhead - not their expertise.

  2. Too late

    Quality bolted on at the end of a sprint isn't quality - it's panic. The later a bug is found, the more people it drags in and the longer it takes to put right.

  3. Too siloed

    When QA is someone else's department, everyone else stops caring. Broken builds, repeated bugs, and a culture where quality is always someone else's problem.

Who one bug drags in
  • The developer

Caught while the code is being written

  • A hotfix release
  • A tester
  • The developer
  • A product manager
  • Support
  • A customer

Caught after release

Services

Other ways I can help

Test rounds suit most teams. Some need testing at a different moment - before a big launch, or long after it.

01

Production Health Check

Not ready to commit to rounds? Start here. A one-off check of what's live today - key journeys, forms, devices and accessibility, the things that break quietly - ending with a prioritised list of what to fix first. From £800. A smaller first step before booking rounds.
02

End-Stage Testing

Need a thorough, independent test pass before a major release? I'll test it ahead of launch and give you a clear picture of what's ready - and what isn't. Quoted per release. No retainer required.

Why ProTesting

Not your typical testing consultancy

  • Senior-led, always

    I do every piece of work myself. No junior handovers, no bait-and-switch staffing. The person you speak to is the person doing the work.

  • Cheaper than you'd expect

    No agency overhead. No inflated day rates. You pay for expertise - not a brand name, a big office, or a salesperson's commission.

  • Flexible by design

    Book a single round, or one every few months. Each round stands on its own, and whether you book the next one is up to you.

  • Quality is everyone's job

    I don't just find bugs. I help your whole team think about quality differently - so it sticks long after I've gone.

Quality is everyone's responsibility.

Dan Wilson, Founder of ProTesting

Two-minute check

Do you need professional testing?

Answer five quick questions and find out.

5 out of 5 stars

"Really helps to understand what software testing is all about."

Shaun Bokenham · Verified purchase · Amazon UK · About the book

16 years testing software

Dan Wilson

About

Led by a tester who's seen it all

I'm Dan Wilson, and I've been testing software for 16 years, leading QA strategy at scale - from early-stage startups to global enterprise teams. I've built testing frameworks from scratch, coached engineers across every discipline, and written the book on it, literally: The Book On Software Testing.

I started ProTesting because I believed the industry was overcharging and underdelivering - and that quality should be part of how teams work, not a department you call when something breaks.

Find me on LinkedIn