Internal Comms & Meetings

How to run an async standup as Small RevOps Teams

Internal Comms & MeetingsFor Small RevOps Teams3 apps11 steps~22 min to set up

Your async standup today is a Slack message you typed at 8:47am that three reps read, two ignored, and one replied to with a question that spawned a thread nobody closed. You're a two-person RevOps team: one of you is in HubSpot cleaning up pipeline, the other is rebuilding the quota model. There's no shared cadence for what each of you worked on yesterday, what's blocked, and what the reps actually need from you this week. Status updates happen in hallway Slack DMs or get skipped entirely. When the CRO asks on Friday why the forecast deck wasn't ready, nobody has a log of what RevOps was doing. You need a standup that doesn't require a meeting but still produces a real record.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small RevOps Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

A daily async standup that automatically pulls what each RevOps team member did in HubSpot, Apollo, and Gmail — so you're not writing status updates from memory

A Slack digest that lands every morning with the prior day's blockers, the open 'can you pull me a list of...' requests, and what's on deck — without scheduling a call

A searchable log of every standup response so when someone asks what RevOps was doing in the week the territory model broke, you have a timestamped answer

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

Task Manager Email Agent Project Management

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, deals, owners) and connects directly to Gmail so the standup automation can reference what you actually touched. Slack is connected from Starch's integration catalog; the agent queries it live to post the morning digest and read incoming rep requests. Task Manager tracks the open 'pull me a list' items and pending RevOps work items in one place.

Prompts to copy

Every weekday at 8:30am, pull my completed tasks from yesterday, check HubSpot for any deal stages I updated or contacts I modified, scan my Gmail for threads I responded to, and post a standup summary to our #revops Slack channel in this format: Yesterday / Today / Blockers. Tag my teammate so they see it.

When a rep sends me a 'can you pull me a list of...' request in Gmail or Slack, create a Task Manager item with P2 priority, due today, and include the original request text so I don't lose it in the thread.

At 5pm every Friday, compile the week's standup summaries from Slack, list any tasks that are still open from Monday through Thursday, and send me a digest email with a one-paragraph summary of what RevOps shipped this week.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your deals, contacts, and activity log on a schedule so the standup automation knows what you touched in the CRM without you typing it manually.

2 Connect Gmail — Starch connects directly to Gmail so the agent can scan which threads you responded to, which 'can you pull' requests came in, and which rep emails are still unanswered.

3 Connect Slack from Starch's integration catalog — the agent queries it live to post the morning standup digest and to watch the #revops channel for incoming ad-hoc requests.

4 Open Task Manager and set up your RevOps backlog — create a standing 'ad-hoc rep requests' project so every 'can you pull me a list of...' DM becomes a tracked task with a due date, not a Slack message you'll forget.

5 Build the daily standup automation: tell Starch 'Every weekday at 8:30am, pull what I did in HubSpot and Gmail yesterday, format it as Yesterday / Today / Blockers, and post it to #revops on Slack.' Starch builds the scheduled automation from that description.

6 Build the rep-request capture rule: tell Starch 'When a Gmail message from a sales rep contains the phrase "can you pull" or "can you send me a list", create a P2 task in Task Manager with the email subject and sender.' This stops requests from dying in your inbox.

7 Review the first morning digest the next business day — check that HubSpot activity and Gmail threads are pulling correctly; adjust the format prompt if the CRO wants a different structure.

8 Have your teammate connect their own HubSpot login and Gmail so the standup covers both RevOps members, not just one — the automation can post two formatted blocks in the same Slack message.

9 Set up the Friday wrap-up automation: 'At 5pm every Friday, summarize this week's standup posts from #revops and email me a digest with open tasks still outstanding.' This becomes your weekly RevOps record without any manual writeup.

10 Pin the Starch-generated standup format in #revops so reps know when to expect it and where to reply — the standup thread becomes the single place to drop blockers instead of hunting you down in DMs.

11 Once the standup log is a few weeks old, ask Starch to build a dashboard: 'Show me all blockers flagged in our standup posts over the last 30 days, grouped by category — CRM issue, data request, quota model, other.' Now you have evidence for where RevOps time actually goes.

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 Close Week — March 28, 2026

Sample numbers from a real run

HubSpot deal stage updates pulled automatically	14
Gmail rep requests captured as tasks	6
Minutes spent writing standup manually	0
Open blockers surfaced in Friday digest	3

It's March 28 — the last week of Q1 and the CRO is asking for a forecast update every six hours. Your standup automation fired at 8:30am and posted to #revops: Yesterday you updated 14 deal stages in HubSpot during the cleanup blitz, responded to 6 Gmail threads from AEs asking for commission-eligible pipeline lists, and flagged a blocker — the Salesforce-to-HubSpot field mapping for 'Expected Close Date' is still broken from the territory change two weeks ago. Today you're rebuilding the attribution model for the LinkedIn Ads spend. Blocker: need the CRO to confirm whether SDR-sourced deals count toward quota. All six of those 'can you pull me a list' emails from reps got auto-created as P2 tasks in Task Manager before you even opened your laptop. By Friday, the weekly digest compiled all five days of standup posts and surfaced the three recurring blockers — the field mapping issue, a missing Apollo sequence tag, and a rep who kept asking for the same Salesforce report — as a list you could take into the Monday planning call. No meeting needed. No status update typed from memory. The CRO had a timestamped log of what RevOps shipped in close week.

Measurement

How you'll know it's working

Standup completion rate — how many business days in the week did both RevOps members post an update vs. letting it slip

Ad-hoc rep request backlog — number of open 'can you pull me a list' tasks in Task Manager at any point in the week

Blocker resolution time — average days between a blocker flagged in standup and marked resolved in Task Manager

RevOps coverage ratio — percentage of sales reps who got at least one data request fulfilled per week, tracked from Task Manager completions

CRM hygiene actions logged — number of HubSpot deal or contact updates attributed to RevOps per week, surfaced automatically in the standup

Comparison

What this replaces

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

Geekbot or Standuply on Slack

Those tools send the standup prompt and collect free-text replies, but they don't know what you actually did in HubSpot or Gmail — every answer is still written from memory, which means busy close weeks are the weeks the standup gets skipped.

Manual Slack posts + Notion log

Writing the post and pasting it into Notion works until Q1 close week, when neither of you has five minutes to type a status — and the Notion log is always two weeks behind anyway.

Loom async video standup

Loom is better than nothing for human context, but there's no structured data extraction — blockers live inside a video file nobody will search, and rep requests still land in your inbox untracked.

Linear or Asana for RevOps task tracking

Either tool handles task structure well, but they don't connect to HubSpot or Gmail, so the standup still requires you to manually summarize what the CRM actually shows — you're paying for another SaaS seat to solve half the problem.

On Starch RECOMMENDED

One platform — task manager, email agent, project management 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

Can Starch actually read what I did in HubSpot yesterday, or does the standup just post whatever I type?

Starch syncs your HubSpot data on a schedule — contacts, deals, owners, and activity. The standup automation queries that synced data to see which deal stages you updated, which contacts you modified, and when. You don't type yesterday's activity; Starch pulls it. The accuracy depends on what's logged in HubSpot — if you worked in a spreadsheet and never updated the CRM, that activity won't show up.

We use Salesforce, not HubSpot. Does this still work?

Yes. Connect Salesforce from Starch's integration catalog; the agent queries it live when the standup automation runs. The connection behavior is slightly different from HubSpot — Salesforce is queried live rather than synced on a schedule — but the standup automation can still pull your recent deal activity and surface it in the daily post.

Can it post to a specific Slack channel and tag my teammate?

Yes. When you describe the automation, tell Starch which channel and whose handle — 'post to #revops and tag @[name].' Slack is connected from Starch's integration catalog and the agent queries it live at the scheduled time to post the digest.

What if one of us has a blocker that needs a real conversation — will the async standup actually surface it fast enough?

The standup posts at 8:30am and tags your teammate. If the blocker is urgent, nothing stops you from jumping on a call — async standup is a floor, not a ceiling. The value is that the blocker is written down and searchable, so when the CRO asks two weeks later why a deal sat stuck, you have a log.

Is Starch SOC 2 certified? We handle commission and quota data.

Not yet — Starch is not SOC 2 Type II certified today. If your security review requires SOC 2 before connecting HubSpot or Gmail, that's a real constraint worth knowing upfront. It's on the roadmap.

Can I search old standup posts to see what RevOps was doing in a specific week?

If you route the standups through Slack, Slack's own search covers it. You can also ask Starch to build a simple dashboard that pulls standup content from the Slack channel history — 'show me all blockers mentioned in #revops posts from the last 60 days' — and the agent queries it live from the integration catalog.