Frequently asked questions
Answers to what clients most often ask before booking a discovery call. Can’t find what you need? Get in touch directly.
What does a discovery call involve?
A free, no-obligation conversation about your current testing setup, the challenges you’re facing and your goals. From there I’ll recommend the right scope of engagement — whether that’s a short assessment or ongoing support.
Do you work remotely, on-site, or both?
Both. I’m based in the United Kingdom and work with teams remotely as standard, with on-site visits available where useful.
Which industries have you worked in?
Primarily Payroll, HR software, Cybersecurity, SaaS, Enterprise and Cloud Platforms — though the QA principles I apply translate well across most software domains.
What testing tools and frameworks do you use?
Mainly Playwright with TypeScript and JavaScript, alongside tools like Postman, Selenium, Provar, Jenkins, Azure DevOps and Git — selected based on what fits your stack.
How is pricing structured?
Engagements are scoped to your team size and goals rather than a fixed price list — see the Pricing page for the typical shape of each package, and a discovery call will confirm the details.
Do you offer ongoing support after the initial engagement?
Yes — many clients move from an initial assessment into an ongoing Growth or Enterprise partnership covering automation, mentoring and QA leadership.
How quickly can you start?
It depends on current availability, but discovery calls are typically available within the same week — get in touch and I’ll confirm the soonest slot.
Why does my company need a QA?
A QA helps you catch problems before your customers do. They test your software from a user’s perspective, identify bugs and risks, and help make sure new features and changes work as expected. Good QA can reduce costly defects, improve customer confidence, and give your Software team greater confidence when releasing.
Let’s talk it through
Book a free discovery call — there’s no obligation and no sales pitch.