Technical founders avoid LinkedIn for a defensible reason: most of what succeeds there is performative in a way that is genuinely embarrassing to produce. The broetry, the humblebrag origin story, the thread about what a taxi driver taught you about resilience.
You do not have to do any of that, and the advice to “just be authentic” is useless because it does not say what to actually do.
So here is the specific version, built around the asset you already have and most salespeople do not: you can talk about how the thing works, in detail, truthfully.
Your profile is a landing page, not a CV
Before any outreach, fix the profile, because the profile is read before any reply is sent, and a weak one caps your reply rate regardless of what the message says.
Most engineer profiles read as a job application: a list of employers and technologies. For outreach, that is the wrong document. The person reading it is deciding one thing: does this person understand my problem well enough to be worth answering?
Four changes, in order of impact:
The headline says what you do for whom. Not “Founder & CTO”. Something closer to “Building deliverability infrastructure for teams running cold email at scale”. It is the only part guaranteed to be read.
The About section opens with the problem, not your history. Two sentences on the problem you work on, one on why you work on it, one on who you help. Your career path is not the hook; the problem is.
Pin one thing that demonstrates competence. A technical write-up, a benchmark, a tool, a teardown. One artifact proving you know the subject does more than any amount of description.
A photograph that looks like you on a working day. Not a studio portrait, not a conference stage. This is a small thing and it affects acceptance rates.
Thirty minutes. It compounds across every message you send afterwards.
Commenting beats posting
The most useful thing in this post, and the thing that lets you skip content creation entirely.
Posting requires an audience you do not have. Commenting borrows one. A substantive comment on a post by someone with 20,000 followers in your niche is seen by more of your market than anything you publish, and it costs five minutes rather than an afternoon.
More importantly, it suits what you are good at. The comment that performs is the one that adds specific technical information, a correction, a caveat, a number, an explanation of the mechanism. That is the register you already write in.
How to do it:
- Find five to ten practitioners who post consistently about your problem. Practitioners, not personalities, read their comment sections and check the job titles. Choosing whose audience to watch covers the selection criteria.
- Comment on two or three posts a week. Add something that was not in the post.
- Never pitch. The comment is not an advert and treating it as one undoes the benefit.
Three months of this produces recognition in your niche without a single post of your own. People will start replying to your messages because they have seen your name attached to something useful.
If you do post, post the thing you would have written anyway: what broke and how you fixed it, a number you measured, a thing that is commonly believed and is wrong. Technical write-ups travel further than people expect, because almost nobody is producing them.
The message, written as an engineer
Your advantage in a cold message is precision. Use it.
What works:
- Mechanism over outcome. “We rotate sending across mailboxes and throttle per-domain so a single provider’s limits don’t gate the whole campaign” tells a technical buyer more than “improve your deliverability”.
- A number with its source. Not “10x faster”, the actual figure and what it was measured against.
- Stated limitations. “This won’t help if your problem is list quality” raises credibility rather than lowering it. Sales instincts say otherwise. Sales instincts are wrong with this audience.
- One specific thing about them. The system they wrote about, the architecture decision they described, the problem their job posting implies.
What does not work:
- A paragraph of specification. Precision is not length.
- Jargon from your domain they have no reason to know.
- Assuming they share your technical values. Plenty of buyers are technical and still care mainly about the commercial outcome.
Length: four to six sentences. The temptation is to explain properly. Do not, the reply is where you explain properly, and getting the reply is the only job of the first message.
The sequence
Short, and in this order.
1. View their profile. They often see it. Costs nothing.
2. Connection request with no note, or a one-line note. Long requests reduce acceptance. If your profile is fixed, the profile does the work.
3. After acceptance, wait a day or two. A message arriving within a minute of acceptance is obviously automated.
4. The message. Four to six sentences, mechanism-first, one specific thing about them, an easy out.
5. One follow-up, five days later, adding new information rather than repeating. A link to something you wrote on the subject works well here, which is where the commenting and writing pays off.
6. Stop. Two messages. A third reads as pressure and a fourth gets you reported, which carries account consequences.
The limits you must respect
The part where engineers get into trouble, because the instinct to automate is correct in general and dangerous here.
Roughly 100 connection requests a week per account is the sustainable figure. The cap is not a published number you can optimise against, enforcement is behavioural, driven by acceptance rate, how many of your messages go unanswered, reports from recipients, and whether your session patterns look like a person.
Two specific traps for technically capable people:
Writing your own automation against the unofficial endpoints. Entirely possible and the fastest route to a restricted account, because a hand-rolled script does not reproduce the session consistency and IP stability that platform-based tools maintain. You are not optimising a rate limit; you are failing a behavioural check.
Running a browser extension on your own machine, at scale. Fine at low volume. At higher volume the pattern is detectable and the account at risk is the one carrying your name and your network.
What actually gets accounts restricted covers the enforcement signals. The practical summary: stay under the limits, keep acceptance rate high by only requesting people with a plausible reason to accept, and use something that manages sessions properly rather than something you wrote on a Saturday.
The asymmetric risk: a restricted account costs you your network, your live conversations and your profile’s history. The upside of exceeding the limits is a few dozen extra requests a week. That trade is bad.
A weekly rhythm
Two hours, which is what a technical founder can sustain.
- 45 minutes: comment on two or three posts, properly
- 30 minutes: 20–25 connection requests to people with a specific reason to accept
- 30 minutes: messages to people who accepted this week
- 15 minutes: replies
Scale by adding accounts and people, not by raising per-account volume. The five-hour outbound week covers how this sits alongside email.
What to measure
Three numbers, monthly.
Acceptance rate. Above 30% is healthy. Below 20% means you are requesting people with no reason to accept, which degrades the account as well as wasting the requests.
Reply rate on messages after acceptance. This is your message quality. If acceptance is good and replies are poor, the problem is the four to six sentences.
Conversations per week. The only output that matters. Everything else is an input.
Do not track followers, impressions or profile views. They are not correlated with conversations and chasing them is how you end up writing the content you did not want to write.
Build a motion you can hand off
The outreach process you build now becomes the foundation for your first sales hires. Document what works (the targeting, the sequences, the messaging) so that when you bring on an SDR, you’re handing them a proven system rather than starting from scratch. Founder-led outreach done well isn’t just early pipeline; it’s your future sales playbook.
The short version
You do not need to become a content creator. Fix the profile so it reads as a landing page rather than a CV, then comment substantively on two or three posts a week by practitioners in your niche, it borrows an audience instead of building one, and it suits how you already write.
Write messages like an engineer: mechanism over outcome, real numbers with their source, stated limitations, four to six sentences. The reply is where you explain properly.
View, request, wait, message, one follow-up, stop. Two messages total.
Stay under about 100 requests a week per account, keep acceptance above 30%, and do not write your own automation against the unofficial endpoints, the enforcement is behavioural, and the account at risk carries your name.
Next: the five-hour outbound week, or what gets LinkedIn accounts restricted.
Frequently asked questions
Can you use LinkedIn for outreach without posting content?
Yes. Commenting substantively on posts by practitioners in your niche borrows their audience rather than building your own, takes a few minutes per comment, and produces recognition in your market within a few months without publishing anything of your own.
What should a technical founder’s cold LinkedIn message say?
Explain the mechanism rather than the outcome, include a real number with what it was measured against, state where your product does not help, and reference one specific thing about the recipient. Four to six sentences, with the detail saved for the reply.
How many LinkedIn connection requests can you send per week?
Around 100 per account is the sustainable figure, and enforcement is behavioural rather than a fixed cap, acceptance rate, unanswered messages, recipient reports and session consistency all contribute. Acceptance rate above 30% is the number to protect.
Is it safe to build your own LinkedIn automation?
No. Hand-written scripts against unofficial endpoints fail the behavioural checks that matter, session consistency and IP stability, and the account at risk carries your name, your network and your live conversations.
Is LinkedIn outreach good for startups?
Yes, it’s one of the most cost-effective ways for early-stage startups to land first customers, especially when the founder leads it. It needs little budget and produces direct conversations with your ICP.
Should founders do outreach themselves?
Early on, yes. A founder’s message carries authenticity and weight, and the conversations double as product and market learning. Automate the logistics so it doesn’t consume your week.