Sales & CRM

How to enrich leads with linkedin data as Small Marketing Teams

Sales & CRMFor Small Marketing Teams3 apps12 steps~24 min to set up

You're a three-person marketing team running demand gen, content, and lifecycle simultaneously. Your HubSpot contacts exist in one silo, your LinkedIn outreach lives in another, and every time someone asks 'what company does this lead actually work at now?' you're manually cross-checking a Sales Nav tab against a HubSpot record that was last touched six months ago. Enriching leads with LinkedIn data means either paying for a standalone enrichment tool, copy-pasting from profiles by hand, or begging the SDR to update fields they never update. Meanwhile your nurture flows in Customer.io or Klaviyo are segmenting on stale job titles and company sizes, and you're blaming creative when the real problem is the data underneath.

Build this on Starch → See the apps used

Sales & CRMFor Small Marketing Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A LinkedIn-enriched contact list that pulls current job title, company, and seniority from LinkedIn profiles and writes it back to your working CRM view — updated on demand without anyone copy-pasting

An automated outbound workflow that identifies LinkedIn profiles matching your ICP, sends connection requests at human-paced intervals through browser automation, and logs activity against your HubSpot contacts

A reporting view that shows which enriched segments are converting — so you can tell your CEO why MQL quality improved, not just that it did

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 contacts on a schedule (scheduled-sync provider) and syncs your Gmail thread history so email touchpoints appear on each contact record. LinkedIn enrichment and outreach run through browser automation — no LinkedIn API required, so your account operates at normal human-paced activity. HubSpot is the system of record; Starch reads it, enriches it via LinkedIn browser automation, and writes enrichment results back into your Starch CRM view. Customer.io or Klaviyo can be connected from Starch's integration catalog; the agent queries them live when you need segment overlap data.

Prompts to copy

Look at my HubSpot contacts added in the last 30 days. For any contact missing job title or company size, find their LinkedIn profile and fill in current title, company, seniority level, and industry. Flag anyone whose title has changed since we last emailed them.

Build me a CRM view that shows HubSpot contacts enriched with LinkedIn data — columns for current title, company headcount bucket, seniority, days since last email, and whether they've accepted a LinkedIn connection request. Let me filter by ICP match score.

Send LinkedIn connection requests to all first-degree connections of our three largest customers who work in demand gen or marketing ops at B2B SaaS companies with 50–500 employees. Pace it at no more than 20 invites per day and log each one back to HubSpot.

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

Walkthrough

Step-by-step

1 Connect HubSpot as a scheduled-sync provider — Starch pulls your contacts, companies, deals, and owners on a recurring schedule so your enrichment work is always running against current CRM data, not a CSV export from last Tuesday.

2 Connect Gmail through the scheduled-sync provider — email thread history surfaces on each contact record so you can see the last message alongside the LinkedIn enrichment data without switching tabs.

3 Install the LinkedIn Automation app from the Starch App Store. This gives you a pre-built starting point for ICP-targeted connection requests and profile review — you'll customize the ICP criteria to match your actual buyer profile (job title, industry, company size range).

4 Tell Starch which contacts to enrich first: paste in a HubSpot segment URL or describe the filter ('HubSpot contacts in the SaaS industry added in Q1 2026 with no job title on record'). Starch identifies the gaps.

5 Starch's browser automation opens each contact's LinkedIn profile, reads current title, company, seniority, and headcount, and writes the enriched fields back into your Starch CRM view alongside the HubSpot record.

6 Review the enriched batch — Starch flags anyone whose current title differs significantly from what HubSpot has on file (e.g., a contact you've been nurturing as a 'Marketing Coordinator' is now a 'Director of Demand Gen'). These are your highest-priority re-engagement candidates.

7 Use the LinkedIn Automation app to send connection requests to ICP-matched contacts who aren't yet connected. Set your daily cap (20–30 requests/day is typical) and describe the ICP in plain English — Starch handles pacing through browser automation so LinkedIn sees normal activity.

8 Build a CRM view that surfaces enriched contacts by segment: seniority tier, company size bucket, ICP match, and days since last touch. Tell Starch what columns you want and it assembles the view — no drag-and-drop, no BI tool required.

9 Connect Customer.io or Klaviyo from Starch's integration catalog. Ask Starch to show you which enriched segments are currently enrolled in which nurture flows — so you can identify mismatches (e.g., Director-level contacts getting entry-level drip content).

10 Set up a weekly automation: 'Every Monday, pull all HubSpot contacts whose job title changed in the last 7 days based on LinkedIn enrichment. Slack me a list with their old title, new title, and last email date.' This keeps your lifecycle team from nurturing stale personas.

11 Build a pipeline-contribution report on top of the enriched data: which LinkedIn-sourced or LinkedIn-enriched contacts converted to MQL, to opportunity, to closed-won. Pull HubSpot deal data alongside enrichment timestamps so you can show attribution, not just volume.

12 Publish your enrichment workflow as a saved automation inside Starch so any team member can trigger a batch enrichment run without rebuilding the logic — critical when your team is three people and no one has time to re-explain the process.

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 ICP Re-enrichment — 340 stale HubSpot contacts

Sample numbers from a real run

HubSpot contacts in batch	340
Contacts with outdated or missing job title	187
Title changes detected via LinkedIn	64
Net-new Director/VP-level contacts identified	29
Re-engagement emails sent to changed-title contacts	64
MQLs from re-engaged batch within 30 days	11

In February 2026, your team pulled a HubSpot segment of 340 contacts who hadn't been emailed in 90+ days. Manually, enriching these would have taken an SDR 10–15 hours. Instead, you described the segment to Starch and ran LinkedIn enrichment through browser automation. Of 340 contacts, 187 had missing or stale titles. Starch flagged 64 title changes — the most significant being 29 contacts who had moved into Director or VP roles since their last touch. You briefed your CEO on this cohort directly: 'We have 29 people who were mid-level when we last talked to them and are now decision-makers. Here's the list.' Your lifecycle marketer updated the Customer.io segment the same day, pulled them out of the entry-level nurture, and sent a re-engagement sequence tailored to Director-level buyers. Within 30 days, 11 of those 64 re-engaged contacts converted to MQL — a number you could tie directly to enrichment quality, not volume or creative. That's the kind of attribution story a three-person team can actually tell.

Measurement

How you'll know it's working

Contact enrichment coverage rate — % of HubSpot contacts with current LinkedIn title, company, and seniority on file

Title-change detection rate — how many contacts per month are flagged for ICP re-evaluation based on enrichment

Re-engagement MQL rate — % of stale contacts who convert to MQL after being re-segmented on enriched data

LinkedIn connection acceptance rate — % of ICP-targeted outreach requests accepted (benchmark: 25–40% for well-targeted ICP)

Nurture segment accuracy — % of active nurture contacts whose enrollment matches their current seniority and buyer stage based on enriched data

Comparison

What this replaces

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

Clay

Clay is purpose-built for enrichment workflows and has more enrichment data sources out of the box, but it's a separate tool from your CRM and campaign stack — you'll still need to export, enrich, and re-import, and it doesn't connect natively to your HubSpot nurture logic or give you a custom reporting surface on the same platform.

LinkedIn Sales Navigator + manual copy-paste

Accurate data but entirely human-hours-dependent — a three-person team enriching 300+ contacts by hand is a week of someone's time every quarter, and it still doesn't write back to HubSpot automatically.

ZoomInfo or Clearbit

Strong data coverage and HubSpot integrations exist, but pricing is built for larger sales teams and you're paying for a contact intelligence platform when what you actually need is enrichment tied to your existing workflows — not a standalone database license.

HubSpot native enrichment (Breeze Intelligence)

Convenient because it lives inside HubSpot, but credit-based pricing adds up fast for a small team running regular batch enrichments, and it doesn't give you the custom reporting or LinkedIn outreach automation in the same place.

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 LinkedIn actually allow this kind of automation? Will it flag our account?

Starch runs LinkedIn enrichment and outreach through browser automation — it navigates LinkedIn the way a human would, at human-paced intervals, rather than hammering an API. That means LinkedIn sees normal activity rather than bot-pattern API calls. You set daily caps (e.g., 20 connection requests per day), which keeps behavior well within the range of what a real person would do. No guarantees — LinkedIn's terms are always evolving — but this approach is materially lower risk than tools that use unofficial APIs or scraping at scale.

Does Starch write enriched data back into HubSpot, or does it only live in Starch?

Starch syncs your HubSpot data on a schedule and shows enriched fields in your Starch CRM view. Writing fields back directly into HubSpot as a two-way sync depends on your workflow setup — for most small marketing teams, the practical approach is to use Starch as the enriched working layer and export updated records to HubSpot when you need a segment to act on. This is worth discussing with your team before you set up the workflow so you're not duplicating sources of truth.

Our contact list is in Customer.io, not HubSpot. Can we still do this?

Yes. You can connect Customer.io from Starch's integration catalog — the agent queries it live when your app runs. Enrichment via LinkedIn browser automation works the same way; you'd describe the segment you want to enrich and Starch works from there. HubSpot is used in the pre-built Sales Agent CRM template because it's a scheduled-sync provider (deepest integration), but Starch isn't limited to HubSpot as the source of contact data.

We don't have a dedicated SDR. Can a marketer actually run this?

That's the point. You describe what you want in plain English — 'find LinkedIn profiles for my HubSpot contacts added in Q1 who are missing job titles, and fill them in' — and Starch does the work. You're not configuring a Zapier workflow or writing a script. The LinkedIn Automation app gives you a starting template you can customize for your ICP in the same way.

Is Starch SOC 2 certified? We'll need to get security approval.

Not yet — Starch is not SOC 2 Type II certified as of now. If your company's security review requires SOC 2, that's a real blocker to flag upfront. It's on the roadmap, but we won't claim otherwise.

How fresh is the LinkedIn data? Is this pulling live profiles or cached data?

LinkedIn enrichment runs through browser automation at the time you trigger it — Starch visits the profile in a browser session and reads what's there today. It's not a cached database of profiles from six months ago. The tradeoff is that enriching a large batch (500+ contacts) takes meaningful run time, so you'd typically run enrichment in batches or on a scheduled cadence rather than in real time.