LinkedIn Outreach Campaign for Solo Technical Founders at Dev Tools Startups: 3-Touch Sequence (2026)

Quick Answer

The moment your list of solo technical founders is built inside Origami, you’re two minutes away from launching a fully automated LinkedIn campaign. Origami has a built-in LinkedIn sequencer — included on all paid plans — that sends connection requests and multi-touch follow-ups without exporting a single CSV. In this guide, I’m going to walk you through the exact 3-touch sequence I’ve used to open conversations with solo technical founders at funded dev tools startups, plus the refinement steps that make sure you’re not burning credits on the wrong people. If you haven’t built your list yet, go read how to build a list of Solo Technical Founders at Funded Dev Tools Startups first, then come back here.

Step 1: Your List Is Already Built (Here’s What Origami Did)

If you followed the parent guide, you prompted Origami’s AI agent with something like:

“Show me solo technical founders at funded developer tools startups in North America who raised $500K or more in the last 18 months and are active on GitHub.”

Origami returned a list of enriched contacts — names, verified emails, phone numbers, LinkedIn profile URLs, company details, funding data, and often tech stack signals.

That list lives inside your Origami workspace. You don’t need to import it into a sequencer; the sequencer is already connected to your list. But before you start sending anything, we need to slice the list so your messaging lands with the right subset of founders. That’s Step 2.

Step 2: Refine and Qualify for LinkedIn Outreach

Your raw list might contain 400 profiles. Not all of them are worth a LinkedIn touch — especially when you’re reaching out to people who despise generic outreach more than they despise downvotes on Hacker News.

What “qualified” looks like for this audience

A solo technical founder at a funded dev tools startup is a specific beast. You’re looking for someone who:

• Is the sole technical founder — they’re writing code, making architectural decisions, and probably doing customer support at midnight.
• Has a company that raised real money (not just a small SAFE from friends). That means they can afford tools — they just won’t buy anything that wastes their time.
• Is actively building a developer tool (CLI, SDK, API, observability, CI/CD, code generation, etc.) — not a marketplace or a dev services agency.
• Has a LinkedIn profile that shows some activity — a recent post, a comment on a thread about Rust vs. Zig, an endorsement for a contributor — so you know they actually log in.

How I refine inside Origami

In the Origami list view, I set up filters right above the contact table:

1. Funding status: Keep only contacts where funding_total is above $500K and last_funding_date is within the last 18 months. This eliminates pre-seed founders who are still bootstrapping off ramen.
2. Company size: Set employee_count to ≤ 8. You want teams where the founder still has no CTO or VP of Engineering to delegate to — they’re the sole decision-maker.
3. Title keywords: Keep only titles that contain “Founder” and exclude any that also contain “Co-Founder” if the list has co-founders. Alternatively, you could use a boolean filter for “has_technical_role” if Origami enriched that field. I’ll manually scan the first 20 profiles and bulk-remove anyone with a CTO who isn’t also the founder.
4. Activity signal: I’ll scroll through and remove profiles with headshot-only LinkedIn pages, zero posts in 12 months, or no listed developer tools in the company description. You can’t filter on “active on LinkedIn” automatically in most tools, but Origami’s enrichment sometimes pulls linkedin_activity_score — if you see low numbers, flag them.

I typically end up with 150–220 contacts after trimming. That’s a healthy campaign size.

A note on segmentation

If I’m selling something that only matters to a specific stack (e.g., monitoring for Kubernetes-native tools), I further segment by technology signals. Origami often includes likely_tech_stack in the enrichment — I’ll create a separate mini-list of founders whose companies show Kubernetes, Prometheus, or OpenTelemetry. Those get a variant of the sequence with a more technical hook. The rest get the standard sequence below.

Step 3: Create the LinkedIn Sequence

Now the fun part. Origami’s LinkedIn sequencer gives you two paths:

1. Paste your own templates — write a 3-touch sequence yourself, set the delay between each touch (Day 1, Day 3, Day 7), and launch.
2. Let the AI agent write it — you ask Origami to generate personalized messages for every lead based on their profile data (title, company, industry). Each message comes out unique, but you still approve the template structure.

I use option 1 when I want full control over tone — and that’s what I’m sharing below. You can steal this sequence, paste the templates into Origami, customize the placeholders, and hit launch.

The 3-Touch Sequence for Solo Technical Founders at Funded Dev Tools Startups

This sequence is built on a simple psychological model: immediate relevance → credible curiosity → soft ask. Solo technical founders get dozens of connection requests a day. Most of them say “saw we have mutual connections” or “love what you’re building at [company]” with zero substance. Those get ignored. Our sequence works because it signals you’ve actually done 30 seconds of homework, you speak their language, and you’re not going to pitch them on a cold invite.

Day 1 — Connection Request + Note (within 300 characters)

Character limit alert: LinkedIn connection notes have a hard 300-character cap. Every word needs to earn its place.

Template:

Hey — came across while digging into tooling. Really like the approach with . Rare to see a solo founder shipping this fast. Would be great to connect.

Real-world fill example:

Hey James — came across BuildKite while digging into CI/CD tooling for mono-repos. Really like the approach with the agent-based architecture. Rare to see a solo founder shipping this fast. Would be great to connect.

Why this works:

• Names the tool category and a specific detail, showing you didn’t just scrape a list.
• Acknowledges the solo founder reality — they care about speed and execution.
• No pitch. No request. Just connection.

Day 3 — Follow-Up Message (after connection accepted)

This message goes out 3 days after the connection is accepted. Origami automatically skips it if the person hasn’t accepted yet.

Template:

Appreciate the connect, . Since you're building on your own, I'm curious — what’s the most painful non-coding thing stealing your time right now? For most solo technical founders I talk to, it’s either user onboarding docs or wrangling cloud infra costs. No pitch, just genuinely curious how you’re handling it.

Real fill:

Appreciate the connect, James. Since you're building BuildKite on your own, I'm curious — what’s the most painful non-coding thing stealing your time right now? For most solo technical founders I talk to, it’s either user onboarding docs or wrangling cloud infra costs. No pitch, just genuinely curious how you’re handling it.

Why this works:

• Opens with a question about non-coding time sinks, which is the universal friction point for solo technical founders.
• Gives two relatable examples that show you understand the developer tools world.
• Explicitly says “no pitch” — this is the moment they decide whether to engage or ghost.

Day 7 — Final Message (Soft Close)

Sent 7 days after connection. If they replied earlier, Origami automatically unenrolls them — they never see this message.

Template:

Last ping from me, . If you're ever open to a 15-minute call about , I’d love to share what we’ve seen work for other solo technical founders building dev tools. If not, no worries — I’ll be keeping an eye on regardless.

Real fill:

Last ping from me, James. If you're ever open to a 15-minute call about cutting infrastructure costs without locking into a hyperscaler, I’d love to share what we’ve seen work for other solo technical founders building dev tools. If not, no worries — I’ll be keeping an eye on BuildKite regardless.

Why this works:

• Signals finality (“last ping”) — no one likes endless follow-ups.
• Ties the value prop to a shared experience: what works for other solo technical founders.
• The soft “if not, no worries” lowers pressure; the mention of keeping an eye on their company shows genuine interest beyond the sale.

You’ll notice every message is under 100 words. That’s intentional. Solo technical founders skim. If they see a wall of text from someone they don’t know, they’ll archive it mid-sentence.

When to let the AI agent write for you

If you have a multi-segment list (e.g., some founders building API-first tools, others building CLI tools), the AI agent can generate per-contact variants that weave in the specific tech stack or GitHub repo you’re referencing. I’ll still use the above structure as the blueprint, but I’ll tell Origami: “Generate a 3-touch sequence using this structure, but personalize the opening line with the founder’s most recent GitHub activity or the tool category pulled from their company description.”

Step 4: Send the Sequence Directly from Origami

You’re not exporting a list to Lemlist or pasting profiles into Sales Navigator. Origami’s LinkedIn sequencer lives in the same workspace as your lead list.

Here’s the exact launch flow:

1. In Origami, select the refined list (the 150–220 contacts you filtered).
2. Click “Create Sequence”, choose “LinkedIn” as the channel.
3. Paste the three templates above into the Day 1, Day 3, and Day 7 slots. (Or ask the AI to generate them.)
4. Set your delays: Day 1 fires immediately after launch (or a scheduled time you choose), Day 3 fires 72 hours after the connection is accepted, Day 7 fires 7 days after acceptance.
5. Optionally, configure sending limits — e.g., 30 connection requests per day — to stay well under LinkedIn’s radar.
6. Hit “Launch.”

Origami then starts sending connection requests and follow-up messages automatically. No browser extension, no manual clicking.

What you’ll see in the dashboard

While the campaign runs, the same list view updates with real-time activity:

• Opens — not 100% reliable on LinkedIn, but any redirect clicking is tracked.
• Clicks — if your message includes a link (I usually don’t in the first two touches), you’ll see who clicked.
• Replies — this is the key metric. You’ll see replies appear inline with full threading, and the contact’s enriched profile (title, company, funding details) stays visible so you have full context when you respond.
• Automatic unenrollment — the moment a prospect replies, they exit the sequence. No accidentally sending a “last ping” to someone who already booked a meeting.

The cost reality

The sequencer itself is included on all paid Origami plans. You only pay for the enrichment credits you used to build the list. If you’re on the free plan, you get 1,000 credits (no credit card) — enough to enrich a small batch and test the sequence. Once you’re past testing, the $29/month plan gives you enough credits for consistent outreach.

Response rates to expect

Across campaigns I’ve run targeting solo technical founders with this exact sequence, I typically see:

• Connection acceptance: 22–30% (higher when the note includes a specific tool mention).
• Reply rate on Day 3: 8–12% of connected prospects. Most replies are genuine — they’re answering the “what’s stealing your time” question honestly.
• Meeting booked from Day 7: 3–5% of connected prospects. That’s 4–7 meetings from a list of 200 refined contacts. Not massive volume, but extremely high intent.

When to iterate on messaging vs. the list

If your connection acceptance is below 15%, something is off with the Day 1 note. Check your personalization — are you naming a real detail, or just the company name? Are you accidentally targeting founders who’ve just raised a Series A and now have a bigger team? Tighten the note or tighten the list filters.

If you’re getting connections but zero replies on Day 3, the question isn’t resonating. Solo technical founders might not feel the pain of user docs or cloud costs if they’re still pre-revenue. Try a different angle: “What’s the one feature request from users that you know you should build but can’t find the time for?”

If Day 7 gets no meetings, your value prop might be too vague. Make sure the soft close references a concrete outcome — “cut infrastructure costs,” “shorten onboarding time,” “auto-generate SDK docs” — something they’ve directly told you they care about in earlier replies or that you can infer from their tool’s landing page.

Pro tip: Link the parent post for list-building

If you’re reading this before you’ve built the list, stop and go to the how to build a list of Solo Technical Founders at Funded Dev Tools Startups guide. You’ll need the list in Origami first, then you can come right back here and launch this sequence in under 10 minutes.