Sales & CRM

How to run a weekly sales pipeline review as Professional Services Founders

Sales & CRMFor Professional Services Founders2 apps12 steps~24 min to set up

Your pipeline review happens Monday morning, fifteen minutes before the partner call, when someone pastes HubSpot deal names into a Google Sheet and guesses at close probabilities. Half the deals are stale — no one updated them after the proposal went out. You can't see which opportunities have gone quiet because the last email thread is buried in a senior's Gmail. Harvest shows hours by project but nothing by deal stage. Stripe shows invoices but not what's still in negotiation. By the time you've correlated three tabs and two browser windows, you've burned 90 minutes and you still don't know which retainer is at risk of non-renewal.

Build this on Starch → See the apps used

Sales & CRMFor Professional Services Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

A live weekly pipeline view that pulls HubSpot deals, Gmail thread recency, and Stripe invoices into one surface — no manual data entry, no tab-switching

An automated Monday morning summary that tells you which deals have gone quiet, which proposals are past their follow-up window, and which retainers renew in the next 30 days

A CRM that reflects your actual sales stages — discovery, proposal sent, proposal review, contract, retainer — not Salesforce's defaults that no one at a 12-person consultancy uses

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, owners) and syncs your Gmail on a schedule (messages and thread recency). Stripe is synced on a schedule for invoice and subscription data. LinkedIn enrichment runs through browser automation — no LinkedIn API needed. For teams using Google Calendar, Starch syncs your calendar data on a schedule to flag proposal review calls already booked. If you manage deals in a spreadsheet instead of HubSpot, connect Google Sheets from Starch's integration catalog and the agent queries it live.

Prompts to copy

Build me a weekly pipeline review app. Pull deals from HubSpot — show stage, deal value, close date, and days since last Gmail thread. Flag any deal that hasn't had an email touch in more than 10 days. Add a 'retainer renewal' column that shows the next Stripe invoice date for existing clients. Sort by close date ascending. I want this as a table I can walk through on Monday mornings with my partner.

Create a CRM for a 12-person professional services firm. Stages are: Outreach, Discovery Call Booked, Proposal Sent, Proposal In Review, Contract Negotiation, Active Retainer, Churned. Track deal value, probability, primary contact, proposal sent date, and last email date. Enrich contacts with LinkedIn job titles automatically. Let me ask 'which proposals have been sitting for more than 14 days with no response?' and get a real answer.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your deals, contacts, companies, and deal owners on a schedule. Existing pipeline stages, field values, and owner assignments come across; you don't remap your whole CRM on day one.

2 Connect Gmail — Starch syncs message threads on a schedule so the pipeline view can show last-contact date per deal without you manually logging calls. This is the column that tells you which opportunities have gone cold.

3 Connect Stripe — Starch syncs invoices and subscriptions on a schedule. This is where your retainer renewal dates live; surfacing them next to open deals tells you whether a renewal is at risk before the client asks.

4 Open the Sales Agent CRM starter app from the App Store. Fork it and describe your actual stages: Outreach, Discovery, Proposal Sent, Proposal Review, Contract, Active Retainer. Starch rebuilds the schema to match.

5 Tell Starch to add a 'days since last email' column calculated from the synced Gmail threads. Set a highlight rule: any deal over 10 days without a thread gets flagged red in the table.

6 Add a 'retainer renewal' field sourced from Stripe subscription data — pull the next invoice date for each company that already has an active subscription and join it to the deal row.

7 Set up a Monday 8 a.m. automation: 'Every Monday, pull the current HubSpot pipeline, flag deals with no email in 10+ days, list proposals sent more than 14 days ago with no stage change, and show retainers renewing in the next 30 days. Post a summary to our #pipeline Slack channel and email it to me.' Starch runs this without you touching anything.

8 Use the CRM app's natural-language query to prep for the partner call: ask 'Which deals moved stages in the last 7 days?' and 'Which contacts haven't been emailed since the proposal went out?' You get a real filtered list, not a canned report.

9 For LinkedIn enrichment, tell Starch to run contact enrichment on any new deal contact weekly — Starch automates this through your browser, pulling current job titles and company details without a LinkedIn API or Sales Navigator seat.

10 If you track proposal documents in Google Drive or Notion, connect Google Drive or Notion from Starch's integration catalog. Then prompt: 'When I move a deal to Proposal Sent, surface the most recent proposal doc for that client in the deal row.' The agent queries it live when the deal view loads.

11 At the end of each Monday review, mark deal stage updates directly in the Starch CRM. If you need those changes to flow back to HubSpot, note this in setup — Starch's HubSpot sync is read; two-way write-back is worth confirming in your onboarding call.

12 After four weeks, ask Starch: 'Show me average days from Proposal Sent to close for deals we won in the last 90 days, broken down by service line.' Use that number to set your follow-up timing rules going forward.

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 pipeline review — Meridian Strategy Group

Sample numbers from a real run

Vantage Capital Partners (proposal sent Mar 19)	48,000
Holloway Manufacturing (discovery booked, no follow-up)	24,000
Renata Health — retainer renewal May 1	96,000
Caruso & Brandt — contract in negotiation	36,000
Foreland Advisors — proposal 21 days stale	30,000

Monday 8:05 a.m., Meridian's pipeline summary lands in #pipeline. The Vantage Capital proposal went out March 19 — 16 days ago, no email reply, flagged red. Foreland Advisors is 21 days stale; the partner didn't realize because the last thread was in a senior's inbox, not in HubSpot. The Renata Health retainer — $96k ARR — renews May 1, 22 days out; no renewal conversation has been booked. The summary surfaces all three in 40 words. The Monday partner call now takes 20 minutes instead of 90: Vantage gets a follow-up call today, Foreland gets a 'checking in' email from the partner, and Renata's account manager books the renewal QBR before lunch. Holloway Manufacturing shows zero email activity since the discovery call — the deal owner thought someone else was following up. Total at-risk value identified before 9 a.m.: $174,000.

Measurement

How you'll know it's working

Proposals sent with no stage change in 14+ days (stale proposal count)

Average days from Proposal Sent to close, by service line

Retainers renewing in the next 30 days and whether a renewal conversation is booked

Weighted pipeline value by stage (probability-adjusted, not just total deal value)

Deal touch frequency — percentage of open deals with an email thread in the last 10 days

Comparison

What this replaces

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

HubSpot Sales Hub (paid tiers)

HubSpot gives you a full CRM but costs $90–$1,200/month at the tiers that include pipeline reporting, requires an admin to configure properly, and still doesn't pull in Gmail thread recency or Stripe renewal dates without custom workflows or a HubSpot admin.

HubSpot + Google Sheets manual export

Free but produces a snapshot, not a live view — the sheet is wrong by Tuesday and someone has to refresh it every week, which is exactly the 90-minute problem you started with.

Kantata / Projector / Deltek (enterprise PSA)

Built for 200-person firms with a dedicated ops team; implementation takes a quarter, pricing starts in the tens of thousands annually, and none of them are designed for a founder who is also the primary rainmaker.

Monday.com or ClickUp CRM

Good for project tracking but weak on sales pipeline specifics — no native Stripe invoice visibility, no Gmail thread recency, and you'll spend more time configuring automations than running your pipeline review.

Notion CRM (homegrown)

Flexible and cheap, but manual — deal stages don't update themselves, LinkedIn enrichment doesn't run automatically, and there's no Monday morning summary unless you build it yourself, which is the time you don't have.

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 HubSpot today. Does Starch replace it or sit on top of it?

Starch sits on top of it. HubSpot keeps doing what HubSpot does; Starch syncs your deal data on a schedule and builds the views and automations you'd otherwise need a HubSpot admin to configure. If you want to move your CRM into Starch entirely and drop the HubSpot subscription, you can do that too — the CRM app lets you describe your exact stages and fields, and Starch builds it against your data.

Can Starch write deal updates back to HubSpot, or is it read-only?

Starch's HubSpot sync reads your deals, contacts, companies, and owners on a schedule. Two-way write-back is worth discussing with the Starch team during onboarding — the honest answer is that the scheduled sync today is read. If you want a workflow where Starch is the primary CRM and HubSpot becomes secondary or drops off, that's the cleaner setup right now.

We don't use HubSpot — our pipeline is in a Google Sheet. Can Starch still work?

Yes. Connect Google Sheets from Starch's integration catalog and the agent queries it live when your pipeline view loads. You'd describe your column names ('Stage is column C, Deal Value is column E, Close Date is column F') and Starch builds the review surface on top of it. You can migrate that data into a Starch CRM app at any point if you want something more structured.

Is Starch SOC 2 certified? We have clients who ask about data security.

Not yet — Starch is not SOC 2 Type II certified today. If a client security review requires a SOC 2 report, that's worth knowing upfront. For most 12-person consultancies whose clients aren't running formal vendor security audits, this doesn't come up. It's on the roadmap.

How does LinkedIn enrichment work without a Sales Navigator seat?

Starch automates LinkedIn through your browser — no API, no Sales Navigator required. It logs into LinkedIn as you, navigates to each contact's profile, and pulls current job title, company, and connection data. Independent browser sessions run per contact so one failure doesn't block the rest. You do need a LinkedIn account; Starch uses it on your behalf.

Can the Monday pipeline summary post to Slack automatically?

Yes. Tell Starch: 'Every Monday at 8 a.m., run the pipeline review and post the summary to #pipeline.' Starch connects to Slack and posts it. You can also have it email the summary to the partner group, or both. The automation runs on a schedule without anyone triggering it.

What if our Stripe invoices don't map cleanly to HubSpot deal names?

This is common at professional services firms where invoices are issued to a company but deals are tracked by project name. When you set up the integration, tell Starch how to match them — for example, 'match Stripe invoices to HubSpot companies by company name' or 'I'll add a client ID field to both.' Starch can handle fuzzy matching or you can define the join logic in plain language.