Marketing & Growth

How to run a linkedin outreach campaign as Event Agency Founders

Marketing & GrowthFor Event Agency Founders3 apps11 steps~22 min to set up

You're running corporate events and social galas for 15-30 clients a year, and your LinkedIn outreach strategy is basically 'post something inspirational on a Tuesday and hope a venue director notices.' Your actual pipeline lives in a HoneyBook or Dubsado account where leads come in from referrals or a contact form — not from proactive outbound. You know the corporate side requires reaching HR directors, office managers, and CMOs before they've even Googled 'event agency,' but manually sending 20 LinkedIn connection requests a day, writing personalized notes, and following up with people who accepted but never replied eats 45 minutes you don't have between vendor calls and site walkthroughs.

Build this on Starch → See the apps used

Marketing & GrowthFor Event Agency Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A LinkedIn Automation app that sends targeted connection requests to HR directors, corporate office managers, and CMOs matching your ICP — running at a human pace through browser automation so your account stays safe

A CRM that tracks every LinkedIn lead from first connection to signed contract, with fields specific to event work: event type, headcount, budget range, venue preference, and decision timeline

An Email Agent that drafts follow-up sequences in your voice the moment a LinkedIn prospect replies or books an intro call, so no warm lead sits unanswered for 48 hours

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

Data sources & config

LinkedIn Automation runs through browser automation on your LinkedIn account — no LinkedIn API needed. The CRM connects to Gmail via Starch's scheduled sync so email thread history pulls in automatically. The Email Agent (Email Triage in the App Store) also uses Gmail via scheduled sync. LinkedIn connection and profile data syncs on a schedule through Starch's direct LinkedIn connection for enrichment inside the CRM.

Prompts to copy

Build me a LinkedIn outreach campaign targeting HR directors and office managers at companies with 50-500 employees in [city]. Send connection requests with a note mentioning I run a boutique corporate events agency that handles everything from 20-person team offsites to 500-person galas. Review incoming requests from anyone in HR, marketing, or executive admin and accept them automatically. Leave one thoughtful comment per day on posts from people in my target ICP.

Build me a CRM for my event agency. Each deal should have: contact name and company, event type (offsite, holiday party, conference, gala), estimated headcount, budget range, venue city, how they found us, current stage (prospect / proposal sent / contract out / deposit received / event confirmed), and next follow-up date. Pull in email thread history from Gmail so I can see every message in context. Ask me 'who hasn't heard from me in 21 days?' and give me a real list.

Set up an Email Agent connected to my Gmail that triages my inbox by priority, summarizes long vendor and client threads in one sentence, drafts replies for new leads who came in from LinkedIn or the contact form, and reminds me about any unanswered email after 48 hours.

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 describe your ICP in plain English: job titles you're targeting (HR directors, office managers, CMOs, executive assistants at mid-market companies), industries where corporate events are regular budget items (financial services, tech, consulting, pharma), and company size range.

2 Set your daily outreach volume and connection-request note template inside LinkedIn Automation — Starch runs it through browser automation at a human pace, so LinkedIn reads it as normal activity rather than a bot, protecting your account from flags and rate limits.

3 Install the CRM app and customize it for event agency work by telling Starch the fields that actually matter to you: event type, headcount estimate, budget range, venue city, lead source, and pipeline stages from first inquiry to deposit received.

4 Connect Gmail to the CRM via Starch's scheduled sync so every email thread with a prospect automatically attaches to their deal record — no manual logging, no copy-pasting subject lines into notes.

5 As LinkedIn connections accept your request, move them from LinkedIn Automation into the CRM manually or ask Starch to create a new deal record for each accepted connection that matches your ICP — include their job title, company, and the note they replied with.

6 Install the Email Triage app and connect it to your Gmail via scheduled sync. Tell the Email Agent your follow-up rules: draft a reply for any new event inquiry within one hour, flag any unanswered email from a prospect after 48 hours, and summarize threads longer than 10 messages so you can respond without reading the whole chain.

7 When a LinkedIn prospect replies to your message or accepts and messages you, the Email Agent picks it up in Gmail if they've emailed you, or you paste their message into Starch directly — and it drafts your reply in your voice based on the context of your agency and the event type they mentioned.

8 Use the CRM's natural-language query — 'which prospects have been sitting in proposal-sent stage for more than 14 days?' — to surface stalled deals every Monday and route follow-up tasks back to LinkedIn Automation for a comment or message nudge.

9 Track conversion by lead source inside the CRM. Ask Starch: 'show me the close rate for LinkedIn-sourced leads versus referrals over the last 90 days' — this tells you whether the outreach investment is worth the calendar space.

10 When a deal moves to contract-out stage, use the Email Agent to draft the contract-summary email in your voice, pulling in the event details (headcount, date, venue, services included) from the deal record in the CRM.

11 Set a weekly automation: every Monday morning, pull a summary of LinkedIn Automation activity (requests sent, accepted, reply rate) and CRM deal movement (new leads added, proposals sent, contracts signed) and Slack yourself a digest so you walk into the week knowing exactly where your pipeline stands.

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 Corporate Offsite Push — NYC Agency

Sample numbers from a real run

LinkedIn connections sent (6 weeks)	420
Accepted connections	168
Replies / expressed interest	31
Discovery calls booked	14
Proposals sent	9
Contracts signed	4
Average event contract value	18,500
Pipeline revenue closed	74,000

A NYC-based corporate events agency running a two-person operation wanted to get ahead of Q2 offsite season — traditionally when tech and finance companies book team retreats. They used LinkedIn Automation to target HR directors and office managers at companies with 100-400 employees in the financial services and SaaS sectors. Over six weeks, 420 connection requests went out at 70 per week, 168 were accepted (40% acceptance rate), and 31 people replied with some version of 'yes we're actually thinking about a summer offsite.' The CRM captured all 31 as active deals with event type (team offsite), headcount (range: 40-150), and budget range filled in from the initial conversation. The Email Agent drafted follow-up sequences for all 31 within the same day they replied — no prospect waited more than two hours for a response. Of 14 discovery calls booked, 9 got proposals, and 4 signed contracts averaging $18,500 each, generating $74,000 in new revenue from a channel that had previously been zero. The agency owner spent roughly 20 minutes a day reviewing the CRM and approving Email Agent drafts — everything else ran on its own.

Measurement

How you'll know it's working

LinkedIn connection acceptance rate (target: 35-45% for warm ICP targeting)

Lead-to-discovery-call conversion rate by LinkedIn vs. referral vs. contact form

Average days from first LinkedIn reply to signed contract

Proposal win rate for LinkedIn-sourced leads vs. inbound leads

Revenue attributed to LinkedIn outreach per quarter

Comparison

What this replaces

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

Expandi or Dripify for LinkedIn automation

Dedicated LinkedIn outreach tools but they don't connect to your CRM or email follow-up — you're still stitching three tools together and manually logging who responded.

HubSpot Starter CRM

More polished CRM UI but you'll spend hours configuring it to match event agency workflows, and the LinkedIn outreach and email AI layers require separate paid add-ons that push the monthly cost well above what a two-person agency wants to spend.

HoneyBook or Dubsado with manual LinkedIn outreach

Great for managing booked clients and contracts but neither has any outbound prospecting capability — your LinkedIn pipeline is entirely manual, which doesn't scale past what you can personally click through each morning.

Phantombuster for LinkedIn scraping

Can extract prospect lists and send bulk requests but uses API-style automation that LinkedIn actively throttles and flags — higher account-suspension risk than Starch's browser-automation approach, and no CRM or email drafting built in.

On Starch RECOMMENDED

One platform — linkedin automation, crm, founder inbox 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 LinkedIn flag or suspend my account if I use this?

Starch runs LinkedIn Automation through browser automation — meaning it navigates LinkedIn the same way a person would, at a human-paced cadence. LinkedIn's restrictions target API-based scrapers and bulk-action tools that look like bots. Starch's approach looks like normal activity. That said, no automation tool can guarantee zero risk — if you set your daily volume unreasonably high or your account is already flagged, that risk exists regardless of what tool you use. Keep daily connection requests in the 50-80 range and you're in safe territory.

My leads come in through HoneyBook and Dubsado — can Starch pull those in?

HoneyBook and Dubsado are web-based platforms, so Starch can automate interactions with them through browser automation — no API needed. For a tighter integration, you can also route new lead notifications to Gmail and have the CRM pick them up from there via scheduled sync. Describe the workflow you want and Starch will build the bridge.

Can the CRM handle event-specific fields like venue, headcount, and event date — or is it a generic sales CRM?

The CRM adapts to whatever schema you describe. Tell Starch 'I need fields for event type, headcount estimate, venue city, budget range, client's internal point of contact, and event date' and it builds exactly that. You're not reshaping your agency workflow to fit a generic pipeline — you're describing your pipeline and Starch builds around it.

Does Starch store my email drafts and LinkedIn messages, or does it just generate them on demand?

The Email Agent drafts replies based on the Gmail thread context it reads via scheduled sync. Drafts live in your Gmail drafts folder — you review and send, or click to send directly. Starch doesn't store your email content independently. LinkedIn messages are sent through browser automation in real time, not stored in Starch.

I'm not SOC 2 certified myself, but some of my corporate clients ask about data security. What can I tell them?

Honest answer: Starch is not SOC 2 Type II certified today. If a corporate client has a vendor security review process that requires a SOC 2 report, that's worth knowing upfront. For most independent event agencies doing outreach and pipeline tracking, this isn't a blocker — but it's worth flagging if you work with clients in regulated industries like financial services or healthcare where vendor security reviews are standard.

What if I want to target attendees or sponsors for a specific event, not just ongoing pipeline?

That's a campaign you can build from scratch. Tell Starch: 'Build me a one-time LinkedIn outreach campaign targeting CTOs and VPs of Engineering at Series B and C companies in New York City — I'm inviting them to a 40-person tech founders dinner on April 15th. Send a connection request with a personalized note about the event, and once they accept, send a follow-up message with the event details and a Calendly link to RSVP.' Starch builds the automation, the CRM tracks RSVPs, and the Email Agent follows up with anyone who hasn't responded after five days.