Sales & CRM

How to qualify inbound leads as Professional Services Founders

Sales & CRMFor Professional Services Founders3 apps10 steps~20 min to set up

You get 20 inbound inquiries a month from your website, referrals, and LinkedIn. Half are tire-kickers or budget-mismatches you won't know about until you've spent 90 minutes on a discovery call. Your qualification process lives in a HubSpot deal you remember to update when you have time, a Gmail thread you have to hunt for, and a mental checklist of the five questions that actually predict whether a prospect will close. A senior consultant ends up doing admin triage because you haven't had time to codify what 'good' looks like. By the time a lead hits your calendar, you've already lost 45 minutes of billable time deciding whether they were worth the slot.

Build this on Starch → See the apps used

Sales & CRMFor Professional Services Founders3 apps10 steps~20 min to set up

Outcome

What you'll set up

An automated lead-scoring app that reads every new HubSpot deal and connected Gmail thread, scores the lead against your qualification criteria, and surfaces the top three things you need to know before the discovery call

A qualification checklist that auto-populates from email history, company size signals, and any enrichment data you already have — so you walk into every call with context, not a blank page

A triage queue in Starch that ranks open inbound leads by fit score and flags which ones need a reply today before they go cold

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

Data sources & config

Starch connects directly to HubSpot (scheduled sync — contacts, companies, deals, and owners update on a schedule) and Gmail (scheduled sync — message threads and labels sync on a schedule so the agent can read conversation history). Lead enrichment pulls LinkedIn profile data through browser automation — no LinkedIn API needed. All three data sources land in one place so the qualification app has full context on each lead without you copying anything manually.

Prompts to copy

Build me a lead qualification app that pulls every new deal from HubSpot, reads the last five Gmail threads with that contact, and scores them 1-10 on budget clarity, timeline urgency, decision-maker access, and fit with my three service lines: strategy, implementation, and managed services. Show me the score, a one-sentence summary, and the single most important open question for each lead.

Add a triage queue to the top of the app that sorts all open inbound leads by score, highlights anyone I haven't responded to in more than 48 hours, and shows the next step I've committed to.

Set up an automation that emails me every morning at 8am with the three highest-priority inbound leads and one suggested reply draft for each unanswered thread.

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

Walkthrough

Step-by-step

1 Connect HubSpot to Starch — Starch syncs your contacts, companies, deals, and deal owners on a schedule, so every new inbound deal is visible in Starch within minutes of it entering your pipeline.

2 Connect Gmail — Starch syncs your message threads on a schedule, giving the agent full conversation history so it can read what the prospect actually said, not just what you put in the HubSpot notes field.

3 Open the Sales Agent CRM starter app from the App Store and fork it — the pre-built template gives you contacts, deals, and email context out of the box, and you customize from there.

4 Describe your qualification rubric in natural language: tell Starch your scoring dimensions (budget, timeline, decision-maker, service-line fit), your three service lines, and any deal-breaker signals you've learned over the years (e.g., 'single-person teams rarely convert').

5 Tell Starch to enrich each new lead's company profile from LinkedIn — Starch automates this through your browser, no LinkedIn API needed, and writes the enrichment data back into the lead record.

6 Set the triage queue to surface leads with scores above 7 at the top and flag anyone you haven't responded to in 48 hours — this replaces the mental overhead of remembering who needs a nudge.

7 Configure the morning briefing automation: every weekday at 8am, Starch reads all open inbound leads, re-scores any that have had new email activity overnight, and emails you a ranked list with one draft reply per unanswered thread.

8 Add a 'qualification call notes' field to the deal record and tell Starch to update the score after a call based on what you log — so your scoring model improves over time without a separate tool.

9 Set a follow-up reminder automation: if a lead scores above 6 and you haven't logged any outbound activity in five business days, Starch surfaces it in your triage queue with a suggested re-engagement message pulled from the email history.

10 Once a lead clears qualification, tell Starch to move the deal to your 'Proposal' stage in HubSpot and create a task for proposal assembly — keeping your existing HubSpot workflow intact while Starch handles the triage upstream.

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 cohort — 18 leads, 3 proposals sent in 6 days

Sample numbers from a real run

Leads received (April 1–14)	18
Auto-scored by Starch before discovery	18
Scored 7+ (high fit)	6
Scored 4–6 (nurture)	8
Scored under 4 (low fit, no call)	4
Discovery calls held	6
Proposals sent	3
Estimated triage hours saved vs. manual process	5

In the first two weeks of April, 18 inbound inquiries landed across your website contact form, two referrals from existing clients, and five LinkedIn messages. Before Starch, you would have spent roughly 30 minutes per lead just figuring out whether they were worth a call — reading the email thread, checking the company on LinkedIn, deciding if their budget language sounded real. With Starch running qualification, every lead was scored within two hours of entering HubSpot. The four leads who scored under 4 — two consultants looking for subcontracting work, one startup with a $5k budget asking for a six-month strategy engagement, one prospect who wanted 'a quick call to pick your brain' — got a polite email from your assistant template and never touched your calendar. The six leads who scored 7 or above got a full brief in your Starch triage queue: score, one-sentence company summary pulled from LinkedIn via browser automation, three key qualification signals from the Gmail thread, and the one open question to press on. You walked into each discovery call knowing the answer to 'do they have budget and authority?' before you'd said hello. Three proposals went out by April 7. You saved an estimated five hours of triage work across the cohort — roughly half a day you billed to an active client instead.

Measurement

How you'll know it's working

Lead-to-discovery-call conversion rate (% of inbound leads worth a call, tracked by score threshold)

Time from lead entry to first qualified response (target: under 4 hours for 7+ scored leads)

Discovery-call-to-proposal rate (are you qualifying hard enough upstream?)

Triage hours per cohort (senior consultant time spent on admin qualification, tracked monthly)

Pipeline accuracy at month-start (do your HubSpot deal stages reflect reality, or are you surprised at close?)

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 is property-based and requires a marketing hub upgrade; it doesn't read email thread content or enrich from LinkedIn automatically, so you're scoring on form-fill data rather than actual conversation signals.

Manual spreadsheet + weekly pipeline review

Zero cost and zero setup, but qualification lives in someone's head — usually yours — which means leads sit unscored until you have a free hour, and nothing improves over time.

Apollo.io sequences

Apollo is strong for outbound prospecting; for inbound qualification of warm referrals and website leads, it adds a tool and workflow your team has to learn without solving the triage-and-scoring problem on existing pipeline.

Kantata / Projector / Deltek

Enterprise PSA tools include CRM-adjacent features but are priced for 200-person firms, take months to configure, and are far more than you need for a 12-person shop trying to triage 20 leads a month.

On Starch RECOMMENDED

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

Does Starch replace HubSpot, or does it sit on top of it?

It sits on top. Starch syncs your HubSpot deals, contacts, and companies on a schedule — your team keeps using HubSpot however they already do. Starch reads that data, runs the qualification logic, and can write activity or move deal stages back to HubSpot via the integration catalog. You're not migrating anything.

What if my qualification criteria are different from a standard sales framework?

That's the point. You describe your criteria in plain language — 'score leads higher if they mention a specific compliance deadline' or 'flag any prospect from the financial services sector because we have a conflict check process' — and Starch builds the scoring logic around what you tell it. You're not configuring dropdowns in a CRM admin panel.

Can Starch read emails that came in before I connected Gmail?

Starch syncs Gmail on a schedule and can read historical messages up to the depth the sync covers. For most recent inbound leads, the thread history will be available. If you have leads from months ago, older threads may be outside the sync window — worth checking before you rely on historical scoring for cold pipeline.

Is Starch SOC 2 certified? We sometimes handle prospect data that's sensitive.

Not yet — Starch is not SOC 2 Type II certified today. If compliance certification is a hard requirement for your firm or a client's vendor review, that's worth knowing upfront. It's on the roadmap.

How does the LinkedIn enrichment work without a LinkedIn API?

Starch automates LinkedIn through your browser — no API needed. It navigates LinkedIn the way you would, reads the profile data, and writes it back to the lead record. This is a first-class Starch pattern, not a workaround. The same approach works for any website you can log into.

What happens to leads that score low — does Starch send them an automatic rejection?

Only if you tell it to. By default, low-scoring leads go into a separate queue in your triage view. You can set up an automation to send a templated response (drafted by Starch from your inbox history), but you approve the logic when you build it. Nothing goes out without your sign-off on the rules.