Sales & CRM

How to run a weekly sales pipeline review as Chief of Staff and Founder's Office

Sales & CRMFor Chief of Staff and Founder's Office2 apps12 steps~24 min to set up

You run the weekly pipeline review because the CEO trusts you to catch what the sales team glosses over. But 'running it' means exporting a HubSpot report, pasting it into a Google Sheet, cross-referencing it against last week's version, chasing three reps on Slack for deal notes, and then reformatting everything into a slide before the Monday standup. By the time you've done all that, you've spent three hours producing a review that takes twenty minutes to run. You're not a sales ops person — you just ended up owning this because nobody else connects the dots between the pipeline, the revenue forecast, and what the board is going to ask about in six weeks.

Build this on Starch → See the apps used

Sales & CRMFor Chief of Staff and Founder's Office2 apps12 steps~24 min to set up

Outcome

What you'll set up

A live pipeline dashboard that pulls from HubSpot on a schedule and surfaces deal movement, stage velocity, and rep activity without manual exports

A weekly digest automation that writes a plain-English pipeline summary — what closed, what slipped, what needs CEO attention — and drops it in Slack every Monday morning

A board-ready pipeline view that maps current deals to quarterly revenue targets so you can answer 'are we going to hit the number?' before anyone asks

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. Starch also syncs your Gmail on a schedule so email thread context surfaces inside the pipeline view. Slack is connected from Starch's integration catalog and queried live when the Monday digest automation fires. Google Calendar is synced on a schedule so the automation knows when your pipeline review meeting is and can pre-populate the brief.

Prompts to copy

Build me a weekly sales pipeline dashboard using our HubSpot data. Show deals by stage, owner, and close date. Flag any deal that hasn't had activity in more than 10 days, any deal where the close date has slipped more than twice, and any deal above $50k that's been in the same stage for more than 3 weeks. Group by rep and by quarter.

Every Monday at 7am, pull last week's HubSpot pipeline activity and send me a Slack message summarizing: how many deals moved stages, what closed or was lost, which reps had the most activity, and what our current pipeline coverage is against the Q3 revenue target. Include the three deals I should flag for the CEO.

Build me a CRM view that shows our 20 largest open deals with the last email thread subject pulled from Gmail, the HubSpot stage and owner, and a field where I can add a one-line status note before the weekly review.

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

Walkthrough

Step-by-step

1 Connect HubSpot to Starch — Starch syncs your deals, contacts, companies, and owners on a schedule, so every time your pipeline app runs it's reading current data, not a last-Tuesday export.

2 Connect Gmail — Starch syncs your inbox on a schedule and links email threads to deals by contact match, so you can see the last conversation on any deal without leaving the pipeline view.

3 Connect Slack from Starch's integration catalog so the Monday digest automation can post directly to your #exec or #pipeline channel.

4 Connect Google Calendar — Starch syncs your calendar so the automation can anchor the digest delivery to 30 minutes before your actual pipeline review meeting, not an arbitrary time.

5 Open the Sales Agent CRM app from the App Store as your starting point, then describe how your pipeline actually works — your stage names, the fields that matter (e.g., deal source, broker contact, competitor in play), and which rep owns what.

6 Add a 'deal health' layer by telling Starch: 'Flag any deal where close date has moved more than once, or where the last activity is older than 10 days.' This becomes a persistent filter in your dashboard.

7 Set up the Monday morning automation: describe the pipeline summary format you want — closed/lost last week, stage movement, pipeline coverage ratio, and a shortlist of deals needing CEO attention — and tell Starch to post it to Slack at 7am every Monday.

8 Build a board-prep view that maps open pipeline to quarterly target: tell Starch 'Show me total pipeline value by expected close month, weighted by stage probability, compared against our Q3 revenue target of $X.' Update the target number each quarter.

9 Add a pre-meeting brief step: tell Starch 'Before my Monday pipeline review, generate a one-page summary of the five deals most likely to close this month and the five most at risk, with the last Gmail thread subject for each.'

10 Share the dashboard link with the CEO and relevant sales leads so they come to the Monday review having already read the numbers — you stop being the person who emails a PDF at 8:55am.

11 After the first two weeks, review which deal flags were accurate and which were noise; adjust the activity-threshold and amount-threshold parameters by telling Starch to update the filter rules in plain language.

12 Each quarter, fork the board-prep view into a one-time snapshot you can drop into the investor update — same data, different format, described to Starch as 'a board-ready pipeline summary for Q3 close, formatted for a slide appendix.'

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

Q3 2026 Pipeline Review — Week of July 14

Sample numbers from a real run

Meridian Logistics (Enterprise, Stage: Proposal)	120,000
Holloway & Co (Mid-Market, Stage: Negotiation)	48,000
Pinebrook Health (SMB, Stage: Demo Scheduled)	22,000
Deals closed last week (3 deals)	67,500
Deals slipped from July close (2 deals)	88,000
Total Q3 pipeline (weighted)	390,000
Q3 revenue target	450,000

It's Sunday evening. The Monday pipeline review is at 9am. In the old world, you'd be building a HubSpot export right now. Instead, the Starch automation already fired at 7am — you have a Slack message that reads: '3 deals closed last week ($67.5k). 2 deals slipped from July close ($88k combined — Meridian and Holloway). Current weighted pipeline is $390k against a $450k Q3 target, giving you 87% coverage. Deals needing CEO attention: Meridian Logistics ($120k, no activity in 14 days, close date slipped once) and Holloway & Co ($48k, three-way competitive situation, last email from rep was 11 days ago).' You walk into the Monday review, open the live dashboard on your laptop, and the CEO asks about Meridian. You already have the last Gmail thread subject pulled in: 'Re: Legal review timeline — following up.' You flag it for immediate outreach. The whole review runs 22 minutes. The board appendix for the July investor update will use the same data — you'll describe the format to Starch on Thursday and have a slide-ready pipeline table in about four minutes.

Measurement

How you'll know it's working

Pipeline coverage ratio: weighted open pipeline vs. quarterly revenue target (you want to see 3x minimum six weeks out)

Stage velocity: average days deals spend in each stage, tracked week-over-week to catch where deals are stalling

Deal slip rate: percentage of deals where close date moved at least once — your leading indicator of forecast accuracy

Rep activity rate: number of logged activities (emails, calls, meetings) per rep per week, surfaced from HubSpot and Gmail

Days since last contact on deals above $25k: your early-warning system for deals going cold before anyone notices

Comparison

What this replaces

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

HubSpot native reports + manual export to Google Sheets

HubSpot's built-in reports are decent but static — you still have to pull them, paste them somewhere, and write the narrative yourself every single week; Starch automates the pull, the narrative, and the Slack delivery.

Salesforce + Tableau or Looker

Powerful if you have a RevOps person to maintain it, but at 150 people you probably don't — and standing up a Tableau environment for one weekly review is months of setup and ongoing admin overhead you can't justify.

Notion database manually updated by sales ops or you

Notion is where your docs live and it's fine for that, but it has no live HubSpot sync — you're either copying data by hand or paying for a third-party sync tool that breaks every time HubSpot updates its API.

Excel / Google Sheets pipeline tracker

Every chief of staff has one of these; it works until it doesn't — it goes stale the moment someone forgets to update it, and you end up being the person who maintains it manually while also being the person who needs to trust it.

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

Does Starch actually stay in sync with HubSpot, or is it a one-time import?

Starch syncs your HubSpot data on a schedule — deals, contacts, companies, and owners update automatically. Your pipeline dashboard reflects current data each time it loads; you're not looking at a snapshot from last Tuesday.

I don't just use HubSpot — our sales team also uses Gmail heavily. Can Starch connect those threads to deals?

Yes. Starch syncs your Gmail on a schedule and can match email threads to deals by contact. When you build your pipeline view, you can ask Starch to surface the last email thread subject for each deal so you don't have to tab between HubSpot and Gmail to get context.

Can Starch post the weekly pipeline digest to a specific Slack channel automatically?

Yes. Connect Slack from Starch's integration catalog, set up the Monday morning automation, and tell Starch which channel to post to. The automation can be scheduled (e.g., 7am every Monday) or triggered manually if you want to run an ad-hoc review mid-week.

What if our pipeline stages or field names are different from whatever the default CRM template uses?

That's the point of Starch's natural-language app authoring. You describe your actual stages — 'Qualified, Proposal Sent, Legal Review, Closed Won, Closed Lost' — and the dashboard and automations are built around those, not around a template someone else designed. You can also fork the Sales Agent CRM from the App Store and tell Starch what to change.

Is my HubSpot and Gmail data stored in Starch, or just queried when I open the app?

HubSpot and Gmail are scheduled-sync providers — Starch stores a copy of that data in its database, refreshed on a schedule. This is what makes the Monday automation possible: the digest can run at 7am without you opening anything. It also means Starch isn't hitting HubSpot's API live every time you load a dashboard, which keeps things fast. Worth knowing: Starch is not a long-horizon data warehouse, so it's not designed to store years of historical pipeline archives — it's a live operational surface.

We're not SOC 2 certified yet — is Starch?

Starch is not SOC 2 Type II certified today. If that's a hard procurement requirement for your company or your investors, that's worth knowing upfront.

Can I use this to prep the pipeline section of a board deck, not just run the internal review?

Yes, and this is one of the more useful patterns for a chief of staff role. You can describe a board-ready pipeline view to Starch — 'show me total pipeline by expected close month, weighted by stage probability, compared against our Q3 target, formatted for a slide appendix' — and get a structured output you can drop directly into your investor update prep.