Marketing & Growth

How to run a linkedin outreach campaign as Professional Services Founders

Marketing & GrowthFor Professional Services Founders3 apps12 steps~24 min to set up

You're a 12-person consultancy founder who knows LinkedIn is where your next three retainer clients are hiding, but your 'outreach strategy' is opening the app at 10pm, firing off five connection requests to people you vaguely remember from a conference, and forgetting to follow up. Your SDR is you — on top of delivery, proposals, and a utilization spreadsheet that's already a week stale. Tools like Expandi or Dux-Soup hit LinkedIn's rate limits fast and flag accounts. You've tried dumping a prospect list into a Google Sheet and assigning it to a junior, but that junior is billable and the quality of messages reflects it. The pipeline dries up every time you're heads-down on a big engagement.

Build this on Starch → See the apps used

Marketing & GrowthFor Professional Services Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

An always-on LinkedIn outreach campaign that sends targeted connection requests to your ICP — specific titles, industries, seniority levels — at a human pace, so your account stays safe

Automated follow-up sequencing that moves warm connections into Gmail threads and syncs contact history into your CRM without you touching a spreadsheet

A weekly digest in Slack that shows you how many new connections accepted, which conversations got replies, and who's ready for a proposal conversation

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 Email Agent

Data sources & config

LinkedIn Automation runs through browser automation — no LinkedIn API needed, activity looks like normal human use. Starch syncs your Gmail data on a schedule so the Email Agent can read thread history and draft contextual follow-ups. HubSpot is connected from Starch's integration catalog and the agent queries it live when syncing new contacts. Slack is connected from Starch's integration catalog for weekly digest delivery. New contacts land in the Starch CRM, which can be pre-loaded from HubSpot or built fresh against your existing schema.

Prompts to copy

Send connection requests to heads of strategy, VP-level and above, at professional services or consulting firms with 50–500 employees. Use this note: 'Hi [first name], I work with firms your size on [service area] — connecting in case it's ever useful.' Cap at 20 invites per day.

When a new LinkedIn connection accepts, add them as a contact in my CRM with their title, company, and the date we connected. Tag them 'LinkedIn - cold outreach 2026'.

Draft a follow-up email to everyone tagged 'LinkedIn - cold outreach 2026' who hasn't replied in 7 days. Keep it under 4 sentences. Reference their firm size and ask if utilization or pipeline visibility is a current challenge.

Every Monday at 8am, send me a Slack message with: new LinkedIn connections this week, reply rate on follow-up emails, and any contacts who've moved to 'active conversation' in the CRM.

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

Walkthrough

Step-by-step

1 Install the LinkedIn Automation app from the Starch App Store and connect your LinkedIn account. Starch automates your LinkedIn through your browser — no API credentials or third-party tool required.

2 Describe your ICP in plain English: titles, industries, company size, geography. Starch builds the targeting criteria and sets daily send caps to stay within LinkedIn's safe activity range.

3 Write your connection request note once — or tell Starch the angle you want and have it draft three variants. Starch rotates them to avoid pattern detection.

4 Connect Gmail from Starch's scheduled-sync providers so the Email Agent has full thread history. When a connection accepts and an email conversation starts, Starch reads the context before drafting any follow-up.

5 Set up the Starch CRM (or connect HubSpot from Starch's integration catalog if you're already using it) as the single place new contacts land. Tell Starch: 'When someone accepts a LinkedIn connection, create a contact record with their title, company, LinkedIn URL, and tag the source.'

6 Build the follow-up automation: tell Starch 'Seven days after a new contact is tagged LinkedIn - cold outreach and no email reply exists, draft a follow-up email and queue it for my review.' You approve before anything sends.

7 Set pipeline stages in the CRM that match how your firm actually works — 'Connected,' 'In Conversation,' 'Proposal Sent,' 'Active Client.' Describe the stages and Starch builds the schema; no admin configuration needed.

8 Tell Starch to enrich new contacts automatically: 'For every new CRM contact tagged from LinkedIn outreach, pull their current title, employer, and any recent job changes from their LinkedIn profile.'

9 Build the weekly digest automation: 'Every Monday at 8am, post a Slack message to #pipeline with: LinkedIn connections added this week, follow-up emails sent and reply rate, and contacts who moved to In Conversation.' Connect Slack from Starch's integration catalog.

10 After 30 days, ask Starch: 'Show me which ICP segments — by title and firm size — have the highest connection acceptance rate and the most email replies.' Adjust your targeting criteria based on what's actually working.

11 When a contact replies and the conversation warms up, use the Email Agent to draft a short proposal-qualification email: 'Draft an email to [contact] asking about their current approach to [service area] and whether it's worth a 20-minute call.'

12 Promote hot contacts to 'Proposal Sent' in the CRM and set a reminder automation: 'If a contact has been in Proposal Sent for 10 days with no reply, flag them in Slack and draft a gentle follow-up.'

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 New Business Push — 8-Week Outreach Sprint

Sample numbers from a real run

LinkedIn connections sent (20/day × 40 days)	800
Acceptance rate (~28%)	224
Follow-up emails queued by Email Agent	224
Reply rate on follow-ups (~18%)	40
Calls booked from replies (~35% conversion)	14
Proposals sent from calls	5
Estimated new retainer ARR at £4,800/mo average	115,200

In February 2026, the founder of a 12-person London-based change management consultancy set up LinkedIn Automation targeting 'Head of Transformation,' 'VP Operations,' and 'Chief of Staff' at professional services firms with 100–400 employees in the UK. Starch sent 20 connection requests per day through browser automation — human-paced, no API flags. By week three, 224 connections had accepted. The Email Agent, reading synced Gmail history, drafted a 3-sentence follow-up for each: 'We work with firms your size on organisational change during growth or restructuring — curious whether that's a live challenge for you right now.' Forty replied. Fourteen calls were booked. The founder reviewed and approved every draft before it sent; total active time spent on outreach across the 8 weeks was under 3 hours. Five proposals went out. Two retainers closed at £4,800/month. The CRM, built inside Starch against the firm's actual pipeline stages, tracked every contact from 'Connected' through 'Active Client' — and a Monday morning Slack digest meant the founder knew exactly where the pipeline stood without opening a spreadsheet.

Measurement

How you'll know it's working

Connection acceptance rate by ICP segment (title × firm size × industry)

Follow-up email reply rate — how well the messaging is converting cold connections

Pipeline velocity: days from LinkedIn connection to proposal conversation

New retainer ARR sourced from LinkedIn outreach per quarter

Founder hours spent on outreach activities per week (target: under 2 hours active time)

Comparison

What this replaces

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

Expandi or Dux-Soup

Purpose-built LinkedIn tools with more granular sequence controls, but they run via API or browser extension in ways LinkedIn actively detects; account restriction risk is real, and they don't connect to your CRM, Gmail, or Slack — you're still stitching.

HubSpot Sequences + Sales Hub

Solid for email sequencing once you have a contact's email, but LinkedIn outreach still requires a human or a separate tool; Sales Hub at this tier costs more per seat than most 12-person consultancies want to spend.

Manual outreach by a junior or VA

Fully human-reviewed but burns billable or near-billable hours, doesn't scale past 20-30 contacts per week, and dies the moment the person turns over.

Salesflow or Waalaxy

LinkedIn-native multi-step campaign tools, but no deep integration with your Gmail thread history, CRM data, or the rest of your ops stack — outreach stays siloed from where your actual pipeline lives.

On Starch RECOMMENDED

One platform — linkedin automation, crm, email agent 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 restricted?

Starch runs LinkedIn Automation through browser automation — your account, your browser session, at a pace that looks like normal human activity. You set the daily caps. Most restrictions happen when tools make direct API calls that LinkedIn's systems can fingerprint; Starch doesn't do that. That said, LinkedIn's policies on automation exist, and no tool can guarantee zero risk — keeping daily volumes conservative (20 invites/day is well within safe territory) is the right call.

Does Starch write the messages, or do I?

Both. You describe the angle — the ICP, the problem you solve, the tone — and Starch drafts the connection note and follow-up email. You review and edit before anything goes live. The Email Agent queues follow-up drafts for your approval; nothing sends without you seeing it first. If you want to write your own messages and just automate the sending and sequencing, that works too.

I'm already in HubSpot. Do I have to switch CRMs?

No. You can connect HubSpot from Starch's integration catalog; the agent queries it live when new contacts need to be created or updated. If your HubSpot setup is a mess and you want a cleaner CRM inside Starch, you can import your existing contacts and Starch will help clean the schema. Your choice — Starch works on top of your existing tools.

What if someone I'm targeting doesn't have a public email address?

Starch can enrich contacts with publicly available LinkedIn profile data through browser automation — title, employer, recent role changes. For email addresses not available on LinkedIn, the Email Agent works with the Gmail thread history once a conversation has started via LinkedIn messaging. Full cold-email prospecting from zero data is a different workflow; this is optimised for warm-to-warm LinkedIn-to-email conversion.

Is my email and LinkedIn data stored in Starch?

Starch syncs your Gmail data on a schedule — messages and thread history are stored in Starch's database so the Email Agent can read context when drafting follow-ups. LinkedIn activity runs through browser automation in session; Starch captures the output (who connected, when) and writes that to your CRM. Starch is not SOC 2 Type II certified today — if that's a hard requirement for your clients or firm policy, it's worth noting.

How long does it take to set this up?

The LinkedIn Automation app is a live App Store template — you're not starting from scratch. Describing your ICP, writing your first connection note, and connecting Gmail and HubSpot typically takes under an hour. The weekly Slack digest automation and CRM pipeline stages add another 30 minutes. First campaign can realistically be running the same day you start.

Can Starch track which ICP segments are actually converting, not just connecting?

Yes. Once your contacts are in the Starch CRM with source tags and pipeline stages, you can ask: 'Which titles and industries have moved from Connected to In Conversation at the highest rate over the last 60 days?' Starch queries the live data and gives you a real answer, not a canned report. That's how you refine targeting over time without guessing.