Mid-size organizations buy security services when a date forces them to, and most of those dates are published before anyone calls a security firm.
- A breach notice is filed with a state attorney general or the federal health breach portal.
- A small business wins its first defense contract and inherits a CMMC assessment with it.
- A company posts its first CISO or security engineer role, or leaves one open for two months.
- A newly funded software company starts asking for SOC 2 in its job ads.
- A lender or insurer is newly licensed under a state cybersecurity rule.
Reach the accountable executive inside that window and the conversation is about scope and timing, which is the conversation a security firm wins.
This guide compares seven channels by estimated cost per signed first engagement and ends with a 30-day plan.
Referrals from auditors, brokers, and MSPs
The best security clients usually arrive through someone the buyer already trusts.
Three referral sources matter more than the rest:
- Audit firms. A SOC 2 or financial auditor meets organizations the month they discover a gap, and cannot fix it themselves.
- Cyber insurance brokers. The renewal questionnaire exposes missing controls, and the broker wants the client to pass.
- Managed IT providers. An MSP without a security practice needs a partner for assessments and incident work.
Referrals cost nothing per lead and cannot be scaled on demand. Treat them as the return on doing good work for the people who send them, and keep them separate from the plan for next quarter.
Conferences and local security events
Regional security conferences, industry association events, and local chapter meetings put a firm in front of buyers and peers.
| Metric | Range |
|---|---|
| Cost per event | $3,000 to $20,000 with a booth or sponsorship |
| Conversations | 10 to 40 useful ones per event |
| Time to first engagement | 3 to 9 months |
| Best fit | Firms with a clear sector specialty |
Those are estimates. The weakness is timing: the people at the booth are mostly learning, and the ones with a deadline are rarely there that week.
Vendor and distributor partner programs
Security product vendors and distributors pass service work to partner firms that sell and support their products.
The work is real and the volume can be steady. The relationship belongs to the vendor, and the firm is often competing with other partners for the same referral.
Partner programs work best as a floor under the practice. A firm that depends on them has handed its growth rate to someone else’s sales team.
Appointment-setting agencies
Security-focused appointment-setting agencies run outbound on a firm’s behalf and deliver booked meetings.
| Metric | Range |
|---|---|
| Monthly retainer | $4,000 to $12,000 |
| Meetings delivered | 4 to 10 a month |
| Fit quality | Varies widely |
| What remains when it stops | Very little |
The best agencies know the market. The common weakness is generic targeting, because most agencies prospect by title and headcount with no event behind the message.
Paid search and content
Search reaches genuine intent on terms like penetration testing or SOC 2 readiness.
Budget $2,000 to $8,000 a month to hold position on service terms, an estimate, with clicks that are among the most expensive in B2B services.
Content compounds more slowly and more cheaply. A firm that publishes clear guides on one framework for one sector earns search traffic that paid clicks cannot match, though it takes six to twelve months to show.
Intent data and bought leads
Products sold as cybersecurity leads fall into two groups:
- Intent-data platforms. Lists of organizations researching security topics, from about $15,000 a year.
- Shared form fills and list vendors. Contacts sold to several firms at once.
Both say an organization might be interested. Neither says it has a deadline, and a message with no event behind it replies at under 1%.
As a lookup for an organization you already have a reason to contact, a list is useful. As a prospecting source it produces generic pitches.
Trigger-based outbound from public records
Record-driven outbound has the lowest cost per scoping call of any channel that scales, at about $180 a month in tools, producing 390 to 680 prospects and 6 to 14 scoping calls a month. Those are estimates for one firm with a 3 to 6 sector focus.
The five records to watch
- Breach notices posted by state attorneys general and the federal health breach portal.
- Federal defense awards to small businesses with no prior defense contract.
- Security job postings where the company has never hired for security before.
- Form D filings at software companies whose job ads mention SOC 2.
- New financial licences under NYDFS, the FTC Safeguards Rule, or state insurance data security laws.
The method, in four steps
- Read the records daily or weekly. All five are public and free.
- Filter to your practice. 25 to 1,000 employees, sectors you have delivered in, no named forensic or managed security provider.
- Find the executive who owns the risk. The CTO after a funding round, the owner at a small defense supplier, the compliance officer at a lender, counsel after a breach notice.
- Send a short sequence whose first line names the record and whose offer is one fixed-scope first engagement.
“Congratulations on the Navy contract awarded on the 9th” gets read. “We are a full-service cybersecurity provider” gets deleted.
What the numbers look like
| Stage | Estimate |
|---|---|
| Reply rate on breach notice and award rows | 3 to 6% |
| Reply rate on new licence rows | 1 to 3% |
| Replies on 390 to 680 prospects | 8 to 34 |
| Scoping calls booked | 6 to 14 |
| Call to signed first engagement | 20 to 30% |
One rule matters more than any number here. A breach notice may start a conversation and may never be described in it: cite the regulator and the date, and nothing about the incident.
The workflow, the five record feeds, the filter logic, the sequence, and the stack costs are documented in the Cybersecurity Lead Gen System. It runs on n8n Cloud and you own every piece of it.
Buying lists versus owning a system
A purchased list is a set of names someone else compiled and sold to every security firm in the market. It carries no timing, and it stops when the subscription stops.
An owned system reaches an organization in the weeks when its obligation is genuinely new, on a record the organization or its regulator published, for a fixed monthly cost.
The compounding matters more than the arithmetic.
Every organization the system touches stays under observation, so a defense supplier that wins a second award comes back the same week, and one that named its incumbent provider resurfaces 75 days before the contract end it mentioned.
The record history becomes an asset nobody can sell you:
- Which providers hold which organizations in your sectors, and when those contracts end
- Which small defense suppliers in your region face an assessment this year
- Which companies have tried and failed to hire a security leader
What to do first
Thirty days, in order.
Week 1: write the firm profile
- Sectors you have delivered in, with a client count for each
- States to watch for breach notices and licences
- The frameworks you know best, since the filter and the templates lean on them
Week 2: build the credential sheet and the catalogue
- Credential sheet. Certifications held by named staff, frameworks delivered, insurance limits, and one redacted report page.
- Service catalogue. Three to five fixed-scope first engagements with deliverables, duration, and a price band.
- Vendor pack. Your own security policies and data handling answers, because the buyer’s questionnaire follows every yes.
Week 3: domain, proposal document, two-day rule
- Buy a separate sending domain with SPF, DKIM, and DMARC at enforcement, and start warmup.
- Build the scoping proposal document so an intake form becomes a branded proposal with its assumptions written out.
- Set a rule that every proposal goes back inside two business days, because a buyer with a deadline signs the first clear scope.
Week 4: send the first 10 by hand
Send the first 10 emails by hand before automating anything. The opening line has to read like it came from someone who looked at the award or the licence.
Then review the reply rate by trigger against the system spec and change one thing at a time.
