Marketing & Growth

How to run a linkedin outreach campaign as Small Marketing Teams

Marketing & GrowthFor Small Marketing Teams3 apps12 steps~24 min to set up

Your three-person team runs LinkedIn outreach the slow way: one person manually searches Sales Navigator, copies prospects into a spreadsheet, drafts 40 connection requests by hand, and follows up in a separate tab while trying to remember who already accepted. HubSpot holds your CRM data but LinkedIn doesn't talk to it, so you're reconciling two systems every Friday. Response rates are a mystery because nobody has time to build the tracking layer. You know LinkedIn is where your buyers are — SaaS decision-makers, ops leaders, mid-market CMOs — but the manual process tops out at maybe 20 outbound touches a week before it becomes someone's full-time job.

Build this on Starch → See the apps used

Marketing & GrowthFor Small Marketing Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

An automated LinkedIn outreach workflow that reviews incoming connection requests against your ICP, sends targeted outbound invites, and comments on relevant posts — all running on human-paced browser automation so your account stays safe

A lightweight CRM surface that syncs accepted connections and reply threads back to HubSpot so your pipeline data stays in one place instead of three spreadsheets

A weekly outreach report showing accepted rate, reply rate, and meetings booked that you can drop straight into your Monday pipeline review without rebuilding it by hand

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

LinkedIn Automation CRM Sales Agent CRM

Data sources & config

LinkedIn Automation runs through browser automation on your behalf — no LinkedIn API needed, activity looks human-paced. Starch syncs your HubSpot data on a schedule so accepted connections and deal stages are always current. Gmail is also synced on a schedule so reply threads appear in your CRM contact view automatically. Customer.io and Mailchimp are reachable from Starch's integration catalog and can be queried live if you want to cross-reference which LinkedIn contacts are already in a nurture sequence.

Prompts to copy

Review every incoming LinkedIn connection request. Accept anyone who is a VP of Marketing, Head of Demand Gen, or Marketing Director at a B2B SaaS company with 50–500 employees. Decline everyone else, and log accepted connections with their title and company into my CRM.

Send outbound LinkedIn connection requests to people who match this ICP: B2B SaaS companies, 50–300 employees, job titles include Demand Gen Manager, VP Marketing, Growth Lead, or CMO. Use a short personalized note referencing their company name and a recent post if available. Cap at 25 invites per day.

Every morning, leave one thoughtful comment on a post from a marketing leader or operator founder in my LinkedIn feed. The comment should add a concrete point, not just agree. Log which posts I commented on and the text of each comment.

Build me a weekly outreach summary app that shows: total invites sent, acceptance rate, replies received, and meetings booked from LinkedIn — pulled from my CRM data. I want this in a simple table I can paste into our Monday Slack standup.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect LinkedIn through Starch's LinkedIn Automation app — this runs through browser automation on your account, so no API key, no OAuth dance with LinkedIn's restrictive developer portal.

2 Starch syncs your HubSpot contacts and deals on a schedule so the CRM surface always reflects your current pipeline; accepted LinkedIn connections land in the same contact record.

3 Define your ICP in plain English inside the LinkedIn Automation app — job titles, company size, industry, seniority — and set your daily invite cap (start at 20–25 to stay under LinkedIn's limits).

4 Turn on inbound request filtering: describe which profiles to accept and which to ignore, and Starch reviews the queue each morning and takes action automatically.

5 Set up the morning comment routine — tell Starch to scan your feed for posts from marketing leaders and founders, pick one, and leave a comment that adds something concrete. This builds top-of-funnel visibility without you spending 30 minutes scrolling.

6 As connections accept your invites, Starch logs them into your CRM with name, title, company, and LinkedIn URL. If a contact already exists in HubSpot, it enriches that record instead of creating a duplicate.

7 Build a follow-up sequence: tell Starch to send a short message to anyone who accepted an invite but hasn't replied in 5 days — something like 'Noticed you're working on demand gen at [company], happy to share what's worked for us on [topic] if useful.'

8 Wire Gmail into the CRM so that when a LinkedIn prospect emails you after connecting, the thread is visible on their contact record next to their LinkedIn activity — no manual linking.

9 Build the weekly report app: tell Starch 'every Monday at 8am, pull last week's LinkedIn outreach stats from my CRM and give me a summary table — invites sent, accepts, replies, meetings booked — and Slack it to the #marketing channel.'

10 After four weeks, ask Starch to analyze which ICP segments have the highest accept-to-reply conversion and update your targeting criteria accordingly — this is a natural-language query against your own CRM data.

11 If you run paid LinkedIn Ads alongside organic outreach, connect LinkedIn Ads from Starch's integration catalog and build a view that shows organic connection activity alongside paid impression and click data for the same target audience segments.

12 Share the weekly report app template with your team so the content person running thought leadership posts and the demand gen lead tracking MQLs are both looking at the same outreach numbers — one source, no spreadsheet reconciliation.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q1 2026 Mid-Market Push — March Week 3

Sample numbers from a real run

Invites sent (week)	125
Accepted connections	41
Acceptance rate	33
Replies received	9
Meetings booked from LinkedIn	3
Hours saved vs. manual process	6

In week three of March, the LinkedIn Automation app sent 125 outbound connection requests to demand gen and marketing ops leaders at B2B SaaS companies with 50–300 employees — all running through browser automation at human-paced intervals. 41 accepted (33%), which is about double what the team was hitting manually because the ICP filter meant every invite was actually relevant. Starch logged all 41 into HubSpot automatically, enriching 12 records that already existed in the CRM with updated titles and LinkedIn URLs. Of the 9 replies, 3 converted to intro calls after Starch sent a follow-up message to the 28 non-responders on day 5. The Monday Slack report dropped into #marketing at 8:02am with the full table — nobody had to pull it together. The content lead used the same data to brief the CEO on why LinkedIn was outperforming Meta Ads on a cost-per-meeting basis that week.

Measurement

How you'll know it's working

LinkedIn invite acceptance rate (target: 25–35% for a well-defined ICP)

Accept-to-reply conversion rate (how many accepted connections turn into actual conversations)

Meetings booked from LinkedIn outreach per week

Time from connection accepted to first reply (proxy for message quality and follow-up timing)

LinkedIn-sourced MQLs as a percentage of total MQL volume (tied back to HubSpot deal stage)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Expandi or Dux-Soup

Dedicated LinkedIn automation tools with more granular sequencing options, but they don't connect to your HubSpot CRM or Gmail, so you're still reconciling data manually and can't build the attribution view or the weekly pipeline report in the same place.

Sales Navigator + manual outreach

Better search filters and lead recommendations, but every touch is human-hours — realistic cap is 20–30 invites a week before it becomes someone's primary job, and there's no automated logging back to HubSpot.

HubSpot Sequences + LinkedIn Sales Navigator integration

Native HubSpot integration keeps everything in one CRM, but the LinkedIn steps in sequences still require manual sends unless you're on an Enterprise plan, and browser automation for comments or inbound filtering isn't part of the product.

Zapier + LinkedIn + HubSpot

Can automate some LinkedIn-to-HubSpot data flows, but LinkedIn's API restrictions mean most outreach actions (sending invites, leaving comments, reviewing requests) still can't be triggered via API — you'd need browser automation anyway, which Zapier doesn't provide.

On Starch RECOMMENDED

One platform — linkedin automation, crm, sales agent crm all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Will this get my LinkedIn account flagged or restricted?

LinkedIn's restrictions target API-based automation that fires actions faster than a human could. Starch's LinkedIn Automation runs through browser automation — activity looks like a normal person using LinkedIn at a normal pace. Keep daily invite volume under 25–30 and you're in the same range as an active human user. That said, no tool can guarantee LinkedIn won't change its policies, so don't treat this as a 'set and forget forever' system — review your account health monthly.

Does Starch store my LinkedIn credentials?

Browser automation works by controlling a browser session on your behalf — similar to how you'd use LinkedIn in a tab. Starch doesn't store your password in plain text; the session is managed through your connected account. If you're concerned about credential handling, this is worth a direct conversation with the Starch team before you set it up.

We use HubSpot as our CRM. Will LinkedIn contacts sync there automatically or do I have to export them?

Starch syncs your HubSpot data on a schedule and logs accepted LinkedIn connections into your CRM surface. If a contact already exists in HubSpot, Starch enriches that record. You can then build an automation that pushes net-new contacts from Starch's CRM back into HubSpot — describe what you want and the agent builds the sync. No manual CSV exports.

Is Starch SOC 2 certified? Our company has a security review process.

Not yet — Starch is not currently SOC 2 Type II certified. If your company requires SOC 2 as a hard gate for new tools, that's worth knowing upfront. It's on the roadmap.

We already pay for Mailchimp for nurture and Customer.io for lifecycle. Can we cross-reference who's in those systems with LinkedIn outreach contacts?

Yes. Connect Mailchimp or Customer.io from Starch's integration catalog — the agent queries them live when your apps run. You can build a view that shows which LinkedIn contacts are already in an active nurture sequence so your outreach team isn't touching someone who's mid-drip. Describe what you want to see and Starch builds the view.

Can Starch write the LinkedIn connection messages for us, or do we have to write the templates ourselves?

Both. You can give Starch a template with variables (like company name or a recent post reference) and it fills them in, or you can describe your ICP and tone and tell Starch to generate the message text. The output is always reviewable before anything goes out — you're not handing over message approval entirely unless you want to.

What if the prospect isn't on LinkedIn but we want to reach them via email instead?

Gmail is synced on a schedule in Starch, so you can build an outreach workflow that starts on LinkedIn and falls back to a Gmail-drafted follow-up if there's no LinkedIn connection after a set number of days. Describe the sequence — 'if they haven't accepted on LinkedIn in 7 days, draft a cold email to their work address if I have it in HubSpot' — and Starch assembles the automation.