Leads StarterLeads Starter

You sell an engineering productivity platform to VPs of Engineering at Series A B2B SaaS companies, 30 to 120 people, in the quarter after a raise, when headcount grows faster than the tooling around it.

Two companies from last month raised again and moved up the list. Four of the twelve accounts you were watching filled the role you were targeting, so they drop out. This batch is entirely new companies.

Email: [email] (verified, listed on the engineering blog author page).

Signal: closed a 14[personne] A eight weeks ago, 6 backend roles opened the same month (careers page).

Pain point: onboarding capacity, not hiring. The last two engineering posts are about ramp-up time.

Opening line: "Six backend openings eight weeks post-Series A usually turns into an onboarding problem before it turns into a capacity win. Your last two posts read like you are already there. How are you handling ramp-up?"

Email: [email] (pattern, first name at domain, matches two public addresses).

Signal: engineering post naming the monolith split as the two-quarter priority.

Pain point: observability was not scoped into the migration plan they published.

Opening line: "Your monolith split post scopes the two quarters carefully but never mentions observability. That is usually the part that gets discovered halfway. Is it already on the plan?"

Email: [email] (verified, conference speaker page).

Signal: Staff Engineer posting explicitly scoped to replacing the in-house deploy pipeline.

Pain point: an in-house pipeline nobody wants to own, being rebuilt rather than replaced.

Opening line: "Your Staff Engineer posting puts the in-house deploy pipeline up for replacement. What is pushing you to rebuild rather than buy?"

Contact Dana first: the signal is 8 weeks old and the pain point is already public in their own words. Then Priya, whose posting states the buying intent outright. Marcus third: strong fit, but the email is a pattern match, so verify before a sequence.