Sales & CRM

How to qualify inbound leads as Small RevOps Teams

Sales & CRMFor Small RevOps Teams2 apps12 steps~24 min to set up

You're two people supporting 30 reps, and inbound lead qualification is a daily fire drill. A form fill comes in, a rep pings you on Slack to ask if it's real, you cross-reference Apollo to check if the account is already in HubSpot, discover three duplicate contacts, find the deal was marked Closed Lost six months ago by someone who left, and by the time you've figured out what to tell the rep, twenty minutes are gone. Multiply that by a dozen leads a day. The routing logic lives in a Google Sheet that only you understand, ICP criteria change every time the CRO has a new idea, and nobody updates HubSpot until pipeline review forces the issue.

Build this on Starch → See the apps used

Sales & CRMFor Small RevOps Teams2 apps12 steps~24 min to set up

Outcome

What you'll set up

A live qualification app that pulls every inbound lead against your HubSpot and Apollo data, scores it against your current ICP definition, and flags duplicates or prior closed-lost history before a rep ever sees it

An automated routing and notification flow that assigns leads to the right rep based on territory or segment rules you define in plain language, then Slacks the rep with a one-paragraph brief on the account

A hygiene dashboard that surfaces stale opportunities, missing qualification fields, and leads that fell into HubSpot but never got touched — so your weekly forecast call isn't a data-cleaning session

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

Data sources & config

Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and owners — so the qualification app is always reading current pipeline state. Apollo is connected from Starch's integration catalog and queried live when the app needs to enrich or cross-reference an account. Slack is also connected from Starch's integration catalog so rep notifications go out without manual copy-paste. Gmail is synced on a schedule for email thread context inside the CRM view.

Prompts to copy

Build me a lead qualification app that scores every new HubSpot contact against our ICP: company size 50-500 employees, SaaS or fintech vertical, US-based, and no prior Closed Lost deal in the last 12 months. Show a confidence score, pull in any matching Apollo account data, flag duplicates, and surface the rep assignment based on the territory field in HubSpot.

Build a hygiene dashboard that shows every open opportunity created more than 14 days ago with no activity, every inbound lead with a missing job title or company, and every deal in Proposal stage with no close date set. Let me filter by rep.

Create an automation that runs every morning at 8am, pulls new HubSpot contacts added in the last 24 hours, scores them against ICP criteria, and posts a Slack message to the assigned rep with account name, score, ICP fit reason, 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 owner assignments on a schedule. This becomes the base dataset every qualification rule runs against.

2 Connect Apollo from Starch's integration catalog. When a new lead comes in, the agent queries Apollo live to pull firmographic data — employee count, funding, vertical — that may not be in the form fill.

3 Connect Slack from Starch's integration catalog so automated rep notifications land in the right channel or DM without you copying anything.

4 Start from the Sales Agent CRM template or describe your own qualification app from scratch. Tell Starch your ICP criteria in plain language: company size range, verticals, geographies, any disqualifying signals like prior churn or existing customer status.

5 Tell Starch to add a duplicate-detection rule: 'Flag any inbound lead where the email domain or company name already exists as a HubSpot contact or deal, and show the most recent stage and close date of that existing record.'

6 Define your territory routing logic in natural language. For example: 'Assign leads with a US East billing address to reps in the Enterprise East group; assign SMB leads under 100 employees to the SMB pool. Pull rep assignments from the HubSpot owner field.'

7 Build the morning automation: Starch pulls new HubSpot contacts from the last 24 hours, runs the ICP score, and posts a Slack brief to the assigned rep. The brief includes company name, employee count from Apollo, ICP score with the top reason, and a direct link to the HubSpot record.

8 Build the hygiene dashboard: stale open deals with no activity in 14+ days, leads with missing qualification fields, and Proposal-stage deals with no close date. Add a rep filter so you can use it in forecast prep without generating a new report every week.

9 Add a manual trigger to the qualification app so any rep can paste in a company name or domain and get an instant ICP score mid-call, without pinging you on Slack.

10 Set a weekly automation that posts a hygiene summary to your RevOps Slack channel: count of unworked inbound leads, count of stale opps, and count of deals missing required fields — so you have the data before anyone asks.

11 As your ICP definition changes, update the qualification criteria in Starch in plain language. No one needs to touch the scoring Sheet or rebuild a Zapier flow.

12 Use the CRM app to build a qualification audit view: every lead scored in the last 30 days, the score it received, whether it was contacted, and what stage it reached — so you can tune the ICP model with actual outcome data.

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 inbound spike after a product launch

Sample numbers from a real run

Meridian Logistics (inbound form fill, 210 employees, freight SaaS)	0
Cascade Financial (duplicate — Closed Lost Nov 2025, same domain)	0
Thornfield HR Tech (ICP match, Apollo confirms 180 employees, Series B)	0
Solo freelancer — disqualified (1 employee, personal Gmail)	0

Your product launch drives 47 inbound form fills in 72 hours. Normally this means two days of manual triage. With the qualification app running, Starch processes each lead against your ICP the moment it appears in HubSpot. Meridian Logistics scores 82/100 — employee count and vertical match, US-based, no prior history — and the rep assigned to the freight vertical gets a Slack message within minutes with the account brief and HubSpot link. Cascade Financial scores 15/100 because Starch surfaces the Closed Lost deal from November 2025 with a note that the contact churned after two months; the rep gets that context before making a single call. Thornfield HR Tech scores 91/100 — Apollo confirms a Series B close in January, 180 employees, a VP of People as the submitter — and it goes to your top enterprise rep with full firmographic context already attached. The solo freelancer is automatically tagged Disqualified with the reason logged in HubSpot. Out of 47 leads, 11 are qualified and routed, 8 are flagged as duplicates or prior churns, and 28 are auto-disqualified. You spend 20 minutes reviewing exceptions instead of two days processing everything by hand. The hygiene dashboard the following Monday shows zero unworked qualified leads from the launch week — which is a first.

Measurement

How you'll know it's working

Lead-to-qualified rate by channel (what share of inbound form fills pass ICP scoring)

Time-to-first-contact on qualified inbound leads (hours from form fill to rep activity logged in HubSpot)

Duplicate and recycled-lead rate (what share of inbound leads are already in HubSpot as prior contacts or closed deals)

Hygiene score: percentage of open opportunities with all required fields populated and activity in the last 14 days

Qualification override rate (how often reps manually flip a disqualified lead — signals your ICP criteria need tuning)

Comparison

What this replaces

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

HubSpot Workflows + manual scoring properties

HubSpot workflows can route leads and set field values, but building ICP scoring logic requires property-based branching that breaks every time criteria change — you're the one rebuilding it, not describing it.

Salesforce + Einstein Lead Scoring

Einstein scoring is powerful but requires a Salesforce admin to configure, a training dataset to be meaningful, and a license tier most small teams don't have — and it still won't cross-reference Apollo or deduplicate against closed-lost history automatically.

Apollo sequences + manual HubSpot sync

Apollo is good at finding and sequencing leads, but the qualification handoff to HubSpot is still manual or reliant on a Zapier flow you maintain — there's no unified view of ICP score, duplicate history, and rep assignment in one place.

Google Sheets scoring model + Zapier routing

Fast to set up for one criteria set, but the Sheet breaks when ICP changes, Zapier adds per-task cost that scales badly with volume, and neither tool surfaces HubSpot context like prior deal stage or close date alongside the score.

On Starch RECOMMENDED

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

We use Salesforce, not HubSpot. Does this work?

Yes. Salesforce is available through Starch's integration catalog and queried live when your qualification app runs. The sync behavior is different from HubSpot — HubSpot syncs on a schedule and stores data in Starch, while Salesforce is queried live at runtime — but the qualification logic, routing rules, and hygiene dashboard all work the same way.

What happens when our ICP definition changes mid-quarter?

You update the criteria in Starch using plain language — 'remove freight from our target verticals, add healthcare' — and the app rebuilds the scoring logic. You don't touch a workflow builder, a scoring property in HubSpot, or a conditional branch in a Zap. The change applies to all new leads immediately.

Can Starch write back to HubSpot — update the lead score field, set owner, change deal stage?

Starch's HubSpot sync is read-only for the scheduled data pull. For write-back actions, the agent can reach HubSpot through the integration catalog at runtime and execute updates via the API — but this is worth confirming for your specific write actions when you set up the workflow. Ask Starch to include a write step and it will tell you exactly what it can execute.

Is there a pre-built qualification app in the Starch App Store?

The Sales Agent CRM template is the closest starting point — it connects HubSpot and Apollo and handles deal and contact tracking. Lead qualification scoring is something you describe on top of that foundation. Most RevOps teams describe their ICP criteria directly and let Starch build the scoring logic rather than starting from a generic template.

We're not SOC 2 certified — is Starch?

Starch is not SOC 2 Type II certified today. If your security review requires SOC 2, that's worth knowing upfront. For teams where that's not a blocker, Starch handles the data connections your qualification workflow needs.

Our Apollo data is messy — stale contacts, wrong titles. Will the ICP scoring still work?

Starch queries Apollo live at scoring time, so it gets the current state of the record rather than a cached snapshot. If Apollo itself has stale data, the qualification app will reflect that — you can add a rule that flags leads where Apollo returns no match or low-confidence firmographic data, so a human reviews those rather than auto-routing them.