Sales & CRM

How to enrich leads with linkedin data as Event Agency Founders

Sales & CRMFor Event Agency Founders2 apps10 steps~20 min to set up

You get 40 inquiries a month from couples, corporate clients, and nonprofits who all found you the same way — Instagram, a vendor referral, or your website contact form. Their LinkedIn profiles would tell you instantly whether the corporate lead is a budget holder or an EA forwarding a task, and whether the social lead is a planner at a funded company or someone who wants a full-service gala on a $3,000 budget. Instead you're manually searching LinkedIn between proposal writing sessions, copy-pasting job titles into your HoneyBook or Dubsado contact record, and guessing at prioritization. Half your proposals go to leads you wouldn't have chased if you'd known the full picture first.

Build this on Starch → See the apps used

Sales & CRMFor Event Agency Founders2 apps10 steps~20 min to set up

Outcome

What you'll set up

A living lead list where every contact — from your inquiry form, Gmail, or a manual add — gets LinkedIn profile data (title, company, seniority, industry) pulled in automatically before you send the first proposal.

A qualification layer that scores or tags new leads by job title and company type so you know immediately which $25k corporate gig to call back today versus which $800 backyard party inquiry to politely route to your starter package.

An outbound connection workflow that sends targeted LinkedIn invites to event managers, HR directors, and office operations leads at companies in your metro — so your pipeline grows while you're on-site at a wedding.

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

CRM LinkedIn Automation

Data sources & config

The CRM uses Starch's Gmail scheduled sync to pull inbound inquiry threads and attach them to the right contact record — Starch syncs your Gmail data on a schedule. LinkedIn enrichment and the outbound connection workflow both run through browser automation on your LinkedIn account — no LinkedIn API needed. Contact data (names, emails, notes) lives in Starch; LinkedIn profile data is fetched via browser automation each time a new lead is added or you trigger a manual refresh.

Prompts to copy

Build me a CRM for my event agency. Stages are: New Inquiry, Proposal Sent, Contract Out, Deposit Received, Planning Active, Completed, Lost. Fields I need on every contact: event type (wedding / corporate / social / nonprofit), estimated budget range, event date, venue status (confirmed / searching / TBD), how they found me (Instagram / referral / website / LinkedIn), and LinkedIn profile URL. When a new lead comes in from Gmail, pull their LinkedIn profile data — job title, company name, company size — and populate those fields automatically. Flag any contact where company size is over 100 employees as a 'Corporate Priority' tag.

Set up LinkedIn Automation to send connection requests to people at companies in the Chicago metro with titles like 'Office Manager', 'Executive Assistant', 'HR Director', 'Events Coordinator', or 'Chief of Staff' at companies with 50 to 500 employees. Use a personalized note that mentions I run a corporate events agency and specialize in off-sites, team celebrations, and client dinners. Review incoming connection requests and accept anyone whose title or company matches that ICP. Run this at normal human pace — no more than 20 outbound invites per day.

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

Walkthrough

Step-by-step

1 Connect Gmail — Starch syncs your Gmail data on a schedule, so every inquiry email that lands in your inbox becomes a candidate lead record with the full thread attached.

2 Start from the CRM app in the Starch App Store and describe your agency's actual pipeline stages and fields in plain English — event type, budget range, venue status, how they found you. Starch rebuilds the schema around your terminology, not a generic sales template.

3 Add a LinkedIn Profile URL field to the contact record. When a new lead is created from an email thread, describe the enrichment rule: 'search for this contact's LinkedIn profile using their name and company, then fill in their job title, company size, and seniority level.'

4 Set a qualification rule in the CRM: any contact where LinkedIn company size is 50+ employees and the event type is corporate gets tagged 'Corporate Priority' and surfaces at the top of your pipeline view automatically.

5 Install LinkedIn Automation from the App Store and describe your ICP in plain English — the job titles, industries, metro area, and company size range of the decision-makers and coordinators who book corporate events at your tier.

6 Set daily outbound invite limits (20/day is a safe default) and write the connection request note in your own voice — reference your agency specialty, not a generic pitch. Starch's browser automation sends these at human-paced intervals so your LinkedIn account stays healthy.

7 Configure the incoming request review: tell Starch which title keywords and company types should be auto-accepted versus flagged for your manual review. Anyone accepted from LinkedIn automatically becomes a lead in your CRM with their profile data pre-filled.

8 Wire the Email Agent to watch for reply threads from LinkedIn-sourced leads: when someone responds to a connection request or sends a direct message, the Email Agent drafts a first-response note in your voice and routes it to your Gmail for one-click send.

9 Build a 'Leads to Enrich' view in the CRM — a filtered list of contacts added in the last 7 days who are missing a LinkedIn profile or job title — so you can trigger a batch enrichment run once a week for any leads that slipped through.

10 Add a KPI dashboard panel: 'Proposal-to-deposit rate by lead source' — split by LinkedIn-sourced leads vs. Instagram vs. referral. After 60 days you'll have real data on whether LinkedIn-enriched leads close at a higher rate.

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

April 2026 corporate pipeline — 11 new leads, 3 proposals, 2 deposits

Sample numbers from a real run

LinkedIn-sourced lead — HR Director at 200-person fintech	18,000
Gmail inquiry — 'events@domain.com' unknown seniority — enriched to Office Manager, 12-person startup	2,200
Instagram DM — enriched to freelance designer, no company	0
LinkedIn-sourced lead — Executive Assistant at 400-person law firm	22,000
Website form — enriched to VP of People at 90-person SaaS company	14,500

In April, 11 new leads came in across four sources. Without enrichment, all 11 looked the same in your inbox — a name and an email. With LinkedIn enrichment running in the CRM, within 24 hours you knew the fintech HR Director managed a $50k annual events budget and had already booked two agencies in the prior year (visible from her recommendations), making the $18k proposal a strong bet. The 'events@domain.com' email resolved to an Office Manager at a 12-person startup — still a real lead, but correctly routed to your starter package conversation instead of your full-service pitch deck. The Instagram DM enriched to a freelance designer with no events budget signal — you sent a kind 'we're outside your budget' response in 2 minutes instead of spending 45 minutes on a proposal. The law firm EA turned into your largest April deposit: $22k for a partner appreciation dinner in May, sourced entirely from a LinkedIn invite Starch sent on a Tuesday morning while you were on-site at a bridal shower. Total time spent on lead qualification that week: under 30 minutes.

Measurement

How you'll know it's working

Proposal-to-deposit rate by lead source (LinkedIn-sourced vs. Instagram vs. referral vs. website)

Average time from inquiry to first proposal sent — target under 4 hours for Corporate Priority leads

LinkedIn connection acceptance rate by ICP segment (title + company size bucket)

Percentage of active pipeline contacts with LinkedIn job title and company size populated

Revenue booked per lead-source channel, rolling 90 days

Comparison

What this replaces

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

HoneyBook or Dubsado

Great for contracts, invoices, and client portals — but neither pulls LinkedIn data, scores leads by seniority, or runs outbound connection campaigns; you'd still be doing all the qualification manually.

Hunter.io + LinkedIn Sales Navigator (manual workflow)

Sales Navigator surfaces the ICP leads and Hunter finds emails, but stitching them into your CRM and writing personalized notes is entirely manual labor — typically 2-3 hours a week a small agency doesn't have.

HubSpot Starter + LinkedIn Sales Navigator

A real enrichment workflow is possible here, but HubSpot's free/starter tier doesn't include native LinkedIn enrichment, and the configuration effort assumes you or someone on your team wants to spend a week in HubSpot's settings.

Airtable + Zapier + PhantomBuster

PhantomBuster can do LinkedIn scraping and Zapier can pipe it into Airtable, but you're maintaining three separate tools with separate billing, separate failure points, and no AI that can answer 'who are my best-fit open leads right now' in plain English.

On Starch RECOMMENDED

One platform — crm, linkedin automation 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 restrict my account if I use this automation?

LinkedIn Automation in Starch runs through browser automation — Starch automates LinkedIn through your browser at human-paced intervals, not via LinkedIn's API. That means LinkedIn sees normal activity patterns rather than bulk API calls. The 20-invites-per-day default is intentionally conservative. That said, no automation tool can guarantee zero risk from LinkedIn's detection systems — if you're also running outreach manually on the same account, keep your total daily activity within normal human range.

My leads come from HoneyBook inquiry forms, not just Gmail — can Starch pull those in too?

HoneyBook is web-reachable, so Starch can automate it through your browser — no HoneyBook API needed. You'd describe the automation: 'When a new inquiry form submission appears in HoneyBook, copy the contact name, email, event type, and event date into my Starch CRM and trigger LinkedIn enrichment.' This is a standard browser automation pattern in Starch.

What exactly does LinkedIn enrichment pull? Am I getting their full profile?

Starch fetches what's visible on a LinkedIn profile when you're logged in — job title, current company, company size (if listed), location, and connection degree. It does not pull private contact info, direct messages from people you haven't messaged, or data behind LinkedIn's recruiter paywalls. For most lead qualification purposes — 'is this person a budget holder at a company big enough to hire me?' — the publicly visible fields are exactly what you need.

I use Dubsado instead of HoneyBook — does that change anything?

Same answer as HoneyBook — Dubsado is web-reachable, so Starch can automate it through your browser without needing a Dubsado API. Describe the workflow you want and Starch builds it.

Is Starch SOC 2 certified? I sometimes handle Fortune 500 client data.

Starch is not currently SOC 2 Type II certified. If a corporate client requires a signed SOC 2 report before sharing data with a vendor tool, that's a real constraint worth naming upfront. For most small agency use cases — lead data, LinkedIn profiles, proposal status — this is not a blocker, but it's worth knowing.

What happens to LinkedIn lead data if someone updates their job title after I've enriched them?

Starch stores the enriched data at the time it was fetched. It doesn't auto-refresh LinkedIn profiles on a daily schedule — LinkedIn's rate limits make that impractical. The practical approach: run a manual enrichment refresh on your active pipeline contacts once a month, or set a reminder to re-enrich any lead before you send a proposal if more than 60 days have passed since they were added.