Tell me what you want tested

What happens after you send this

1. Acknowledgement, same or next working day. A short reply confirming what you sent and asking anything that is missing — usually the number of user roles, whether a staging environment exists, and the deadline driving the work.
2. A scoping call, 30 minutes. Free, and genuinely a scoping call rather than a sales one. We walk the architecture, agree what is in and out of scope, and decide whether testing, code review or threat modelling gives you the most for the budget.
3. A written proposal within two working days. Fixed price, number of testing days, named methodology, deliverables, dates, and what happens if the scope turns out larger than described.
4. Authorisation and access. A signed authorisation letter, test accounts for each role, and any builds or read-only cloud roles. This step causes most schedule slippage, so it starts early.

If you are not sure what you need

Describe the product and the pressure you are under — a launch, an enterprise questionnaire, an audit, or a nagging feeling about the authentication code. Scoping is part of the free consultation, and if the honest answer is a smaller engagement than you asked for, the proposal will say so.

Confidentiality

An NDA is signed before any technical detail is exchanged — yours by preference, or a standard mutual one if you would rather not draft it. Enquiry details are never shared with third parties, and nothing about a client or an engagement appears publicly without written permission.