Sales & CRM

How to qualify inbound leads as Small Marketing Teams

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

Your team gets 200+ form fills a week from paid campaigns across Google, Meta, and LinkedIn. Half are tire-kickers, students, or the wrong company size entirely. The 'qualification' process right now is a HubSpot view that someone built six months ago, a Monday morning Slack thread where you manually flag the good ones for sales, and a spreadsheet where you're copy-pasting company size from LinkedIn because HubSpot didn't capture it. By the time a genuinely qualified lead gets a follow-up, it's been 18 hours. You have no scoring logic, no enrichment automation, and no reliable way to tell the CEO which campaign is actually sourcing pipeline-ready leads versus noise.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A live qualification view that scores inbound leads against your ICP criteria — company size, industry, job title, recent activity — without anyone manually touching a spreadsheet

An enrichment automation that pulls LinkedIn profile data and email context for every new HubSpot contact, so your first outreach is already informed

A weekly digest that shows which campaigns sourced qualified leads (not just form fills), so you can tell the difference between a high-volume channel and a high-quality one

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

Sales Agent CRM CRM Growth Analyst

Data sources & config

Starch syncs your HubSpot contacts, companies, deals, and owners on a schedule — that's the backbone of the qualification view. Gmail is synced on a schedule too, so Starch can check whether a lead has already emailed you before you reach out. LinkedIn enrichment runs through browser automation — no LinkedIn API needed — pulling current role, tenure, and recent activity for each scored contact. Customer.io or Klaviyo can be connected from Starch's integration catalog; the agent queries them live to check whether a lead is already in an active nurture sequence before routing them to sales.

Prompts to copy

Build me a lead qualification view that pulls new HubSpot contacts from the last 7 days, scores them against these criteria: company size between 50 and 500, job title contains 'marketing' or 'growth' or 'demand gen', and they submitted via our paid channels. Show me a ranked list with a fit score out of 10.

For every contact that scores 7 or above, pull their LinkedIn profile and summarize their last 3 posts, their current role tenure, and whether they're hiring in marketing right now. Add that as a note in HubSpot.

Every Monday at 8am, send me a Slack message showing which UTM sources produced leads that scored 7+ this week, the average score by campaign, and the top 5 leads by fit score with a one-line summary of each.

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 is your source of truth for every inbound lead.

2 Define your ICP criteria in plain language: company headcount range, industries you actually close, job titles that show up in won deals, and any disqualifying signals like personal email domains or single-person companies.

3 Start from the Sales Agent CRM app in the Starch App Store — it's pre-wired for HubSpot and handles contact context out of the box. Customize the pipeline stages and scoring fields to match your qualification rubric.

4 Tell Starch to build a fit-score field: 'Score each new HubSpot contact from 1-10 based on company size, job title match to our ICP, and whether they came from a paid channel. Weight company size at 40%, title match at 40%, and channel at 20%.'

5 Wire up LinkedIn enrichment via browser automation — tell Starch: 'For any contact that scores 6 or above, find their LinkedIn profile and pull their current title, company size, tenure in role, and whether they're actively hiring in marketing. Write it as a note on the HubSpot contact.'

6 Connect Gmail — Starch syncs your inbox on a schedule. Add a step: 'Before flagging a lead for sales follow-up, check whether anyone on our team has already emailed them. If yes, include the thread summary in the handoff note.'

7 Connect Customer.io from Starch's integration catalog so the agent can query it live — add a routing rule: 'If a qualified lead is already in an active nurture sequence in Customer.io, do not send to sales. Tag them as nurture-active and surface them again in 14 days.'

8 Build the weekly campaign-quality report: 'Every Monday at 8am, pull all leads that came in last week, group them by UTM source and campaign name, calculate the average fit score per campaign, and show me the top 3 campaigns by qualified lead volume alongside total spend from Google Ads and Meta Ads.' Connect Google Ads and Meta Ads from Starch's integration catalog.

9 Set a Slack automation — Starch posts the ranked lead list and campaign quality summary to your #demand-gen channel every Monday, tagged with the campaign source so you can bring it straight into your weekly sync with sales.

10 Once the scoring is running, ask Starch: 'Which lead attributes are most common among contacts that converted to opportunities in the last 90 days?' Use that answer to tighten your ICP criteria and re-score.

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

March 2026 Demand Gen Review

Sample numbers from a real run

Total form fills (March)	847
Leads scored 7+ (ICP fit)	112
Leads already in Customer.io nurture (suppressed from sales)	34
Net new qualified leads routed to sales	78
Average hours to first sales touch (before Starch)	22
Average hours to first sales touch (after Starch)	4

In March, your Google Ads campaigns drove 410 form fills — the most of any channel. But when Starch scored them against your ICP, only 58 hit a 7 or above (14%). LinkedIn drove 180 form fills and produced 47 qualified leads (26%). The weekly Monday digest made this visible for the first time: Google was your volume channel, LinkedIn was your quality channel, and you'd been allocating budget 60/40 in Google's favor. The LinkedIn enrichment step also flagged 11 contacts who had 'VP of Marketing' titles at companies between 100 and 300 employees, had been in role less than 6 months (likely still building out their stack), and weren't yet in any nurture sequence — your sales rep touched all 11 within the same day the automation ran. Three of those converted to discovery calls by end of month.

Measurement

How you'll know it's working

Qualified lead rate by campaign (fit-scored leads as % of total form fills, by UTM source)

Time-to-sales-touch for leads scoring 7+ (measured in hours, not days)

Suppression rate — what % of inbound leads were already in active nurture and correctly excluded from sales routing

ICP attribute match rate — how often enriched LinkedIn data confirms the self-reported title and company size from the form

Pipeline contribution by channel — which campaigns produced leads that became HubSpot opportunities within 30 days

Comparison

What this replaces

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

HubSpot Workflows + lead scoring

HubSpot's native lead scoring works if your ICP criteria map cleanly to HubSpot properties, but enriching from LinkedIn, suppressing against Customer.io, and surfacing a campaign-quality report all require separate tools or manual joins — none of it is in one place.

Clearbit + HubSpot

Clearbit gives you company-level enrichment automatically, but it's a paid add-on with per-record pricing, doesn't pull LinkedIn behavioral signals, and still doesn't produce the campaign quality view your team needs for the Monday CEO briefing.

Zapier + Google Sheets

You can stitch together a scoring flow with Zaps and a Sheet, but every step is a separate Zap, the scoring logic lives in formulas no one remembers how to update, and when something breaks at 2am before a board meeting you're debugging trigger logs instead of sleeping.

Clay

Clay is excellent at enrichment and waterfall lookups, but it's priced per row, requires you to build the table logic yourself, and doesn't connect back to your campaign reporting or route to HubSpot and Slack in the same workflow.

On Starch RECOMMENDED

One platform — sales agent crm, crm, growth analyst 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

We already have HubSpot lead scoring turned on. Why would we add Starch on top of it?

HubSpot's lead scoring is property-based — it can score on title, company size, page views. It can't pull LinkedIn activity from outside HubSpot, check whether someone's already mid-sequence in Customer.io, or build the campaign quality report that joins your score distribution against paid spend. Starch sits on top of HubSpot, not instead of it.

Does Starch store our lead data, or does it query HubSpot live each time?

Starch syncs your HubSpot contacts, companies, and deals on a schedule and stores them — that's what powers the scoring view without hitting HubSpot's API on every page load. Your Customer.io and ad platform data is queried live from Starch's integration catalog each time an automation runs. That means HubSpot data is always fresh on a sync cadence; ad spend numbers reflect what's live in the platform at the moment the report runs.

Is Starch SOC 2 certified? Our IT team will ask.

Not yet — Starch is not SOC 2 Type II certified today. That's a real limit worth knowing before you route sensitive lead data through it. If your company has strict data compliance requirements, this is a conversation to have with your IT and legal team before you start connecting HubSpot.

Can Starch pull LinkedIn data on leads without us having a Sales Navigator license?

Yes. LinkedIn enrichment runs through browser automation — Starch navigates LinkedIn through your browser session the way a person would, no API or Sales Navigator required. It pulls public profile data: current title, company, tenure, and recent public activity. It won't access private InMail or recruiter-only data.

What happens when a lead's company size isn't captured in the HubSpot form?

That's exactly where the LinkedIn enrichment step fills the gap. When a contact scores on title and channel but has no company size in HubSpot, Starch's browser automation finds their LinkedIn profile, pulls the employee count from the company page, and writes it back as a note. You can then tell Starch to re-score any contacts where that field was previously blank.

We use Customer.io for nurture — can Starch suppress leads that are already in a sequence?

Yes. Connect Customer.io from Starch's integration catalog; the agent queries it live when the routing automation runs. Tell Starch: 'Before flagging this contact for sales outreach, check whether they have an active campaign in Customer.io. If yes, tag them nurture-active and skip the sales handoff.' That logic runs automatically on every new qualified lead.