How to Run a Cold Email Campaign to VP of Engineering and CTOs at Small Tech Companies in 2026

You built a list of VP of Engineering and CTOs at small tech companies using Origami. Now it’s time to turn that list into meetings. The good news: Origami has a built-in email sequencer — you don’t need to export or switch tools. This guide walks you through refining your list, crafting a 3‑touch sequence that resonates with engineering leaders, and sending it directly from Origami.

If you haven’t built your list yet, start with our guide on how to build a list of VP of Engineering and CTOs at Small Tech Companies. That post covers the exact prompt and filtering tricks. For a quick recap, here’s the prompt you’d type into Origami to get started:

“Find VP of Engineering and CTOs at small tech companies in the US, with 10–50 employees, that use modern cloud stacks (AWS, Kubernetes) and have raised seed or Series A funding.”

Origami returns a list with verified names, direct emails, phone numbers, job titles, company size, recent funding data, and the tools each company uses — all from a single prompt. Free plan: 1,000 credits, no credit card required. Paid plans start at $29/month with the sequencer included.

Now, let’s turn that list into a real outreach engine.

---

Step 1: Build the list (or retrieve it)

You already know the drill — but just to make it a seamless walkthrough: you describe your ideal engineer leader in plain English, and Origami’s AI agent searches the live web, chains data sources, and returns a clean CSV-like table inside the app. Every contact comes with an enriched profile: their title, company size, industry tags, tech stack guesses, and direct contact details. That’s your starting point.

When you target VP Eng and CTOs at small tech companies, the prompt matters. I’ve found that adding a couple of qualifiers — company stage, engineering headcount range, and recent funding — drastically improves response rates. For example:

“Find VP of Engineering or CTO at small US tech companies that have raised a seed or Series A round in the last 18 months and have between 15 and 50 employees. Include companies using cloud-native tooling.”

Origami will then give you a list of 100–200 leads in under a minute, complete with signals that tell you these people are likely in scaling mode.

If you already have your list saved from the earlier exercise, just open it in your Origami workspace and move on to refinement.

---

Step 2: Refine and qualify the list

Resist the urge to blast the whole list. Small tech companies are not a monolith — a CTO at a 10‑person bootstrapped startup cares about different problems than a VP of Engineering at a well‑funded 45‑person SaaS company. Before you write a single email, you need to slice your list into segments that let you speak to the right pain points.

Inside Origami, your enriched leads sit in a table where you can filter by company size, role, location, and even detected technology tools. Here’s how I qualify a raw list for this audience:

• Role segmentation: Group VP of Engineering and CTOs separately. CTOs at sub‑20‑person teams often still code daily and care deeply about tech debt and architecture. VPs of Engineering at 30–50‑person companies fight against process creep, slow deployment pipelines, and hiring bottlenecks. Your messaging will shift slightly between them.
• Company size buckets: 10–25, 26–50, 51–100 (if you expanded your prompt). The 10–25 bucket is your sweet spot for “we are moving from scrappy to structured” pain. The 26–50 bucket buys for “our half‑built CI/CD is breaking at scale” problems.
• Tech stack signals: If Origami detected that a company uses Kubernetes, Terraform, or Datadog, you know they are already paying for infrastructure and monitoring. They have budget. If they still use a hodgepodge of free-tier tools, they might be more cost‑sensitive — your offer needs a clear ROI.
• Funding recency: Seed or Series A closed within the last 12 months often means the engineering org is about to double. That’s a prime buying window. Older funding with a small team? They may be stuck in maintenance mode and harder to convert.

What “qualified” looks like for this funnel before you hit send:

• The contact is clearly a decision‑maker (not an IC acting as interim CTO).
• The company has at least 10 engineers (or a public team page that shows growth).
• There’s a visible technical challenge — scaling, reliability, or velocity — that you can reference organically.
• The email address is verified (the green check in Origami tells you it passed validation).

Once you’ve segmented, tag the contacts with labels inside Origami so you can send different sequences to each bucket later.

---

Step 3: Create the email sequence

Now the meat of the campaign: the words that get a reply. In Origami, you have two ways to build a sequence.

Option 1 — Paste your own templates: You can write a 3‑touch sequence yourself (copy mine below), paste the templates directly into Origami’s sequencer, set the delay between touches (Day 0, Day 3, Day 7 — or whatever cadence you want), and hit “Launch.” This gives you full control over voice and offer.

Option 2 — Let the agent write it: Alternatively, you can ask Origami’s AI agent to generate a personalized 3‑day email sequence for all of your leads automatically. The agent uses each lead’s profile data — title, company, industry, detected tools — to craft messages that feel custom. You can then review and tweak before sending.

My recommendation for VP Eng and CTOs: start with your own copy because the narrative needs to be deeply technical and peer‑level. The AI is great for adding light personalization touches afterwards, but the core story should sound like another engineering leader wrote it.

Below is the exact 3‑touch sequence I’ve used to book meetings with engineering leaders at small companies. Replace the placeholders and the description of your product/service. Each message is short enough that a busy VP can read it in under 15 seconds on a phone, and every line pushes toward a clear next step.

Email 1 – Day 1: Initial outreach

Subject: , a thought on 's engineering velocity
Preview: Fast-growing teams often hit the same wall.

Hi ,

I’ve been looking at how small engineering teams scale, and stood out. The jump from 10 to 25 engineers often introduces tech debt and process bottlenecks that silently kill shipping speed.

I help VPs of Eng like you avoid that — we built a lightweight platform that reduces incident response time and brings deployment consistency, without adding headcount.

Worth a 15‑minute call to see if it’s relevant? Happy to share a 2‑minute video overview first if you prefer.

Best,

(Word count: 98)

Email 2 – Day 3: Follow‑up

Subject: Re: engineering velocity
Preview: A different angle on the same problem.

, following up with a different lens.

When I saw ’s stack includes some cloud‑native tooling, I thought of how we helped a similar 20‑person team cut deployment downtime by 40% in one month. No magic — just consolidating the monitoring and alerting spaghetti into one clear pipeline.

I bet you’re already thinking about reliability as the team grows. If you’d find a 20‑minute walkthrough useful, I’ll send over a timeslot. If not, no harm done.

Cheers,

(Word count: 85)

Email 3 – Day 7: Breakup

Subject: Closing the loop,
Preview: A resource you might actually find useful.

, I’ll keep this short.

If now isn’t the right time to chat about scaling engineering, I totally understand. However, since you’re likely wrestling with similar growing pains, I thought you’d find this [case study / guide] useful — we break down how a 25‑person team shipped 2x faster after fixing their CI/CD pipeline.

If you’d be open to a conversation down the road, reply here and I’ll circle back in a quarter. Otherwise, best of luck building.

(Word count: 90)

How to adapt the sequence

• Replace “platform that reduces incident response time” with whatever you actually sell — but keep it concrete. Engineering leaders hate vague “we optimize your workflow” speak.
• Swap the tech stack mention in Day 2 with a real signal from Origami’s enrichment (e.g., “When I saw you use Kubernetes and Terraform” — that specificity alone lifts reply rates).
• Link to a case study or a relevant blog post in Day 7. Make it something genuinely educational, not a sales deck.
• Add a soft CTA like “reply ‘yes’ and I’ll send the video” if you want to lower the friction of a meeting.

Once your templates are ready, paste them into Origami’s sequencer, one after another, and set the delays. I like Day 1, Day 3, Day 7 because it’s persistent without feeling spammy. If you are feeling bolder, you can add a Day 12 soft touch — a plain-text “thought you might like this article” note — but a 3‑touch cadence is the minimum viable campaign that still gets replies.

---

Step 4: Send the sequence directly from Origami

With your templates in place and the list segmented, you launch the sequence directly inside Origami. No CSV exports, no syncing with a separate cold‑email tool. Origami’s built-in email sequencer does everything for you.

Here’s what happens after you hit Launch:

• The sequence automatically sends the Day 1 email to all contacts. Day 3 follows up only to those who didn’t reply, and Day 7 only to the remaining non‑responders.
• Automatic un‑enrollment: If someone replies — even a “not interested” — they are instantly removed from the sequence. You will never accidentally send a breakup message after you’ve already booked a meeting. That alone saves the social capital of a sloppy outreach.
• Sending & tracking: Opens, clicks, and replies appear in the same dashboard where you built the list. No hopping between tabs. While looking at a contact’s activity, you can still see their enriched profile — title, company size, tools used — so you always remember why you reached out in the first place.
• Prospect context: That enriched data stays attached to every lead. When you get a reply, you don’t have to dig through a spreadsheet to recall what they do; it’s right there next to the email thread.
• Cost: The sequencer itself is free on all paid plans. You only pay for the credits used to enrich the leads. So once you have your list, the actual sending doesn’t add a cent. Even on the free plan, you can sequence up to 1,000 leads with your initial credits.

What response rates to expect

For a well‑targeted list of VP of Engineering and CTOs at small tech companies, here’s what I’ve seen in 2026:

• Open rates: 45–65% on the first email if you personalize the preview line and the first sentence refers to their company. Generic blasts land around 20–30%.
• Reply rates: 3–8% across a 3‑touch sequence is a realistic range. I’ve hit 12% when the offer was exceptionally relevant (e.g., a tool that solved a known Kubernetes pain) and the list was filtered to companies that recently adopted K8s.
• Meeting booked rate: Roughly half of replies turn into a scheduled call if your follow‑up is fast (under 2 hours) and you share a calendar link immediately.

Don’t treat these numbers as gospel. Early‑stage outreach is a numbers game, but a small, deeply qualified list will almost always outperform a large, loosely filtered list.

When to iterate on messaging vs. iterate on the list

If after 2–3 weeks you’re seeing high opens (above 50%) but very few replies, your subject line and preview text are working — but the body doesn’t give them a reason to respond. Tweak the pain point, sharpen the CTA, or add a specific signal from their company before you change the list.

If opens are consistently below 30%, the problem is likely technical (domain reputation, spam folders) or your list contains too many generic info@ email addresses. Run a quick deliverability check and re‑filter your list to only keep verified personal emails. Origami marks bounce risks before you send, so pay attention to those warnings.

If replies are coming but meetings aren’t, your offer may be too vague or the timing is off. Try adding a value‑first resource in Day 2 instead of a direct meeting ask — sometimes that nurture step makes the difference.

---