ESSENTIAL GUIDANCE · BUYER GUIDE · 5 min read
Part of Validate insights →Penetration testing cost in the UK: scope and quotes
Understand penetration-testing prices, scope units, delivery models, quote details, fixes and retesting before choosing a UK provider.
Technical review lead: James Hinton · Offensive security lead
Understand penetration-testing prices, scope units, delivery models, quote details, fixes and retesting before choosing a UK provider.
Need an acronym translated?Open the cyber glossary →Start with scope and inclusions
There is no single price for every app or network. A starting price only helps when it explains the method, scope unit and inclusions behind it. Use the live Pentesys pricing page as a guide to penetration testing pricing, then ask for a quote for the real systems and test goal. Compare what will be tested and what proof you will get, not only the lowest headline number.
Know what the quoted unit covers
A scope unit, consultant day, fixed job and ongoing programme are different ways to price the work. A published unit rate is not always the total penetration testing cost for a whole company or app. Ask how the provider turns your list of assets, user roles, workflows and access assumptions into effort. Write down exclusions and assumptions with the price so any change can be handled openly.
Compare AI-enabled, Combined and human-led delivery
Pentesys offers CREST-accredited AI-enabled testing with expert oversight and evidence checks, Combined delivery with additional, explicitly scoped human-led investigation, and CREST-accredited human-led testing. The best fit depends on the system and the test goal. Complex business rules, identity boundaries and higher-risk questions may need specialist human review. Compare the depth you buy, not just the label.
Applications, APIs and mobile apps have different drivers
For an application, list user roles, key workflows, tenant boundaries, admin tasks and integrations. Say if backend APIs, mobile apps and separate environments are in scope. One URL can hide several trust boundaries and business rules. Share sample access and documents so the quote is based on the real app, not a rough page count.
Infrastructure and cloud effort depend on boundaries
For infrastructure, separate internet-facing work from testing that starts inside the network. Note the key segments, sites, identities, service types and access limits.
For cloud work, list the accounts, subscriptions or projects, the identity model and the services the customer controls.
Set supplier boundaries clearly. These details affect useful coverage and effort more than a simple count of IP addresses.
Check the full quote
- Agreed scope, starting access, test method and exclusions.
- Preparation, accounts, documents and technical availability.
- Execution windows, escalation, reporting and debrief.
- Evidence checks and practical fix advice.
- Retest scope, time window and any limits or extra charges.
- Travel, out-of-hours work, extra environments and scope changes.
- VAT and the basis for any repeat commitment.
Ask the provider to identify customer duties as clearly as its own outputs. A lower price may describe a narrower purchase rather than better value.
Compare two quotes on the same basis
Write the same scope and test goal for each quote. Compare roles, boundaries, methods, effort assumptions, outputs and follow-up. If one quote excludes authenticated testing using agreed user accounts, an important API, or retesting, record that difference before comparing totals. Do not treat an unclear day count or a long list of automated findings as a sign of better assurance.
Budget for action after delivery
Your team needs time to review findings, make fixes and provide evidence for retesting. Technology changes and internal remediation work may sit outside the testing quote. A useful report helps turn findings into owned actions, but commissioning a test does not itself reduce risk. Agree the handover and close-out process while the work is being scoped.
Get a scoped quotation
Start with a short description of the service, key systems, deadlines and the decision the test must support. Use the pricing page as a guide, then ask for a scope-specific quote. If you are unsure whether AI-enabled, Combined or human-led testing fits, compare the delivery routes before you buy. Keep the final scope and inclusions with the quote so the expected proof is clear.
Q&A
Common questions
Is the starting price a quote for my whole application?
Only if the stated starting scope really matches your app and agreed inclusions. Roles, workflows, interfaces, environments and method can change the required effort.
Is retesting always included?
Check the written quote for the included retest scope, time window and any conditions. Do not assume unlimited retesting or a full retest of the whole estate.
Should I choose the cheapest quote?
Compare the same test goal, scope, method and outputs first. Differences in access, depth or follow-up can make two headline prices describe different purchases.
Where can I find current Pentesys prices?
Use the live pricing page and ask for a formal scoped quote. This guide explains how to compare the purchase rather than keeping a separate price list.
How much does a penetration test cost?
Cost depends on scope, testing method, access, system complexity and agreed follow-up. Check our current indicative pricing, then request a quotation for your specific requirements.





