Sales & CRM

How to qualify inbound leads as Small Customer Success Teams

Sales & CRMFor Small Customer Success Teams2 apps10 steps~20 min to set up

Your team of three is handling 250 B2B accounts. When a new lead comes in through your website or gets routed from sales, nobody has a clean process to figure out whether this person is actually a fit before the kickoff call. You're scanning HubSpot for deal context, checking Gmail threads to see if anyone on the team already touched them, and asking the AE on Slack. Half the time the account goes into onboarding before anyone has confirmed they match your ICP, their use case is viable, or their contract tier makes a renewal conversation worth having. The bad fits churn at month three and you wonder why your NRR looks the way it does.

Build this on Starch → See the apps used

Sales & CRMFor Small Customer Success Teams2 apps10 steps~20 min to set up

Outcome

What you'll set up

A qualification app that pulls HubSpot deal data and Gmail thread history into one surface, scores each inbound account against your ICP criteria, and flags the ones worth a kickoff call before your team wastes an hour on a bad fit.

An automated triage flow that drafts an outbound clarifying email for any lead missing key qualification fields — use case, seat count, existing tools — so you get the answers you need without a separate discovery call.

A shared view your whole CS team can check each morning that shows every pending lead, their qualification status, the last email touchpoint, and a recommended next action — no Slack back-and-forth required.

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 Email Agent

Data sources & config

Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and owner assignments. Starch also syncs your Gmail on a schedule so email thread history is available inside the qualification app. Intercom is connected from Starch's integration catalog; the agent queries it live when the app needs support ticket history to check whether a lead has already been a user before.

Prompts to copy

Build me a lead qualification tracker that pulls from HubSpot — contacts, companies, and deal stage — and scores each new account against these criteria: annual contract value above $5k, use case is team collaboration or workflow automation, company headcount between 20 and 500, and no overlap with existing churned accounts. Show me a score out of 10 for each lead and flag anything below 6 for review.

When a new lead scores below 7 on qualification, draft a short email to that contact asking three questions: what workflow problem they're trying to solve, how many people on their team will use the product, and whether they've tried any similar tools before. Pull the contact's name and company from HubSpot and personalize the opening line based on the most recent Gmail thread with them if one exists.

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 deal stages on a schedule. Every new inbound lead that lands in HubSpot is automatically visible in Starch.

2 Connect Gmail — Starch syncs your inbox on a schedule so the qualification app can surface whether anyone on your team has already emailed this contact and what was said.

3 Connect Intercom from Starch's integration catalog. The agent queries it live to check whether this contact has submitted a support ticket before, which tells you whether they've been a user at a prior company.

4 Describe your ICP scoring logic to Starch in plain language — deal size, industry, use case, headcount range, whatever your team has actually found predictive. Starch builds the scoring model as part of the app.

5 Set up the qualification tracker view: one row per new lead, columns for ICP score, deal stage, last email date, last email sender (to prevent two CS reps emailing the same account), and a recommended action field.

6 Configure the Email Agent to draft a qualification questionnaire for any lead that comes in below your score threshold. The prompt pulls contact name and company from HubSpot and personalizes based on the most recent Gmail thread.

7 Set an automation that runs every morning at 8am, checks for new HubSpot leads added in the last 24 hours, scores them, and Slacks your team a summary: 'Three new leads today. Two are strong fits. One needs qualification email — draft ready for your review.'

8 For leads that score well, the app generates a kickoff call prep note: account name, deal size, use case as described in the HubSpot deal notes, and any prior Intercom support history — so whoever takes the call walks in knowing the account.

9 Add a disqualification logging field to the app. When your team marks a lead as not a fit, they select a reason from a dropdown you define. Starch stores this and the app can surface patterns over time — 'seven of your last ten disqualified leads came from the same referral channel.'

10 At the end of each week, ask Starch to summarize: leads received, qualification rate, average score of accepted vs rejected, and which ICP criteria are being missed most often. This is your CS team's input into the next sales-to-CS handoff conversation.

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 surge — 18 leads in one week

Sample numbers from a real run

Meridian Logistics	8,400
Sprout Analytics	3,200
Coldwell Partners	12,000
NovaTech Services	1,800
Fieldwork Co.	6,500

Your team got 18 inbound leads the week of April 7th after a product mention in a newsletter. Without a qualification process, that would have meant 18 kickoff calls scheduled by whoever picked up the Calendly notification first. Instead, Starch scored all 18 against your ICP overnight. Eleven scored above 7 — Meridian Logistics at $8,400 ACV and Coldwell Partners at $12,000 both looked strong, matching your ideal headcount range (75–400 employees) and use cases that matched your playbook. Sprout Analytics scored a 5 — the deal size was too small at $3,200 and their team was two people. The Email Agent drafted a qualification questionnaire for them automatically; the question about seat count came back confirming they weren't a fit, saving your team an hour-long discovery call. NovaTech Services scored a 4 — a prior Intercom support record showed they'd been a user at a company that churned six months ago for product fit reasons. That flag surfaced in the qualification view before anyone touched the account. Your team took seven kickoff calls that week instead of eighteen. Four of those seven converted to active onboarding. That's a conversion rate your team can actually sustain.

Measurement

How you'll know it's working

Lead-to-kickoff conversion rate (percentage of inbound leads that actually warrant a call, before and after scoring)

Time from lead creation in HubSpot to qualification decision (target: same business day)

Churn rate by ICP score band (do your low-scoring accounts churn faster than high-scoring ones — if yes, the model is working)

CS team hours spent per qualified lead (discovery calls, email back-and-forth, Slack coordination)

Disqualification reason distribution (which ICP criteria are failing most, fed back to sales for sourcing guidance)

Comparison

What this replaces

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

Gainsight

Built for teams with a CS-ops person to configure it — six-figure contract, months to implement, and you'd still need to build the inbound qualification logic on top of it.

HubSpot Sales Hub (advanced tiers)

Scoring exists but it's based on HubSpot's fields and logic — you can't pull in Gmail thread recency or Intercom history as scoring inputs without significant custom work.

Manual process in Google Sheets + Slack

Your team is probably doing this today — it breaks down the week you get 15 leads at once and there's no audit trail for why accounts were accepted or rejected.

ChurnZero

Strong on churn risk signals for existing customers, but not designed for pre-onboarding lead qualification and pricing assumes a much larger CS team than three people.

On Starch RECOMMENDED

One platform — crm, email agent 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. Does Starch replace it?

No. Starch connects to HubSpot — it syncs your contacts, companies, deals, and deal stages on a schedule — and lets you build surfaces on top of that data that HubSpot doesn't ship. Your HubSpot stays your system of record. Starch is where you build the qualification logic, the scoring view, and the email drafting workflow that HubSpot doesn't give you out of the box.

What if our leads come in through Intercom, not HubSpot?

Connect Intercom from Starch's integration catalog — the agent queries it live. You can describe a qualification app that reads from both Intercom and HubSpot so the scoring view combines CRM deal data with support ticket history. If a lead reaches you through a form tool or a channel Starch doesn't have a direct connector for, Starch can automate the data collection through your browser — no API needed.

Will Starch store our customer data? We're cautious about that.

Starch stores the data it syncs from scheduled-sync providers like HubSpot and Gmail in its database so your apps can query it. Starch is not SOC 2 Type II certified today — that's worth knowing if your contracts have compliance requirements. It's on the roadmap. For live-queried apps like Intercom, data is queried in the moment and not stored in Starch.

Can three people actually set this up without a RevOps or CS-ops person?

Yes — that's the specific design choice Starch makes. You describe what you want in plain language and Starch builds the app. The ICP scoring criteria, the qualification fields, the email draft templates — you define them in natural language prompts, not configuration menus. If you can describe your current manual process, you can build a Starch app that automates it.

What if our qualification criteria change after we build the app?

Tell Starch in plain language. 'Change the minimum ACV threshold from $5k to $8k and add a field for whether the account is in the healthcare vertical — weight that negatively.' Starch updates the app. You're not editing a scoring formula in a settings menu; you're describing the change the same way you'd explain it to a new team member.

Does Starch have a pre-built CS app for this?

The closest live templates are the CRM app (good for managing contacts, deals, and email thread history) and the Email Agent (for drafting and triaging qualification outreach). There's no pre-built 'inbound lead qualification for CS teams' template today, but you'd describe what you want and Starch builds it in minutes — the templates are just a starting point, not a ceiling.