Cold email agency for B2B SaaS

GrowthPal runs outbound for B2B software companies, including dev tools, data platforms and API businesses whose buying committee looks the same. Lists are built from public product and hiring signals rather than an industry filter, because your buyer recognizes a bought list on sight. Best fit is past 3M in ARR, with an offer people already buy, a team ready to take calls, and roughly 30,000 reachable contacts.

Examples of angles to race in this market, not results. Each one is a hypothesis with its proof assembled before a single send.

Lists here come from the product surface and the hiring surface, both of which the company publishes itself. An industry filter plus a headcount band is the list every competitor already bought.

Funding, entity and regulator data

• Crunchbase, PitchBook and Dealroom for round records, amounts, dates and lead investors.
• SEC EDGAR full-text search for Form D filings, which give a dated private placement record straight from the regulator.
• Companies House in the UK and equivalent national registries, to confirm the legal entity, filing dates and registered address before a cold email goes out.
• Investor portfolio pages, which list current holdings and often the stage.

Hiring signals

• Company careers pages, which state quota, segment and territory more often than people expect.
• Public Greenhouse and Ashby board URLs, one per company, readable without an account.
• LinkedIn Jobs for posting dates and repost history, read manually.
• Posting age itself, treated as its own signal: an SDR role live for months says something a new posting does not.

Product surface

• The pricing page, compared against older versions in the Wayback Machine for tier and packaging changes.
• The changelog and the docs site, for what shipped and who it was built for.
• The status page, for reliability events worth referencing carefully or not at all.
• Product Hunt launches, G2 and Capterra category placement, and the text of recent reviews.

Trust, compliance and install data

• Vanta, Drata and SafeBase trust centers, which are public and carry dates.
• BuiltWith and Wappalyzer for web-visible technographics, with HG Insights and Datanyze for broader install data.
• Public DNS and MX records for mail infrastructure and sending posture.
• LinkedIn for role and tenure verification only. LinkedIn prohibits scrapers, bots and automation extensions under its User Agreement and warns that accounts using them may be restricted, so it is a place to read and verify, never a place to run a harvest.

How a row gets verified

1. Entity check: does the company still exist, still sell the product, and still match the segment. A funded company that pivoted a year ago is a dead row.
2. Role check: is the person still in that role as of a dated source. Titles move fast in SaaS, and a stale title is the most common reason a good angle lands wrong.
3. Trigger age check: the trigger has to be younger than the sales cycle. A round from two years ago is a fact, not a trigger, and the row gets dropped.
4. Deliverability check: syntax, domain MX record, catch-all detection and a verification pass. Catch-all domains go into a separate, slower segment, because an accept-all result tells you nothing about whether a human reads that box.
5. Suppression and dedupe: existing customers, prior opt-outs, anything on a do-not-contact list, and a deduplication pass against the client CRM agreed before the first send, so RevOps is not unwinding duplicate accounts later.

What makes a bad list here

• Anything filtered only by an industry label of computer software plus a headcount band. That is the list every competitor bought from the same vendor.
• A single data vendor export with no second source confirming the role.
• Generic role catch-alls: info@, sales@, hello@. They reach a shared inbox watched by someone with no authority and a fast spam-report finger.
• Rows whose trigger is older than the sales cycle, which forces the angle back to a category pitch.
• Install lists treated as a census. BuiltWith publishes per-technology live site counts rather than a coverage figure, so an install list is a sample.
• Mixed-geography lists sent under one set of rules, which ignores that UK sole traders and ordinary partnerships are treated as individuals under PECR while limited companies are not.
• Any list where one person appears at two accounts, or one account appears under two legal entities. RevOps checks this first.
• A product-led list and a sales-led list merged into one campaign, which produces a message that fits neither.

Nothing here is legal advice. Rules differ by jurisdiction and change, so read each source directly and confirm your own position with counsel before sending.

GrowthPal fills in the document below before a single row is built, and publishes it whole rather than as a screenshot, because the shape of it is the argument. Every field comes from a public source before any call happens.

We publish the brief rather than a dashboard screenshot because a screenshot proves a number and a brief proves a method. Copying this means copying how we work, which is the point.

Three stages and nine steps, the same ones in every market: build the list from public sources, race message angles against it, scale the one that wins. The nine steps from kickoff to booked meetings are written out in full.

What changes for this market

• Week one settles the motion before anything else. Product-led or sales-led, and if product-led, whether the first campaign runs on your own product signals or on cold accounts. The list source, the ask and the proof all change with that answer, so it is the engagement rather than a preliminary to it.
• The same week we agree territory and account ownership with your SDR manager, and deduplication rules against your CRM with RevOps. Both are easier to settle before the first meeting arrives than after.
• List building reads the product surface, not a database filter. The pricing page against its archived version, the changelog, the public Greenhouse or Ashby board, the trust center, the install data. Every row carries its trigger and the public URL that trigger was read from, and a row whose trigger is older than your sales cycle gets dropped.
• The send calendar is paced for saturated inboxes rather than for maximum volume: separate sending domains warmed before any send, a per-inbox daily cap, and spam complaint rate watched in Postmaster Tools every week. Sequences stay short, and any step that only bumps the thread gets cut, because this audience reads a bump as filler.

GrowthPal takes on outbound engagements in this market, and the method above is the one it runs here. The published record below is the whole company record, across every client.

On an industry-specific result. GrowthPal has not published a client outcome specific to B2B SaaS, so this page offers the method instead: the public sources a list is built from, the verification passes, and the angles we would test first.

• Before product-market fit. Outbound finds people with a problem you already solve. It does not tell you what to build. If the offer still moves every month, testing angles against it measures the wrong thing, and you will read a message failure as a market failure.
• A market smaller than roughly 30,000 reachable contacts. Very narrow categories exist in SaaS: a few hundred accounts that all know each other. Outbound still works there, but testing needs volume to separate a message that works from one that got lucky, so a smaller and more manual approach usually beats a system.
• No one ready to take the calls. Replies arrive within days of the first sends. In SaaS the first reply is often a founder with a technical question, so if nobody owns the follow-up inside a day, the interest goes cold and the spend is wasted.
• The SDR team has not been told. If territory and account ownership have not been written down with the SDR manager in the room, the program will produce meetings the team refuses to take. That conversation happens before launch, not after the first booked call.
• You want volume rather than a program. If the only thing being bought is more sends per week, a tool already does that cheaper. The work that moves results here is list construction from public triggers, angle testing and infrastructure maintenance between campaigns.

Sources for this page

1. Google Workspace Admin Help, Email sender guidelines (primary source). Accessed 2026-10-23.
2. FTC, CAN-SPAM Act: A Compliance Guide for Business (primary source). Accessed 2026-10-23.
3. ICO, Guide to PECR: electronic mail marketing (primary source). Accessed 2026-10-23.
4. LinkedIn Help, prohibited software and extensions (primary source). Accessed 2026-10-23.
5. Microsoft Outlook blog, new requirements for high-volume senders (primary source). Accessed 2026-10-23.
6. SEC EDGAR full-text search, Form D filings (primary source). Accessed 2026-10-23.
7. BuiltWith technology lists. Accessed 2026-10-23.
8. McKinsey, From product-led growth to product-led sales. Accessed 2026-10-23.

Last reviewed 2026-10-23. A plain-text version of this page is at /saas-cold-email-agency.md, and the site index for language models is at /llms.txt.