Sales & CRM

How to run a weekly sales pipeline review as Small RevOps Teams

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

Your weekly pipeline review prep looks like this: export HubSpot deals to CSV, paste into a Sheets model someone built 18 months ago, manually add the Apollo sequence data that never makes it into HubSpot, screenshot the funnel, drop it into slides, and send it to the CRO by 9am Friday. One of your 30 reps updated their deal stage at 8:55am and now the snapshot is wrong. You spend the first 10 minutes of every forecast call explaining the data instead of talking about the deals. You have two people. You cannot also be the person who builds a better system while running the current broken one.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A live pipeline dashboard that pulls HubSpot deals, Apollo sequence status, and Gmail thread activity into one view — no more Friday morning CSV gymnastics

Automated hygiene rules that flag stale opportunities, missing close dates, and stage mismatches before the forecast call, not during it

A weekly pipeline digest that lands in your inbox (and optionally in Slack) with the three numbers the CRO will ask about, already calculated

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 data on a schedule — deals, contacts, companies, owners, and activity history come in automatically and stay current. Apollo contacts and sequence data are pulled live from Starch's integration catalog when your pipeline app runs. Gmail is synced on a schedule so email thread activity shows up against deal records without manual logging. Salesforce users can connect Salesforce from Starch's integration catalog and the agent queries it live. Slack is available from the integration catalog for delivering your weekly digest.

Prompts to copy

Build me a weekly pipeline review dashboard that pulls all open deals from HubSpot, shows stage, ARR, close date, days since last activity, and rep owner. Flag any deal that hasn't had an activity logged in 14 days or has a close date in the past. Group by rep and by stage. Let me filter by territory.

Create a Monday morning automation that scans all open HubSpot deals, identifies ones with no activity in the last 14 days or a close date that has passed without a stage change, and sends me a Slack message listing them with deal name, rep, and ARR.

Build me a forecast roll-up view that shows weighted pipeline by stage using our standard stage probabilities (Discovery 20%, Demo 40%, Proposal 60%, Verbal 80%, Closed Won 100%), broken down by rep and territory, with a comparison to the same week last month.

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 owner data on a schedule. This becomes the foundation of your pipeline view and replaces the Friday CSV export.

2 Connect Apollo from Starch's integration catalog. The agent queries sequence enrollment and activity data live when your pipeline app runs, so you can see whether a rep's 'active' deal has actually had any touches this week.

3 Connect Gmail — Starch syncs your email threads on a schedule, which means deal records show last email date without reps having to log anything manually.

4 Start from the Sales Agent CRM template in the App Store, then describe the fields that actually matter to your team: territory, segment, sequence status, days since last touch, and weighted ARR.

5 Tell Starch your hygiene rules in plain language: what counts as stale, what close date slippage looks like, which stage transitions require a next step logged. Starch builds the flag logic; you approve it.

6 Build the forecast roll-up by describing your stage probability model. If your CRO uses a different weighting for enterprise vs. SMB, say that — Starch will build the split view.

7 Set up the Monday hygiene automation: tell Starch to scan open deals every Monday at 7am, identify violations of your hygiene rules, and post a Slack message to the RevOps channel with deal name, rep, ARR, and what's wrong.

8 Set up the Friday forecast digest: tell Starch to roll up weighted pipeline by rep and territory as of Thursday EOD and send it to you and the CRO by 8am Friday — formatted the way your forecast call actually runs, not how HubSpot thinks it should look.

9 For the forecast slide, describe what you need: 'a 5-slide pipeline summary showing this week's weighted pipeline vs. last week, the top 10 deals by ARR, and any deals that moved backward in stage.' Starch builds it from the connected data.

10 Wire the 'can you pull me a list of...' requests as saved views — describe each one once, save it with a name, and share the link with the rep or manager who keeps asking. You answer that Slack message once.

11 Review the dashboard with the CRO on the forecast call. When something looks wrong, ask Starch in plain language — 'show me all deals in the Proposal stage where the last activity was more than 21 days ago' — and get the answer in the call, not after it.

12 At the end of each quarter, tell Starch to compare closed-won deals against their earliest stage entry dates and sequence touches to surface what your actual conversion patterns look like by rep and source.

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

Q1 2026 Week 11 Pipeline Review — March 13, 2026

Sample numbers from a real run

Open pipeline (all stages)	2,840,000
Weighted pipeline (stage-probability adjusted)	1,138,000
Deals flagged stale (no activity 14+ days)	340,000
Deals with past close date, no stage change	215,000
Closed Won MTD	187,000
Deals moved backward in stage this week	95,000

It's Thursday at 6pm. Last week, this took 90 minutes of manual work Friday morning. This week, the Starch pipeline dashboard has already been live all week — the CRO has had access to the weighted roll-up since Monday. The Monday hygiene automation fired at 7am and posted 11 flagged deals to the RevOps Slack channel: 8 stale opportunities totaling $340K and 3 deals sitting in Proposal past their original close date for a combined $215K. Two of those three reps updated their deals by Tuesday without you having to chase them. Your Friday digest landed at 8am: $1.138M weighted pipeline, down $62K from last week driven by one enterprise deal ($95K ARR) slipping from Verbal back to Proposal. The forecast slide was built by telling Starch 'give me a 5-slide pipeline summary showing weighted pipeline vs. last week, top 10 deals by ARR, and the deals that moved backward' — it took four minutes. The forecast call started with the CRO asking about the Verbal-to-Proposal slip, not about why the numbers didn't match the export.

Measurement

How you'll know it's working

Weighted pipeline by stage and territory (stage-probability adjusted ARR, not raw open pipeline)

Deal hygiene score — percentage of open deals with a logged activity in the last 14 days and a future close date

Stage velocity — average days spent in each stage, by rep and by segment, to find where deals are actually dying

Forecast accuracy — how close your Thursday weighted pipeline call is to actual Friday EOD closed-won, tracked week over week

Backward stage movement — deals that regressed at least one stage this week, by ARR and rep, as a leading indicator of forecast risk

Comparison

What this replaces

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

HubSpot native reporting + Sheets forecast model

You already have this — it's the thing you're trying to get off of. HubSpot reports don't know about Apollo sequence data or Gmail thread recency, so your hygiene view is always incomplete, and rebuilding the Sheets model every time territory changes is a half-day project.

Salesforce + Clari or Gong Forecast

Clari and Gong give you serious forecast intelligence at serious enterprise prices — $30K+ annually — and they require Salesforce as the foundation, which adds its own admin overhead. Built for 200-rep orgs, not a 30-rep team with a 2-person RevOps function.

Airtable or Notion pipeline tracker

Works until it doesn't — they don't sync from HubSpot or Apollo automatically, so you're back to manual imports and the data is always one export behind reality.

Pipedrive + native automations

Pipedrive's built-in automations handle simple triggers but can't compose across Apollo sequence status, Gmail thread data, and Slack delivery in the same workflow without per-seat add-ons and significant configuration work.

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're a HubSpot shop. Does Starch actually stay in sync with deal updates, or is it a point-in-time snapshot?

Starch syncs your HubSpot deals, contacts, companies, and owner data on a schedule — it's not a one-time import. When a rep updates a stage or logs an activity in HubSpot, that change shows up in your Starch pipeline view on the next sync cycle. You're not working from a CSV you pulled Friday morning.

Half our team uses Salesforce, not HubSpot. Can we still build this?

Yes. Connect Salesforce from Starch's integration catalog and the agent queries it live when your pipeline app runs. HubSpot has a deeper scheduled sync (data stored in Starch's database), while Salesforce is queried live — in practice, both work for a weekly pipeline review workflow.

We have Apollo sequences running in parallel with HubSpot. Can the pipeline view show both?

Yes. Connect Apollo from Starch's integration catalog; the agent queries sequence enrollment, step completion, and reply data live when your pipeline app runs. You can build a view that shows, for each deal, whether the associated contact is in an active sequence and when the last sequence touch was — without manually cross-referencing two tools.

What happens if a rep updates a deal while we're on the forecast call? Do we get the wrong number?

The pipeline view reflects the last sync, so there's a window between a rep updating HubSpot and that change appearing in Starch. For a weekly review, this is rarely a problem — the value is in having the full picture from connected sources, not in sub-minute freshness. If you need a live snapshot mid-call, you can ask Starch to re-query HubSpot directly.

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

Starch is not SOC 2 Type II certified today. That's worth knowing before you connect your CRM. If your company requires SOC 2 Type II for any third-party tool that touches deal data, that's a real blocker right now.

We want to keep HubSpot as our CRM — we're not replacing it. Does this still work?

That's exactly the use case. Starch doesn't replace HubSpot — it syncs from it and lets you build the views, hygiene rules, and automations on top that HubSpot's native reporting doesn't give you. Your reps keep working in HubSpot. You get the pipeline visibility you've been trying to build in Sheets.

Can Starch actually send the weekly digest to Slack, or does it just build the dashboard?

Both. Connect Slack from Starch's integration catalog and tell Starch where and when to post. You can configure the Monday hygiene alert and the Friday forecast digest as scheduled automations that post directly to a Slack channel — formatted however your team actually reads it, not in a generic template.