A market warming up to two people: each in coral, the people who have come to know them in peach round a post, and a meeting ringed. An example.
Help people stop chasing.
Most outreach software makes cold faster. We’re building the opposite. No open roles right now — but the team will grow. If the work looks interesting, get in touch early.
Careers at LinkedReach. Last updated: 10 May 2026
Most outreach software makes cold faster
Most outreach software makes cold faster: more messages, sent quicker, to more strangers. Buyers learn to ignore them, and the people sending them are left with the silence.
We think that’s the wrong problem. People buy from people they know, so the real work is making someone known before they ever ask.
Judgement. That’s harder to build than a faster sender. It takes judgement about who to talk to.
A voice. Writing that sounds like one particular person, not a template with their name in it.
Patience. A careful human pace, every day, for every account.
People it found today Example
Head of OperationsLogistics94
FounderB2B software88
Sales DirectorManufacturing81
Marketing studentBelow your bar of 6041
What we’re building.
An AI agent for LinkedIn that finds a person’s buyers, warms them up in that person’s voice and books the meetings, at a careful person’s pace.
AI that does real work. Not fill-in-the-blanks. It scores people against what someone sells, and writes about the post or the person in front of it, in its user’s own voice.
Real workers, not serverless. Long-running workers that keep a person’s pace, under limits nobody can override. The codebase is TypeScript end to end.
The inbox comes first. Replies are a first-class part of the product, not an afterthought: answered in the sender’s voice, with the hard ones handed back to a person.
How to get in touch.
No public job board yet. If you’re an engineer, designer, or operator who wants to help build this — email hello@linkedreach.ai, tell us what you’ve built, and we’ll talk.
Write to hello@linkedreach.ai, whether you’re an engineer, a designer or an operator.
Show
Tell us what you’ve built: the work you’re proudest of, in your own words, with links if you have them.
Talk
That’s the whole process for now: an email, and then a conversation.
Dana ReyesVP Operations · posted this morningExample
The handover note is where most shifts go wrong. Who owns it on your team?
YouComment
Give the note one owner per shift, and make it the first thing the next lead reads. When everyone owns it, nobody does.
How we work.
Small team. Remote. Async by default, with a weekly sync.
We ship fast, and write it down. We ship fast, and when something goes wrong we write a proper post-mortem, so the next person can see what happened and why.
Small enough to rebuild. We keep the surface area small enough that any engineer can rebuild any component if they have to.
Careful with other people’s names. Our users’ names are on every message, so their safety limits come first, and nobody can override them.
Dana Reyes · 23:12 Example
Dana: Thanks for the note on handovers. Is this something you could show me properly?
Your answer, drafted: Happy to. I have Thursday at 9:30 or 14:00, fifteen minutes.
Dana: Thursday at 9:30 works.
Meeting bookedThursday 9:30–9:45 · Google Meet
This week’s briefing Example
The best thing that happened: Dana Reyes booked a call for Thursday.
Replies with interest6
Meetings booked2
What they could be worthup to £10,000
At about £5,000 a customer, the figure they set.
This is what the work is for.
It’s 23:12. Someone who uses LinkedReach is asleep, and a buyer who already knows their name writes back. By 08:05 the meeting is booked, and nobody was chased.
Tell us what you’ve built.
If you’re an engineer, designer or operator who wants to help build this, we’d like to hear from you.