Marketing & Growth

How to run a linkedin outreach campaign as Small RevOps Teams

Marketing & GrowthFor Small RevOps Teams3 apps11 steps~22 min to set up

You're a two-person RevOps team supporting 30 reps, and LinkedIn outreach is a blind spot in your attribution model. Reps are running their own campaigns in Sales Navigator, sequences are firing in Apollo, and you have no unified view of which touches are actually moving deals. You manually chase reps for LinkedIn activity data that never makes it into HubSpot. When the CRO asks 'how many LinkedIn touchpoints on Q2 pipeline?', you spend 40 minutes piecing together a number you don't fully trust. You need LinkedIn outreach running systematically, feeding back into your pipeline data, without adding a third tool nobody will log into.

Build this on Starch → See the apps used

Marketing & GrowthFor Small RevOps Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

A LinkedIn Automation app that sends targeted outbound connection requests and follow-up messages to ICP accounts matching your Apollo contact lists — running through browser automation so it looks like normal human activity

A connected view that ties LinkedIn touch activity back to HubSpot deal stages and Apollo sequence data, so you can answer attribution questions without manually stitching CSVs

An automated weekly summary delivered to your Slack channel that shows new connections made, reply rates, and which accounts crossed from 'LinkedIn cold' to 'email sequence active' that week

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 Sales Agent CRM CRM

Data sources & config

Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and owners refresh automatically. Apollo is connected from Starch's integration catalog and queried live when the attribution dashboard or CRM view needs sequence and contact data. LinkedIn outreach runs through browser automation on your behalf — no LinkedIn API needed. Slack is available via Starch's integration catalog to push the weekly summary to your ops channel. Google Sheets can be connected from the integration catalog as a lightweight log target for connection activity.

Prompts to copy

Build a LinkedIn Automation that sends connection requests to VP of Supply Chain and Head of Logistics titles at companies with 100-500 employees in the manufacturing and 3PL sectors. Use this message: 'Hi [first name], I work with [our company] — we help teams like yours cut manual ops overhead. Would love to connect.' Run 15-20 invites per day, Monday through Friday, and log each new connection with the person's name, title, company, and connection date to a Google Sheet.

After someone accepts a connection, wait 3 days and send a follow-up message: 'Thanks for connecting — happy to share how we've been helping RevOps teams at similar companies reduce reporting time. Worth a 15-minute call?' Flag anyone who replies as 'LinkedIn Warm' and add them to a list I can push into Apollo for sequence enrollment.

Build me a pipeline attribution dashboard that pulls HubSpot deal data on a scheduled sync and Apollo contact data from the integration catalog, and adds a 'LinkedIn touch' column based on the connection log I feed in. Show me, by deal stage, how many open opportunities had a LinkedIn touch before entering the pipeline.

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

Walkthrough

Step-by-step

1 Connect HubSpot: Starch syncs your contacts, companies, deals, and owners on a schedule — this becomes the backbone your attribution dashboard reads from.

2 Connect Apollo from Starch's integration catalog: the agent queries your contact and sequence data live when building the attribution view or cross-referencing ICP filters.

3 Install the LinkedIn Automation app from the Starch App Store and describe your ICP in plain English — job titles, company size, industry, geography. Starch automates the outbound connection requests through your browser at human-paced intervals.

4 Set your daily send cap (15-20 requests is the safe range) and write your connection request message template. Starch fills in first name and company from the target's public LinkedIn profile.

5 Configure a 3-day follow-up trigger: once a connection is accepted, Starch automatically sends your follow-up note through browser automation and logs the reply status.

6 Build a connection activity log: tell Starch 'log every new LinkedIn connection — name, title, company, connection date, reply status — to a Google Sheet I can reference.' This becomes your attribution bridge.

7 Tell Starch to build a pipeline attribution dashboard: 'Pull HubSpot deal data and Apollo contact data, join on email or company domain, and flag deals where a LinkedIn connection exists. Break it down by current deal stage.' Starch builds the view from your connected data.

8 Set up a weekly Slack automation: 'Every Monday at 8am, pull last week's LinkedIn connection log, count new connections, accepted requests, and replies. Cross-reference with HubSpot to show how many are in active pipeline. Post a summary to #revops-weekly.'

9 Wire a trigger so that when a LinkedIn contact replies, Starch updates their status in the connection log and optionally adds them to an Apollo sequence — describe this in natural language and Starch builds the action chain.

10 Run for two weeks, then ask Starch: 'Show me the conversion rate from LinkedIn connection to first email reply, broken down by job title and company size.' Use this to tune your ICP filter and message copy.

11 Share the attribution dashboard link with the CRO before the next forecast call — pipeline touches now include LinkedIn activity without you manually entering anything.

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

Q2 2026 Mid-Market Push — Manufacturing Vertical

Sample numbers from a real run

LinkedIn connection requests sent (6 weeks)	540
Accepted connections	189
Follow-up messages sent	189
Replies received	41
Contacts added to Apollo sequence from LinkedIn	38
HubSpot deals with LinkedIn touch in last 90 days	14
Pipeline value tied to LinkedIn-touched accounts ($)	620,000

Your team is preparing for the Q2 forecast review and the CRO wants to know whether the LinkedIn push your AE lead ran in January is showing up in pipeline. Before Starch, this answer didn't exist — LinkedIn activity lived in the AE's browser and never touched HubSpot. With Starch running the LinkedIn Automation for 6 weeks, you sent 540 connection requests to VP Supply Chain and Head of Logistics titles at 100-500-person manufacturers. 189 accepted (35% acceptance rate), 41 replied to the follow-up, and 38 were enrolled in an Apollo sequence. When you run your attribution dashboard, it shows 14 open HubSpot deals where the contact also appears in your LinkedIn connection log — representing $620k in pipeline. That number took you 2 minutes to pull, not 40, because HubSpot syncs automatically, Apollo is queried live, and the LinkedIn log feeds in from the automation. You put that slide in the forecast deck in under 10 minutes.

Measurement

How you'll know it's working

LinkedIn connection acceptance rate by ICP segment (title, company size, industry)

LinkedIn-to-pipeline conversion: percentage of accepted connections that appear in HubSpot as active deals within 90 days

Multi-touch attribution: deal count and pipeline value where LinkedIn touch preceded email sequence enrollment

Sequence enrollment velocity: days between LinkedIn connection acceptance and Apollo sequence start

RevOps ticket deflection: reduction in ad-hoc 'can you pull me a list' requests once the attribution dashboard is self-serve

Comparison

What this replaces

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

Phantombuster + manual HubSpot import

Phantombuster can scrape LinkedIn connections, but you're back to exporting CSVs and manually importing into HubSpot — the attribution join never happens automatically, and you're doing the stitching work Starch does for you.

Dux-Soup or Expandi standalone

These run LinkedIn sequences but don't connect to your CRM or Apollo data, so you still have no attribution view and the RevOps reporting problem is completely unsolved.

HubSpot Sales Hub LinkedIn integration

HubSpot's native LinkedIn integration requires LinkedIn Sales Navigator at $1,000+/seat/year and still doesn't run automated outreach — it's an enrichment layer, not a campaign runner.

Apollo sequences only (no LinkedIn layer)

Apollo handles email sequences well and Starch connects to it, but Apollo's LinkedIn steps require manual execution — Starch automates those browser actions Apollo leaves to the rep.

On Starch RECOMMENDED

One platform — linkedin automation, sales agent crm, 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 our LinkedIn accounts flagged or restricted?

LinkedIn Automation runs through browser automation on your behalf — Starch controls a real browser session that logs in as you and performs actions at human-paced intervals, the same way you would manually. It doesn't hit LinkedIn's API or use scraping patterns that trigger their bot detection. That said, no tool can guarantee zero risk from LinkedIn's terms of service enforcement. Keep daily send volumes conservative (15-20 invites/day is the safe range most practitioners use) and you're operating within normal human activity patterns.

How does the LinkedIn data actually get into HubSpot — does Starch write back to HubSpot?

Starch reads from HubSpot on a scheduled sync — it doesn't write back to HubSpot today. The attribution join happens inside Starch: your HubSpot deal and contact data syncs automatically, your LinkedIn connection log is maintained by the automation, and Starch builds the combined view. The output is a dashboard and a Slack summary your team reads from Starch, not a HubSpot field update. If you need the LinkedIn touch flag inside HubSpot itself, you'd export from Starch and import manually — or describe an automation and Starch can build a workflow that pushes data via HubSpot's API through the integration catalog.

We use Salesforce, not HubSpot. Does this still work?

Yes. Connect Salesforce from Starch's integration catalog — the agent queries your deals, contacts, and opportunities live when your attribution dashboard runs. The LinkedIn automation and attribution logic work the same way; the only difference is Salesforce data is queried live rather than stored on a schedule the way HubSpot is. For most RevOps reporting use cases this works fine.

Can Starch enroll LinkedIn replies directly into Apollo sequences without us doing it manually?

Yes. Describe the trigger in natural language: 'When a LinkedIn connection replies to our follow-up message, add their email to this Apollo sequence and mark them as LinkedIn Warm in the connection log.' Starch builds an automation that connects Apollo from the integration catalog, queries it live when the trigger fires, and enrolls the contact. You set it up once; it runs on every qualifying reply.

Is Starch SOC 2 certified? We have to answer a security questionnaire for our CRO.

Starch is not SOC 2 Type II certified today. There's no on-prem or self-hosted option. If your security review requires SOC 2 Type II, that's an honest blocker to flag upfront — it's on the roadmap but not available now.

We already pay for Apollo sequences. Why do we need Starch for LinkedIn outreach?

Apollo's LinkedIn steps in sequences are manual — they queue a task for a rep to execute, they don't fire automatically. Starch automates the actual browser action: sending the connection request and the follow-up message without a rep touching it. The two tools work together: Apollo handles your email sequences, Starch handles the LinkedIn layer and the attribution join, and both data sets live in one place for reporting.