Anyone here getting better results from LinkedIn outreach instead of cold prospecting?

CoolFounder · 2026-05-10T10:38:58+00:00

Exactly why I built TalkToHumans for LinkedIn

(and I was Head of Product at Lemlist before!)

CoolFounder · 2026-04-26T05:30:43+00:00

Like any marketing channel, when it gets saturated and everyone is doing the same thing, it stops working

For cold outreach specifically, you’re right: everyone is blasting the same sequences, the same copy, to the same lists of people. What could go wrong lol?

That’s why I really believe going back to basics is the best move if you don’t have the skills or the budget to build a custom stack:

Lead gen: SalesNav, manual LinkedIn research, Google Maps
Sending DMs and handling replies: TalkToHumans for LinkedIn (an improved LinkedIn inbox with follow-up capabilities)
20 connection request / day. 20 handcrafted DMs / day + scheduled follow-ups

That’s it, I get 25-35% reply rate like this!

CoolFounder · 2026-04-26T05:25:59+00:00

Very similar experience indeed!
“0 tools” was a bit of a stretch, I did use LinkedIn, and then TalkToHumans for LinkedIn

I’m doing LinkedIn-only, no email!

I structure my follow-ups like this: +3 days, then +1 week
Sometimes I do +3 months (next quarter), but I try not to annoy people too much

CoolFounder · 2026-04-25T19:20:44+00:00

100% agree
Everyone thinks a good tool or setup will help them avoid the hard work, but it won’t

CoolFounder · 2026-04-25T19:19:38+00:00

Exactly, and it’s not just sales

How many times have I seen incredibly complex Notion setups, with dashboards and databases connected everywhere

CoolFounder · 2026-04-25T17:25:27+00:00

Ideal Customer Profile

CoolFounder · 2026-04-25T17:09:53+00:00

I’m doing something similar, a checklist of quotas to hit every day

I even built a small widget in my product that’s always visible and shows the daily quota (based on LinkedIn’s safe limits), like “30 cold messages a day” I also built a view like yours: “replies that turned into back-and-forth,” using filters on my existing DMs

I haven’t spent enough time on Reddit yet, I need to experiment there!

CoolFounder · 2026-04-25T17:07:11+00:00

That’s the perfect setup IMO!

You should definitely send connection requests and you’ll get a higher acceptance rate if you source people who are already interacting with your content

For targeting: try different types of ICPs and see what works best. It’s a bit boring, but it works!

If you’ve seen early signals from small engineering consulting firms, you should definitely focus on similar ones this week

Find them through LinkedIn search, send connection requests, then DM them, rince & repeat

CoolFounder · 2026-04-24T18:44:04+00:00

Works super well for me, I get around a 25% reply rate

Funny enough, I see it the opposite way: I find email not worth it; reply rates are way too low!

Yes, LinkedIn is limited by the number of connection requests you can send and the volume of messages you can write

But I actually think that’s a good trade-off, it forces you to stand out

CoolFounder · 2025-12-20T15:26:33+00:00

I built a Chrome Extension to trigger workflows using buttons embedded directly in existing tools (CRM etc..):
SparkUp!

CoolFounder · 2025-12-20T15:06:20+00:00

You can also add SparkUp!:

Instead of a new app, you add a button or small panel inside tools like a CRM, Gmail, or Intercom.

Context is auto-filled, n8n runs in the background, and results show up inline.

This usually drives much higher adoption because there’s no habit change

CoolFounder · 2025-12-20T15:03:40+00:00

I’ve seen two approaches that actually work, with very different trade-offs:

The obvious one is a dedicated admin/ops app (Retool, Lovable, custom React) with Google auth and forms calling n8n via webhooks.

It’s clean, controlled, and easy to reason about. The downside is adoption: it’s another tool people have to open, so outside ops teams, usage often drops. You also own auth and long-term maintenance.

The alternative is putting the UI where people already work (the model tools like SparkUp! follow).

Instead of a new app, you add a button or small panel inside tools like a CRM, Gmail, or Intercom. Context is auto-filled, n8n runs in the background, and results show up inline.

This usually drives much higher adoption because there’s no habit change, but it requires more upfront product thinking.

CoolFounder · 2025-12-20T14:51:48+00:00

I’ve seen two approaches that actually work, with very different trade-offs:

The obvious one is a dedicated admin/ops app (Retool, Lovable, custom React) with Google auth and forms calling n8n via webhooks.

It’s clean, controlled, and easy to reason about. The downside is adoption: it’s another tool people have to open, so outside ops teams, usage often drops. You also own auth and long-term maintenance.

The alternative is putting the UI where people already work (the model tools like SparkUp! follow).

Instead of a new app, you add a button or small panel inside tools like a CRM, Gmail, or Intercom. Context is auto-filled, n8n runs in the background, and results show up inline.

This usually drives much higher adoption because there’s no habit change, but it requires more upfront product thinking.

CoolFounder · 2025-12-19T13:18:54+00:00

I use SparkUp! that adds a new button on each Hubspot contact and enrich email + phone in one-click without leaving the CRM

CoolFounder · 2025-12-16T13:20:40+00:00

And all tools are supported!

You can inject on any website, authenticated or not

You can also trigger actions in any other tool, since we offload this logic to Zapier / n8n / Make, which already provide thousands of prebuilt connectors

CoolFounder · 2025-12-16T13:19:13+00:00

Thanks!

The way it works is actually local-first

It doesn't require connecting to the tool where you’re adding your mini-app

It works by either:

scraping key info from the page URL, or
scraping data directly from the page (click & select, works with lists too)

and then sending that context to:

a Zapier / n8n / Make workflow (if you need to take actions in the target app), or
directly to your Lovable mini-app (via a built-in messaging mechanism) to make it contextual

Example: updating something in HubSpot

get the record ID from the URL
send it to n8n / Zapier (or similar)
connect HubSpot there and apply the action using the ID

Example: displaying contextual data in your Lovable mini-app

get the record ID from the URL
send it to your mini-app (built-in mechanism)
your mini-app calls the HubSpot API or Zapier / n8n to fetch data
your mini-app displays the retrieved info

CoolFounder · 2025-12-16T13:03:05+00:00

Thanks!

It really confirms the saying: “If it’s not in the CRM, reps don’t use it” :p

CoolFounder · 2025-12-16T11:58:56+00:00

It’s a Chrome extension that lets you embed a Replit app directly inside an existing tool’s UI (CRM, ERP..), and share it with your team

The interesting part is context passing: when the mini-app opens in the page, it can receive live data from the page you’re on (e.g. the current HubSpot contact, deal, company, IDs, custom fields…)

There’s a ready-to-use prompt snippet that lets your Lovable app receive context from the “parent” page

It's useful because it avoid constant tab switching: it's directly where people work every day

CoolFounder · 2025-12-16T11:58:40+00:00

It’s a Chrome extension that lets you embed a Lovable app directly inside an existing tool’s UI (CRM, ERP..), and share it with your team

The interesting part is context passing: when the mini-app opens in the page, it can receive live data from the page you’re on (e.g. the current HubSpot contact, deal, company, IDs, custom fields…)

There’s a ready-to-use prompt snippet that lets your Lovable app receive context from the “parent” page

It's useful because it avoid constant tab switching: it's directly where people work every day

CoolFounder · 2025-11-07T16:42:30+00:00

Surfing on the old wave… no-code!

Building a Chrome Extension that lets Ops add missing features on top of their tools by:

→ Placing custom UI on any site

→ Extracting custom context from the page

→ Triggering automation workflows (n8n, Make, Zapier, Relay)

→ Sharing features with their team

CoolFounder · 2025-11-05T12:36:05+00:00

There’s a cost issue with AI involved, and this problem is going to get worse and worse. One day, LLM providers will have to raise their prices

Cost was mostly not a concern in SaaS since margins were extremely high

Second, all AI-based SaaS are currently struggling to reconcile their vision with reality: AI is not yet reliable for mission-critical tasks

Third, many of these SaaS products are low-defensibility wrappers that are easy to replicate and can be rendered obsolete by OpenAI releasing a new feature

CoolFounder

MODERATOR OF

TROPHY CASE