LinkedIn Outreach Campaign for Engineering Leaders at Series A B2B SaaS Startups in NYC (2026)

Quick Answer: Use Origami — which includes a built-in LinkedIn sequencer on all paid plans — to refine your list, craft a 3-touch sequence, and send connection requests and follow-ups automatically. Track replies in one dashboard without exporting a single CSV.

---

You’ve already built a hyper-targeted list of Engineering Leaders at Series A B2B SaaS startups in New York City. (If you haven’t, read this guide on how to build a list of Engineering Leaders at Series A B2B SaaS Startups in NYC first, then come back.)

Now the real work starts: turning that list into conversations that actually lead somewhere.

Cold outreach to engineering leaders isn’t the same as emailing VP Sales or a CMO. These folks get a fraction of the volume, but they're ten times more allergic to fluff. One buzzword-heavy message and you’re ignored — or worse, burned.

Here’s the exact campaign I’ve run for a client selling a developer productivity tool into Series A SaaS engineering teams in NYC. We used Origami for everything: list building, enrichment, sequencing, sending, and tracking. The sequence itself is completely free — you only pay for the credits used to enrich your leads (plans start at $29/month).

I’ll walk through the whole process, give you the copy we used, and show you what to expect.

---

Step 1: Build the list in Origami (recap)

If you followed the parent guide, you already typed something like this into Origami's plain-English prompt:

"Find Engineering Leaders — CTO, VP of Engineering, Head of Engineering, Engineering Manager — at Series A B2B SaaS startups in New York City. Must have raised a Series A between Jan 2024 and Dec 2025. Include verified work emails, personal emails, LinkedIn profiles, phone numbers, and any signals like recent hiring for senior engineers or infrastructure roles."

Origami’s AI agent searched the live web, chained data sources (Crunchbase, LinkedIn, company career pages, GitHub, Twitter bios, you name it), enriched every contact, and returned a clean list. You got:

• Full name, title, and current company
• Verified work email and personal email (where available)
• Direct LinkedIn profile URL
• Phone number (often mobile, depending on coverage)
• Company details: headcount, funding stage, tech stack (if publicly mentioned), and recent news

If you’re starting from scratch, Origami's free plan gives you 1,000 credits — no credit card needed — which is more than enough to build and enrich a list of 200–300 engineering leaders.

---

Step 2: Refine and qualify the list for LinkedIn

Raw output is never perfect. You have to make it relevant for outreach.

I sat with the client and scrubbed the list manually inside Origami’s dashboard. Here’s what we looked at:

Title precision

“Engineering Leader” is a broad bucket. We segmented into three sub-buckets:

• CTO / VP Engineering / Head of Engineering – final decision-makers. Tend to respond better to strategic value props (team velocity, cost efficiency, scaling pain).
• Director of Engineering / Senior Engineering Manager – strong influencers. May own tooling decisions. Respond better to operational wins (code review speed, on-call pain, developer experience).
• Engineering Manager – team leads. Less likely to sign a contract but excellent for seeding internal referrals. We treated these as a separate, softer sequence.

Company fit

We dropped anyone whose company clearly wasn’t B2B SaaS (e.g., an ad-tech Series A we accidentally pulled). Then we filtered out:

• Companies with fewer than 20 employees (too early for a dedicated eng platform purchase; they’re still building the MVP with 2 devs).
• Companies with more than 200 employees (by Series A, a B2B SaaS company shouldn’t be that big yet — if it is, something’s off, or they’re no longer acting like a startup).
• Any remote-first company headquartered outside NYC (some leaders listed NYC but worked for a Delaware corp with zero NYC presence). We want the NYC density: they meet at the same local events, feel the same hiring pressure, and share context.

Signals of intent

Origami’s enrichment pulled hiring signals where available. We tagged anyone whose company was actively hiring for:

• Senior / Staff Platform Engineers
• DevOps or SRE roles
• “Developer Experience” titles

Why? Those hires are expensive, and they’re usually made when the team is feeling scaling friction. The CTO doesn’t post “I’m evaluating productivity tools” on LinkedIn, but a job listing for a Staff Platform Engineer screams “we have a scaling problem.”

After refining, we had 127 contacts that felt genuinely high-propensity.

---

Step 3: Create the LinkedIn sequence

Inside Origami, you have two options:

1. Paste your own templates: Write a 3-touch sequence yourself, paste the messages into the sequencer, set the delays between touches (Day 1, Day 3, Day 7 — or whichever cadence you prefer), and launch.
2. Let the AI agent write it: Ask Origami’s agent to generate a personalized 3-day LinkedIn sequence for all your leads automatically. The agent reads each lead’s profile data — title, company, industry, recent posts — and writes a message that sounds like you did the research. Every message feels custom, no manual copy-pasting.

For a campaign this tight, I recommend starting with option 1 so you control the benchmarks. Then you can let the agent optimize afterward.

Here’s the exact 3-touch sequence we used, targeting the CTO/VP Eng segment. You can steal it verbatim and tweak your value prop.

---

Day 1: Connection request (with note)

When to send: Tuesday–Thursday morning, NYC time. Avoid Monday (backlog pile) and Friday after 2 PM (brains already weekend).

Message (300 character limit):

Saw you’re leading eng at [Company] — respect the scaling push post–Series A. I help NYC-based Series A SaaS teams like [similar company name] cut code review cycles by 40% so engineers ship faster without chasing reviewers. Open to connecting.

Why it works: It’s short, uses their context (“post–Series A,” NYC), cites a similar company (social proof), and mentions a concrete benefit. No “I see we have 14 mutual connections” nonsense.

---

Day 3: Follow-up message (after they accept)

When to send: 2 days after they accept. If they haven’t accepted by Day 3, the sequencer can be set to skip this touch or send a gentle reminder. I prefer to auto-skip if not connected — too aggressive otherwise.

Message (direct message, ~80 words):

Appreciate the connect, [First Name]. Quick one: how’s your team handling the PR review bottleneck right now? I keep hearing from Series A CTOs in NYC that as headcount doubles post-raise, the old ad-hoc review process breaks — especially when you’re shipping a SaaS product under investor pressure. We built [Tool] so eng leads can automate the obvious review feedback and free up 10+ hours a week. Worth a 15-min call, or at least a link to a case study?

Why it works: It acknowledges the new connection, leads with a specific pain point (PR review bottleneck), leans on “NYC CTOs are telling me this” to normalize the problem, and gives a low-friction ask.

---

Day 7: Final message (soft close)

When to send: 4 days after the follow-up. This is the last touch. If they’ve opened the last message but not replied, this lands softly. If they’ve ignored both, still send — sometimes people need a third nudge.

Message (direct message, ~75 words):

Last nudge, [First Name] — I know your calendar is probably a war zone. If improving developer velocity matters this quarter, I’d be happy to show how two NYC Series A teams (similar scale to [Company]) cut their cycle time by 35% without adding headcount. Happy to share those numbers and a 5-min demo. If not, no worries — I’ll leave you to it.

Why it works: The “last nudge” signals finality (no one likes the never-ending drip). It re-frames around business outcomes (developer velocity, cycle time), uses NYC peer examples again, and leaves a polite exit — which often triggers a reply because you’re not begging.

---

Customization note

If you plan to A/B test, swap the value prop for something like:

• “Infrastructure cost visibility”
• “Developer onboarding time”
• “Alert fatigue reduction”

But always keep the structure: reference their stage, mention NYC peers, make a concrete ask.

---

Step 4: Send the sequence directly from Origami

This is where most outreach falls apart — list in one tool, sequencer in another, tracking in a third, and you lose context. Origami handles the full workflow in one place.

Setting up the sequence

Inside Origami’s dashboard, go to your refined list, click “Create Sequence,” and choose LinkedIn as the channel. Paste your Day-1, Day-3, and Day-7 messages into the touch points. Set the delays:

• Touch 1: immediate (or scheduled for the next weekday morning)
• Touch 2: 2 days after connection accepted
• Touch 3: 4 days after Touch 2

The sequencer knows to wait for a connection before sending Touch 2. If the connection is still pending, it can either delay further or skip based on your settings.

If you want the AI agent to generate the messages, just flip the toggle — it will write them personalized for each lead. I recommend this for the second iteration once you have reply rate baselines.

Sending and tracking

Hit “Launch.” Origami’s built-in LinkedIn sequencer sends connection requests and follow-up messages automatically with the delays you configured. No exporting CSVs, no syncing with Snov.io or Apollo, no browser extension required.

Everything appears in one dashboard: opens, clicks, replies, link clicks, and whether someone booked a meeting (if you integrate a calendar link). While viewing a contact’s activity, you can still see their enriched profile — title, company, tech stack, recent hiring signals — so you remember why you reached out in the first place. No more “Who is this person again?” while reading a reply.

Automatic un-enrollment

When a prospect replies, Origami automatically un-enrolls them from the sequence. No one accidentally gets a “last nudge” message after you’ve already booked a call. That alone saves you from the cringe of having to apologize.

One platform: find, enrich, sequence, send, track. No tool-hopping.

The sequencer is included on all paid plans — you’re only paying for the credits used to enrich leads. The actual sending is free.

What results to expect

For this specific audience — Engineering Leaders at Series A B2B SaaS startups in NYC — connected cold outreach, here are the reasonable benchmarks I’ve seen across multiple campaigns in 2026:

• Connection acceptance rate: 25–40%, depending on your own LinkedIn profile quality. Engineering leaders are more selective than sales leaders, but the NYC angle helps because it implies local relevance.
• Reply rate (of those connected): 10–18%. The Day-3 follow-up generates 60%+ of replies. The Day-7 closer catches another 20%.
• Meeting booked rate: 3–7% of the original list. Acceptable, given that you’re reaching the very top of the org chart.

If you see connection rates below 20%, your profile might need work — not your sequence. If reply rates are below 5% after three weeks, iterate the messaging; the list itself is probably fine.

When to iterate on the list: if you see high opens but near-zero replies, or you get a bunch of “not relevant” replies, revisit your qualification in Step 2. You might be hitting companies too early or too late.

---

Go run it

LinkedIn outreach to engineering leaders in NYC’s Series A SaaS scene isn’t about volume. It’s about showing up with context and a problem they recognize. Do the refinement work, steal the sequence above, send it from Origami’s built-in sequencer, and let the dashboard tell you what’s working.

If you still need to build the initial list, start here: how to build a list of Engineering Leaders at Series A B2B SaaS Startups in NYC.