Sales & CRM

How to enrich leads with linkedin data as Small RevOps Teams

Sales & CRMFor Small RevOps Teams3 apps10 steps~20 min to set up

Your HubSpot or Apollo contacts go stale faster than you can fix them. A rep closes a deal, the title in the CRM is still 'VP Sales' from 18 months ago, and LinkedIn shows the person left the company in Q3. You're a two-person team supporting 30 reps, so you can't manually cross-reference LinkedIn against HubSpot for every record — but bad data kills forecast accuracy, tanks personalization in outbound sequences, and means your ICP scoring is running on garbage inputs. You've tried exporting to Sheets, using Apollo's enrichment, or paying for a data vendor, but none of it stays current automatically or feeds cleanly back into the workflow you actually care about.

Build this on Starch → See the apps used

Sales & CRMFor Small RevOps Teams3 apps10 steps~20 min to set up

Outcome

What you'll set up

A live enrichment layer that pulls current LinkedIn title, company, and seniority from LinkedIn into your HubSpot or Apollo records automatically — no manual CSV exports

A hygiene dashboard that surfaces stale or mismatched lead records so your reps are always working from current data before they dial or sequence

An automated weekly job that checks your open pipeline against LinkedIn, flags job changes or company shifts, and Slacks your team with a prioritized list of records to re-engage or update

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

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, owners) and syncs your Apollo.io data on a schedule (contacts, accounts, sequences). LinkedIn enrichment runs through browser automation — no LinkedIn API needed, Starch navigates LinkedIn on your behalf. Slack is connected from Starch's integration catalog and the agent queries it live when posting alerts. Google Sheets can be connected from Starch's integration catalog for any export steps you want to keep.

Prompts to copy

Connect my HubSpot and Apollo accounts. For every open deal and active lead in the last 90 days, find their current LinkedIn profile, pull their current title, company, and seniority level, and write that back to a field called 'LinkedIn Enriched At' with a timestamp. Flag any record where the company or title has changed since we last touched them.

Build me a lead hygiene dashboard that shows: (1) leads touched in the last 30 days where LinkedIn title doesn't match HubSpot title, (2) open deals where the contact has changed jobs in the last 6 months, and (3) leads in active Apollo sequences with no LinkedIn data at all. Sort by deal value descending.

Every Monday at 7am, check all open opportunities over $10k in HubSpot. For each one, look up the primary contact on LinkedIn, compare their current role to what's in our CRM. If anything changed, post a Slack message to #revops-alerts with the deal name, the old title, the new title, and a link to the HubSpot record.

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 base dataset your enrichment jobs run against.

2 Connect Apollo.io — Starch syncs your Apollo contacts, accounts, and sequence membership. Now you can cross-reference who's in an active sequence before you enrich, so you don't waste browser cycles on cold records.

3 Set up LinkedIn browser automation — tell Starch which LinkedIn profile fields you want to capture (current title, current company, connection degree, headline). Starch automates LinkedIn through your browser with human-paced activity so your account isn't flagged.

4 Run the initial enrichment pass — Starch works through your open pipeline and active leads from the last 90 days, looks up each contact on LinkedIn, and pulls current role data. For a list of 500 contacts, expect this to run as a background job over a few hours.

5 Map enriched fields back to HubSpot — Starch writes the enriched title and company into custom properties you define. You decide whether Starch overwrites or just flags a mismatch for a human to review.

6 Build the hygiene dashboard — describe what a clean record looks like versus a stale one. Starch builds a dashboard surface showing mismatches, missing LinkedIn data, and job-change flags sorted by deal value so your team works the highest-risk records first.

7 Wire the weekly Monday Slack alert — describe the cadence and the threshold (e.g., open deals over $10k). Starch schedules the job, checks LinkedIn for any contact where last enrichment is over 30 days old, and posts a structured Slack message to your #revops-alerts channel with old title, new title, and a direct HubSpot link.

8 Set up the 'rep request' flow — connect Slack so reps can type a command like '@starch enrich [company name]' and get a fresh LinkedIn pull on demand. This handles the 'can you just pull me a list' requests without you doing it manually.

9 Layer in ICP scoring — once LinkedIn data is clean, tell Starch to add a calculated field: 'ICP fit score' based on seniority, department, and company size pulled from LinkedIn enrichment. Now your reps' queue is sorted by actual fit, not just pipeline age.

10 Review the hygiene dashboard weekly before the forecast call — Starch keeps it live, so your Monday prep goes from pasting pipeline snapshots into slides to opening one view that already shows which deals have stale data, which contacts have churned, and which open opps need a record update before the CRO reviews them.

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 Pipeline Hygiene Run — 28 Deals Flagged

Sample numbers from a real run

Meridian Logistics (open opp, $47,000)	47,000
Caldwell Group (active sequence, $22,500)	22,500
Rova Technologies (stalled 60 days, $18,000)	18,000
Northgate Partners (deal closed-lost, still in sequence)	0
Symmetry Health (contact changed jobs)	31,000

Going into April's forecast call, your team had 112 open opportunities, 38 in active Apollo sequences, and no idea how many contacts had gone stale since Q1. Monday morning the Starch enrichment job ran across all open opps over $5k — 28 records came back flagged. Meridian Logistics: the primary contact, listed in HubSpot as 'Director of Operations,' had moved to a new company in February. Starch caught the title change via LinkedIn and posted to #revops-alerts with the old and new company. Symmetry Health had the same problem — $31k deal, primary contact now at a competitor, still getting sequenced by the original Apollo cadence. Caldwell Group's contact was still at the company but had been promoted to VP — actually a reason to re-engage with a higher-touch approach, not a generic sequence email. Northgate Partners had closed-lost in January but somehow stayed in an active Apollo sequence burning sends. Your team resolved all 28 flagged records in 90 minutes using the hygiene dashboard — before the forecast call, not after the CRO asked why the pipeline looked off.

Measurement

How you'll know it's working

Percentage of open pipeline contacts with LinkedIn data enriched in the last 30 days (target: >90%)

Number of job-change flags caught before a rep sends an outbound touch

Time from pipeline review request to hygiene dashboard ready — should drop from 2-3 hours of manual Sheets work to under 5 minutes

CRM data accuracy rate: HubSpot title vs. LinkedIn current title match across active deals

Sequence bounce or non-reply rate attributed to stale contact data (should decrease as enrichment improves)

Comparison

What this replaces

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

Clay

Clay is powerful for enrichment waterfall logic but requires a dedicated ops person to build and maintain the table logic; Starch lets you describe what you want in plain English and rebuilds the workflow when your rules change.

Apollo.io native enrichment

Apollo enriches contacts within Apollo, but it doesn't push clean data back into HubSpot automatically or flag job changes across your full open pipeline — you're still reconciling two systems manually.

ZoomInfo

ZoomInfo has broader B2B data coverage but costs significantly more, requires a contract negotiation, and still doesn't replace the automation layer that pushes enriched data back into your CRM workflow on a schedule.

Manual Sheets + LinkedIn Sales Navigator

This is what most two-person RevOps teams actually do — it works but it's 3-4 hours a week of one person's time that disappears into a spreadsheet that's outdated by Friday.

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

Does Starch actually write enriched data back into HubSpot, or does it just show me a report?

Starch syncs your HubSpot data on a schedule (read). For write-back, you can build an automation that outputs a structured CSV or triggers an update through HubSpot's API via Starch's integration catalog connection. The cleanest pattern today is Starch flagging mismatches in a dashboard your team reviews and updates — full automated write-back into HubSpot is doable but requires a step you configure when setting up the workflow.

Will LinkedIn block or flag our account for using this?

Starch uses browser automation with human-paced activity rather than the LinkedIn API, which means LinkedIn sees normal browsing behavior rather than API calls. This is the same approach used in the LinkedIn Automation app. That said, LinkedIn's terms of service prohibit automated scraping, so you're responsible for how you use this. Starch doesn't make bulk connection requests or mass-message as part of enrichment — it looks up profiles, not spams them.

We use Salesforce, not HubSpot. Does this work?

Yes. Salesforce is available through Starch's integration catalog — the agent queries it live when your enrichment apps or dashboards run. The scheduled-sync depth (automatic background refresh) that HubSpot gets isn't there for Salesforce today, so for high-frequency enrichment jobs you'll want to trigger runs manually or on a schedule you set, with Starch querying Salesforce live at that moment.

How long does the initial enrichment run take for a list of several hundred contacts?

Browser automation runs at human pace, so a batch of 500 contacts might take a few hours as a background job. Starch runs these as async jobs so it doesn't block your other work. For ongoing enrichment — checking just the records that changed or haven't been refreshed in 30 days — runs are much faster because you're working a smaller delta, not the full list every time.

Is Starch SOC 2 certified? We have to answer this for our security team.

Not yet. Starch is not currently SOC 2 Type II certified. If that's a hard requirement for connecting your CRM data, that's the honest answer and worth knowing upfront.

Can we use this to enrich net-new leads coming in from inbound forms, not just our existing pipeline?

Yes — you can set up an automation triggered by a new contact appearing in HubSpot or Apollo that immediately kicks off a LinkedIn lookup for that contact. Describe it as: 'When a new contact is created in HubSpot with a company domain, find their LinkedIn profile, pull their current title and seniority, and add those fields to the contact record.' Starch builds that as a triggered automation.