Skip to content
GullySales
← All articles

Notes for owners · Industry playbooks

What a buyer checks before hiring a VAPT firm

Before a CISO lets an outside firm test their systems, they look for a sample report, named testers and a clear method. Here is how to be ready.

The GullySales team · Updated 13 Nov 2026 · 6 min read

Editorial illustration for What a buyer checks before hiring a VAPT firm
On this page
  1. Why does the deadline matter more than the website?
  2. What do they ask for before they ask for a quote?
  3. How should you write about your work without exposing a client?
  4. How do RFP and empanelment buyers differ from everyone else?
  5. Where does the sale stall?
  6. What happens after the test?
  7. How a buyer reads a sample report
  8. Rules of engagement
  9. Handling the buyer's own team
  10. Keeping what you learn confidential
  11. Pricing and scope on a single page
  12. The questions a buyer's auditor will ask
  13. Finding the right person to speak to
  14. What to do next

A buyer hiring a VAPT firm checks four things before they reply: a sample report that shows how findings are written, who exactly will do the testing, a method explained in plain words, and similar work for similar companies. Price comes later. The buyer is about to show an outsider every weak point in their systems, so they read for signs of care before they read for rates.

Why does the deadline matter more than the website?

Almost nobody buys security testing because they feel like it. Something has a date on it. An ISO 27001 surveillance audit, a customer's security questionnaire, a cyber insurance proposal form, a regulator's direction that reaches banks and their vendors, or a story about a company down the road that paid a ransom.

That date decides when the search happens and how impatient the buyer is. A page that says "VAPT for companies preparing for an ISO 27001 audit" meets that buyer where they are. A page headed "Protect your business from cyber threats" meets nobody.

What do they ask for before they ask for a quote?

What the buyer wants to seeWhy they askWhat to have ready
Sample reportTo judge how clearly findings are written and ratedA redacted report with invented systems
Named testersWhoever tests will see the whole networkNames, roles and relevant certifications
Scope and methodTo know what will and will not be touchedA one-page scope template and a rules-of-engagement note
Similar clientsTo check you have done this for a company like theirsClient types you can describe, and references you can give with permission
Empanelment or certificatesSome buyers must use approved auditorsThe certificates you hold, stated plainly
RetestWhether fixing is checked afterwardsWhether a retest is included, and what it costs

Empanelment and eligibility rules differ by buyer and body and change, so check the current requirement with the issuing body or the buyer's own procurement team before you bid.

How should you write about your work without exposing a client?

You cannot publish findings from real engagements, and a buyer would be alarmed if you did. But you can write about method and about classes of problem. A post on what goes wrong in a typical staff VPN setup, how a rules-of-engagement note is written, or what a retest should include shows how you think. This is also where your testers become visible: put their names and short bios on the post.

The tone matters. A firm that explains its approach calmly beats one that opens with a skull on a dark screen. Your buyer is already anxious.

How do RFP and empanelment buyers differ from everyone else?

Banks, insurers and large companies run a formal process. They issue an RFP, compare technical responses against a scoring sheet and negotiate with the top two or three. Here the winning response is the one that answers each question as asked, with the evidence attached, rather than the one with the nicest cover.

Mid-sized companies with no CISO behave differently. They lean on whoever looks after their network, ask the auditor, and speak to two firms at most. They will not read a forty-page response. They want one page: what you will test, what they receive, who does it and what you need from them.

For example, a Pune firm with six testers is invited to respond to a mid-sized manufacturer's questionnaire that came from a European customer. The IT head has no security team. A short reply that names the two testers, attaches a redacted sample report and states what access is required wins a call. A long reply about the firm's "digital resilience" does not.

Where does the sale stall?

After the first call, three places. The scope is still being argued internally and nobody has told you. The proposal is with finance while the IT head waits for a budget line. Or the deadline moved, so the urgency went with it.

A follow-up that helps rather than chases works best: a scope checklist the buyer can forward to their own team, the answer to a question they raised on the call, or a note on what their auditor is likely to ask. Record each opportunity with its deadline and the person who must approve, so you know whose desk it is on. Your sales process should have stages that match this, and your content should answer the questions those stages raise.

What happens after the test?

One-off assessments are easy to buy and easy to forget. A buyer who received a clear report and a useful retest is the likeliest to ask what comes next: a standing engagement, a compliance readiness project or a managed service. Raise it with the findings, while the report is on the table.

How a buyer reads a sample report

The sample report is the page a buyer reads most closely. They look for clear findings, each with a title, a rating, a plain description, the steps to reproduce it and advice on fixing it. They look for a summary that a non-technical manager could read. They check whether the ratings follow a stated method and whether the evidence is specific without exposing any real client. A report that is vague or padded with scanner output reads as cheap.

Prepare the sample from an invented environment and mark it as such. Show how you separate what is confirmed from what is suspected. Make sure no real address, name or credential appears.

Rules of engagement

Before a test begins, both sides agree what is allowed. A buyer expects a written note covering the systems in scope, the systems out of scope, the times of testing, the methods permitted, who is told and who to call if something breaks. Have a standard version ready, and adjust it for each client. Explain it in plain words on a call.

A firm that raises these points early looks careful. A firm that waits for the buyer to ask looks as though it has not thought about what happens when a test disturbs a live system.

Handling the buyer's own team

The buyer's IT staff may feel watched when an outsider tests their work. Speak to them early, explain what you will do and what you will report, and agree how you will share findings. Present findings as things to fix together, not as faults to blame. A report that makes the IT head look careless will be argued over. One that helps the IT head ask for the budget to fix things will be used.

Keeping what you learn confidential

Findings are sensitive. Agree how reports are sent, who may read them and how long you keep the data. Describe how your testers store notes and tools, and how you remove access at the end. Say so on your site in plain language, without claims you cannot back. A buyer who is satisfied on this point will trust you with the rest.

Rules for testing and for reporting incidents differ by sector and change over time. Advise the buyer to check their own obligations with their legal or compliance adviser.

Pricing and scope on a single page

Buyers want to know how the fee is built. Explain, without publishing a rate card, what moves the price: the number of systems or applications, the depth of testing, whether a retest is included, whether the test is run from outside or inside the network. Put the fee in writing after a scoping conversation, and agree the term at the same time. A buyer who can see how the number is made trusts it.

List what is not covered, such as social engineering or physical access, so the buyer knows what remains untested after the work. An honest exclusion sounds more credible than a long list of services.

The questions a buyer's auditor will ask

If the test is for an audit, the buyer's auditor will read your report. Ask the buyer early what the auditor needs: the scope statement, the dates, the methods and the evidence of fixes. Write the report so those items are easy to find. A report that answers the auditor on first reading saves the buyer a round of requests, and that is a service in itself.

Finding the right person to speak to

In a larger company, the person who signs may not be the person who cares most. The security head chooses the firm, finance approves the fee, and the IT team does the fixing. Learn who each is and what each wants. Address your first note to the person with the problem, and give them a page they can forward to the others.

What to do next

Look at your own website as a security head would. Can they find a sample report, the names of your testers, and what a scope looks like, in under a minute? If any of the three is missing, that is where to start.

If you want a second read on how a buyer meets your firm and where the conversation stalls, tell us what you need. We will read your brief before we call.

Put the reading to work

Try this with your own records.

Bring questions from sales calls and examples of objections that delay a decision. Choose a subject expert who can check the substance, and identify evidence that can be published.

How to review the result

Ask a colleague to use the draft in a real buyer conversation. It should answer the question, support its claims, and make the next step clear without requiring a sales pitch to explain it.

Questions

Questions owners ask.

Should a security firm publish its sample report?
Publish a redacted sample, with real structure and invented system names, so the buyer sees how findings are written and rated. Never publish anything drawn from a client's real findings. Buyers trust the firm that shows its method and protects other clients' details.
Do small security firms lose every RFP to the big names?
No. Large buyers shortlist on certificates, tester credentials and similar work, and a small firm with the right credentials and a named senior tester stays in. Where the RFP needs an empanelment or a size you do not have, say so early and spend your time elsewhere.
Is fear-based marketing effective for security services?
It gets attention and loses trust. A buyer who is about to show you every gap in their systems wants a calm explanation of what you will test and what they will receive. Lead with the deadline they are working to, not the breach they dread.
Where do security buyers look for vendors?
They ask peers, their auditor and their firewall or cloud vendor's account manager, then check the firm's website, LinkedIn and published work. Be easy to confirm in all of those places, because the shortlist is usually made before anyone fills in a form.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design. One written way to sell, from first enquiry to repeat order.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.