Cheap Penetration Testing, Without the Catch
A low price is fine when you know what it buys. Here is what drives the number, how to compare two quotes properly, and how to get a test that passes review on a budget that is real.
Tell us the budget
This is a manual penetration test, not a vulnerability scan. Say what you need tested and what you can spend. We will tell you what that buys, and if it does not buy something worth having we will say that too, along with what we would do instead. The scoping call is free and there is no sales team to get past.
Solusec is CREST accredited as a company, and every test is carried out by a qualified, CREST registered tester. Certifications held include CREST CRT, OSCP, OSWE, CISSP and CISM, alongside registration with the UK Cyber Security Council.
A low price is fine when you know what it buys. Here is what drives the number, how to compare two quotes properly, and how to get a test that passes review on a budget that is real.
If you have been quoted two very different numbers for what looks like the same job, the gap is almost never arbitrary. It is usually one of six things, and three of them are perfectly legitimate reasons to take the cheaper quote. Once you can name which one you are looking at, the decision takes minutes.
Our own rates sit below the large consultancies, we quote a fixed price on a defined scope, and retesting is included rather than sold to you later. If a conversation shows you need less than you asked for, or something other than a test, we will say so. Scoping calls are free.
Where a low price actually comes from
There are only so many ways to make a penetration test cheaper, and they are not equally acceptable. Three are legitimate, two depend entirely on the detail, and one is not a penetration test at all.
1. Lower overheads: legitimate
A small practice has no offices to fund, no account managers and no sales team. That is a genuine cost difference and it reaches you as a lower day rate without touching the work itself. Our own rates sit below the large consultancies for exactly this reason, and we would rather say so than imply the difference is some efficiency nobody else has thought of.
The test for whether an overhead saving is real: ask who you will deal with during the engagement. If the answer is the person doing the testing, the saving is structural. If there is a layer of account management on top of a lower day rate, the overhead has not gone anywhere.
2. Fewer days: legitimate, if you know
A three-day test costs less than a six-day test because it covers less. That is fine when the scope genuinely warrants three days, and a problem when a provider quotes three to win the work and then cannot cover what you needed.
This is the single most common reason two quotes differ, and the easiest to check. Always compare day counts rather than totals. A provider who will not state the days, or who gives you a total with no breakdown, has told you something.
3. Automation instead of testing: usually not acceptable
Running a vulnerability scanner and formatting the output takes a fraction of the time. It is also not a penetration test. It will not find broken access control, it will not find business logic flaws, and it will not find the chain of three individually minor issues that together hand somebody your database.
Most compliance requirements that specify penetration testing will not accept it, and the people who evaluate these reports have seen enough of them to recognise one quickly.
4. Junior staff: depends entirely on supervision
Large consultancies often sell senior expertise and staff the work with juniors, because that is how the economics work at scale. With genuine review that can be fine, and it is how testers are trained. Without it, you are paying for somebody to learn on your systems and nobody is checking what they missed.
The question to ask is not whether a junior will be involved. It is who reviews the findings, what they hold, and whether their name is on the report.
5. Offshore delivery: depends on what you need from it
A lower cost base elsewhere is a real difference, not a trick. It becomes a problem when the engagement needs a conversation at short notice during the testing window, when the report has to satisfy a UK buyer who will check the provider's accreditation against a UK register, or when your contract or regulator restricts where your data may be processed. Any of those, and the saving evaporates.
6. A loss leader: check what it is leading to
Some low quotes are priced to win a relationship rather than to cover the work: a cheap first test followed by a managed service, a monitoring subscription or a licence you are expected to take afterwards. That can genuinely suit you. It is worth knowing it is the model before you are halfway into it, because it changes what the provider is optimising for when they scope your test.
What a day of testing actually buys
Day rates sound abstract until you know what a day contains, and the reason day count matters more than rate becomes obvious once you do.
On a web application, roughly the first half day goes on mapping: walking the application as each type of user, finding every function, and building a picture of what the thing is actually for. That sounds like preamble and it is the opposite. A tester who has not understood what your application does cannot tell the difference between a quirk and a flaw.
From there the time divides between the mechanical checks, which tooling helps with, and the ones that need a person: whether one customer's account can reach another's data, whether a sequence of steps can be performed out of order, whether a price or a quantity can be changed in flight, whether an administrative function is protected by anything more than the absence of a link to it. These are where the serious findings live, and none of them is discoverable by a scanner, because each depends on knowing what the application is supposed to prevent.
Reporting is typically a further day on a small engagement and is not optional. A finding nobody can reproduce is not a finding, it is an assertion.
Cut days from that and something specific goes. Usually it is the second half, because the mechanical checks are the ones that are hard to leave out visibly.
When cheap is genuinely the right answer
We would rather say this plainly than pretend every organisation needs the full engagement.
- Small, contained scope. A brochure website with a contact form does not need six days. A short test is the correct answer here, not a compromise, and quoting six would be the dishonest move.
- A lighter check after a specific change. You have had a thorough test, one component has changed, and you want that component looked at. Scoping to the change is proportionate.
- Your real need is certification. If a customer's requirement is satisfied by Cyber Essentials, a penetration test is an expensive way to answer a question nobody asked. This is the most common mismatch we see, and the cheapest problem to fix, because it means buying something far less expensive rather than something cheaper.
- You have foundational gaps you already know about. No multi-factor authentication, unsupported software in production, backups nobody has restored. Spend the money closing those. A test will confirm what you already suspect and you will have paid to be told.
- Nobody has ever looked. If the honest position is that you have no idea what is exposed, a cheap first look has value simply as a baseline, provided you understand that is what you bought.
When cheap costs more
The failure mode is nearly always the same, and it has nothing to do with security. It is that the report has to satisfy somebody else.
A tender evaluator. A client's security reviewer. An auditor. An underwriter at renewal. If the report comes from an unaccredited provider, covers a scope that does not match what was asked for, or is visibly scanner output with a cover page, it gets rejected. You then commission a second test under time pressure, and you pay twice plus whatever the delay costs you in the deal that was waiting on it.
That is the arithmetic that matters. A £1,200 test that fails the requirement is more expensive than a £3,000 test that passes it, and the gap is wider than the difference between the two quotes, because the second test is bought in a hurry with no leverage.
Worth knowing which requirement you are actually under before you buy. Testing for a tender, for a client contract and for cyber insurance each ask for slightly different things, and the differences are precisely where a cheap test tends to fall short.
The costs that are not in the quote
A low headline number sometimes reflects what has been moved out of it. These are the ones worth asking about explicitly, because each is a normal line item somewhere and an unpleasant surprise if you assumed it was included.
- Retesting. Frequently excluded from a low quote and charged later at full rate, which is exactly when you have least room to argue. A report full of unfixed findings rarely satisfies whoever asked for it, so the retest is not optional, only unbudgeted.
- The report itself. Occasionally quoted as testing days only, with reporting added afterwards or offered as a tiered upgrade.
- Out-of-hours work. If your systems cannot be touched during business hours and that was not established at scoping, it arrives as a surcharge.
- Travel. Legitimate when genuinely needed, and worth having as a visible line rather than discovering it later.
- Scope changes. Fine in principle. The question is whether you are told before the work is done or billed for it afterwards.
We include retesting rather than selling it later, charge no travel across the West Midlands and Shropshire, and hold the quoted price for the scope agreed. If the scope changes materially we say so before doing the work, not on the invoice.
How to spot scanner output in sixty seconds
Ask for a redacted sample report before you commit. Any competent provider has one and will send it. The tells are consistent:
- No reproduction steps. A real finding tells your developer exactly how to see it for themselves. Scanner output describes a class of issue in general terms.
- Remediation text that could apply to anybody. Generic advice lifted from a vulnerability database, rather than what to change in your system.
- Severity with no business context. A CVSS score and nothing about what the issue would actually let somebody do to you. An outdated TLS version ranked above a broken access control is the classic giveaway.
- Nothing chained. Every finding stands alone. No sign of anyone having combined two low-severity issues into one that matters, which is most of what you are paying a person for.
- Findings that are not findings. Pages of informational items padding the length. Volume is not depth, and a long report is sometimes a short test.
- No mention of what was excluded. An honest report names the limits of its own coverage.
How to tell what you are being offered
Four questions that expose the difference quickly:
- How many days of manual testing, excluding report writing? If the answer is vague, that is the answer.
- Who is the named tester and what do they hold? "One of our qualified team" tells you something. Accreditation is checkable: ours is on the CREST marketplace at company level, and individually, which are two different things and worth confirming separately.
- Can I see a redacted sample report? Refusal is informative.
- Is retesting included? See above.
There is a fifth test, and it runs the other way. Listen to what the provider asks you. A quote produced without anyone asking how many user roles your application has, whether there is a staging environment, or whether credentials will be available on day one is not a quote. It is a guess with a number on it, and guesses are revised upwards once the work starts.
Our pricing page explains what actually drives the day count, and how to compare providers covers this in more detail.
If the budget genuinely is not there
Sometimes the honest answer is that the money does not exist this quarter. That is a real position and there are better responses to it than buying a bad test.
Narrow the scope rather than the days. Test one application properly instead of four badly. One system examined thoroughly is worth more than five skimmed, and the report says clearly what was covered, which is defensible to a customer in a way that thin coverage of everything is not.
Scope to the authenticated user. Where budget is tight, testing what a logged-in customer can reach, rather than the whole estate, concentrates the effort where the serious findings usually are.
Timebox it deliberately. An agreed number of days spent on the highest-value areas, with the limits stated in the report, is an honest product. It is not the same as a full test and should not be presented as one.
Spread it over time. The application this year, the infrastructure next. For organisations testing repeatedly, a retainer or banked days bought up front works out better than quoting each engagement separately.
Ask about reduced rates. We hold discounted day rates for schools and for small or pre-revenue organisations. It is worth asking rather than assuming the list price is the only price.
Free and subsidised options worth taking first
If money is the constraint, spend none of it until you have used what is already funded. None of this is a substitute for testing, and all of it is better than a bad test.
Cyber Essentials is currently 75 per cent subsidised. The Cyber Essentials First Step Fund, open since 3 November 2026, takes a first certificate down to between £80 and £125 plus VAT for eligible micro, small and medium-sized UK organisations that have not held it in the previous four years. It runs to the end of March 2027 or until the funding is exhausted. If what your customer actually asked for is a certificate, this is the cheapest it will ever be. See buying Cyber Essentials.
The NCSC publishes free tools. Exercise in a Box walks a team through an incident scenario without needing a consultant in the room, and costs nothing. Its Active Cyber Defence programme carries free services that notify UK organisations about threats and vulnerabilities seen against their own networks. The line-up changes, so check what is currently offered, but it is all free and it closes gaps a test would otherwise spend your money finding for you.
The regional Cyber Resilience Centres. Police-linked and not-for-profit, they offer low-cost vulnerability assessments delivered by supervised university students. For an organisation with nothing in place at all, that is a sensible first step and considerably better than nothing. It is not a penetration test and will not satisfy a requirement that asks for one, but it will tell you the obvious things cheaply.
Cheap, and free: the vulnerability scan question
A vulnerability assessment is a tool run against your systems, matching what it finds against a database of known issues. Fast, inexpensive, and genuinely useful as a baseline or as a recurring check between tests.
A penetration test is a qualified person trying to reach something they should not reach. The scan is where that person starts. What they add is the part no tool does: chaining findings, reasoning about what your system is for, and telling you which of thirty issues is the one that gets somebody into customer data.
Neither replaces the other, and the honest recommendation depends entirely on what you have been asked for. If a contract or an auditor requires an annual penetration test by an accredited third party, an automated assessment does not satisfy it, and submitting one as though it did tends to be noticed. The difference is covered in full here.
What we do about it
We quote on a call, for a defined scope, and hold the price. Retesting is included rather than sold later. You deal with the tester throughout rather than an account layer. And if a scoping conversation suggests you need less than you asked for, or something other than a penetration test entirely, we will say so.
That is not generosity. A client who buys the wrong thing does not come back, and in a market this small that matters more than one invoice.
Common questions
Are you cheap?
Cheaper than a large consultancy, because we have no offices, no account managers and no sales function to fund, and that difference reaches you rather than being absorbed. Not the cheapest quote you will receive, because the cheapest quotes in this market are usually a scan with a cover page. We will tell you honestly where we sit against another quote if you show it to us.
What is the least I can spend and get something useful?
Less than you might think, if the scope is genuinely small and you are honest about what you are buying. A contained external perimeter or a single small application is a short piece of work and a legitimate one. What does not work is a small budget stretched across a large estate. Tell us the number at the first conversation and we will tell you what it covers properly rather than what it covers thinly.
A provider quoted half what you did. Should I be worried?
Not necessarily, and the way to find out takes five minutes. Compare the day counts rather than the totals, ask both providers who the named tester is and what they hold, and ask both for a redacted sample report. If the cheaper quote has the same days and a real report behind it, take it. If it has half the days, that is not a discount, it is a smaller job.
Is retesting really charged separately by some providers?
Routinely, and it is the most common thing missing from a low quote. It matters because a report showing unfixed findings rarely satisfies whoever asked for the test, so the retest is not something you can decline. Ours is included. Ask the question explicitly rather than assuming either way.
Can I just get a vulnerability scan instead?
If nobody has ever looked, a scan tells you the obvious things cheaply and is better than nothing. If a contract, an auditor or an insurer has asked for a penetration test by an accredited provider, a scan does not satisfy it, and submitting one as though it did tends to be noticed. The distinction is set out on penetration testing versus vulnerability scanning.
How do I spot a scanner report before I buy?
Ask for a redacted sample. Look for reproduction steps a developer could follow, remediation written for your system rather than lifted from a database, severity explained in terms of what somebody could actually do to you, and at least one finding built by combining two smaller ones. If all six of those are missing, you are looking at tool output.
We genuinely cannot afford a full test. What should we do?
Narrow the scope rather than thinning the days, so that what is covered is covered properly and the report says plainly what was not. Use the free NCSC tools first, and check whether what your customer actually asked for is Cyber Essentials, which is currently 75 per cent subsidised. If it is still out of reach, say so on the call and we will tell you what we would do in your position, including if that is nothing yet.
Is there a discount for schools or small organisations?
Yes. We hold reduced day rates for schools and for small or pre-revenue organisations. We also offer banked days bought up front for organisations testing repeatedly, which works out better than quoting each engagement separately. Both are worth asking about rather than assuming list price is the only price.
Do you offer payment in instalments?
Not for penetration testing. Once a report is delivered it cannot be withdrawn, so instalments put the risk entirely on us. Where cost is the obstacle we would rather reduce the scope honestly, or point you at the subsidised and free options first, than spread a payment for work that is already done.
Why does the day rate vary so much between providers?
Mostly overhead rather than tester quality. Offices, account management and a sales function all sit in the number. That is why the figure that actually determines your bill is the day count rather than the rate, and why comparing totals without comparing days tells you very little.
Does a cheaper test still count for a tender or an insurer?
Only if it meets what they asked for. Most reject an unaccredited provider, a scope that does not match the requirement, or something visibly automated. Send us the wording before you buy anything. It takes minutes and it is the single cheapest way to avoid paying for two tests.
What if I show you a competitor quote?
Send it over. We will tell you what the day count means, whether the scope matches what you have been asked to prove, and whether it looks like a real test. If it is a good quote we will say so, and occasionally we have told people to take it.
Related
Ready to talk?
Scoping conversations are free and there is no sales team to get past. Tell us what you're dealing with and we'll tell you honestly what you need.