Short answer: yes, and it's the category I've built the most outbound systems for. But "can you" is a boring question, so here is the actual build, in the order I do it.
Why B2B SaaS outbound usually fails
Not because the list was too small. Because the list was too broad and the message had nothing true in it. The typical SaaS campaign targets a title at a company size in an industry, which describes tens of thousands of companies, most of whom have no reason to care this month. Fit is not timing, and outbound lives on timing.
Step 1: Qualification gates that run before enrichment
Every company passes hard filters before it costs me a cent to enrich. For a typical sales-led SaaS client the gates look like this:
- Business model gate. B2B software sold on recurring contracts. Agencies, services firms, marketplaces, hardware, and consumer products are removed, not "deprioritized."
- Geography gate. An explicit country list, chosen for where the client can actually sell and support. If the team sells in a second language, that's a reply-rate advantage worth building a segment around.
- Deal-size proxy gate. ACV isn't public; the pricing page is. Qualify a company if the pricing page has a "Contact sales" or demo-only tier, an Enterprise or Custom tier, or no public pricing plus a demo form. Remove it if every tier is self-serve and priced below a low threshold, or if checkout is card-only with no path to a human. This one rule is the single highest-leverage filter in SaaS outbound.
- Pain-proxy gate. Some minimum of visible Account Executive headcount, or a smaller AE count plus a recent open sales requisition. This proxies the real question: is there already a sales team whose top of funnel someone has to fill? A company with one rep has a hiring problem, not a systems problem.
- Size and stage gates. A floor and a ceiling on headcount, and a funding or revenue stage band. Above the ceiling, companies usually have an in-house GTM function and buy tools instead of help. Below the floor, they don't have the budget or the problem yet.
Companies that fail a gate aren't deleted forever. Most go to a monitoring pool, which matters in step 4.
Step 2: Two lanes, run in parallel
I split the market into two lanes because they have completely different economics.
Lane 1: signal-triggered, runs first
Three timing signals put a company in an active buying window: a new revenue leader in the seat under 90 days, a Series A or B announced under 120 days ago, or an open SDR/BDR/GTM Engineer requisition posted in the last 30 days. In each of those windows the buyer has budget, mandate, and an unsolved problem simultaneously. The window is short, so this lane jumps the queue and gets the sharpest copy.
Lane 2: pain-qualified coverage
Everything that passed the gates gets contacted with a persona-appropriate sequence per contact slot. Qualification here is done with public signals rather than purchased intent data. I'd rather reason from something I can point at on a page than from a vendor's black box.
Step 3: Contact mapping, decision-makers only
Up to three contacts per company, chosen by role cascade rather than by whoever had a findable email. The most senior revenue leader first (CRO, then VP Sales, then VP Revenue, then Head of Sales, and so on; first match wins, empty if none exists). Then the operations or growth counterpart. Then the founder or CEO if the company is small enough that they're still in the revenue seat.
What I deliberately skip: SDRs and individual AEs reporting upward. They can't buy, and forwarding a vendor pitch to their boss is, at best, career-neutral for them.
Step 4: The monitoring layer
Every non-responder goes into a pool that gets watched for the same signals from Lane 1, plus tooling changes. When a signal fires, that prospect gets one contextual re-engagement message referencing the change, not another full sequence from the top. This is where a big chunk of pipeline comes from in month three and beyond, and it's the part most agencies never build because it doesn't produce a number in week one.
Step 5: Copy that earns the open
Each segment exists because of a specific data point, so the copy leads with that data point. The structure I use: one line establishing why them specifically, one line naming the pain in their language, one line on the mechanism, one piece of verifiable proof, one low-friction ask. Multiple variants per step, spintax on the phrases that don't carry meaning, and conditional blocks so a lead missing an enrichment field still gets a coherent sentence instead of a blank.
The rule I hold hardest: every claim in the email must be verifiable on the client's own site. Outbound should never write a check the sales call has to cash.
Step 6: Infrastructure and measurement
Domains and inboxes sized to the send volume, warmup running before anything sends, tracking configured deliberately, replies categorized so "positive" means something specific (interested, meeting booked, meeting request, or information request) rather than "someone typed back."
Then the loop: reply rate and positive-reply rate per segment, per role, per variant. Kill the losers, expand the winners, and re-hit the full addressable market on a rotation as new signals fire.
What this looks like on a calendar
Week 1 is strategy and infrastructure. Weeks 2-3 are TAM build, enrichment, qualification, and copy. Week 4 launches in controlled batches. Weeks 5-8 are iteration toward message-market fit. From there it's scale and handoff, and you should end up owning the tables, the scripts, and the runbook.
If you want to see the SaaS-specific campaigns I've already run (trial-conversion targeting, churn-reduction platforms, data enrichment tools, AI search optimization), they're in the case studies with the data source and angle for each.