Internal Comms & Meetings

How to run an async standup as Small Customer Success Teams

Internal Comms & MeetingsFor Small Customer Success Teams3 apps12 steps~24 min to set up

Your three-person team covers 250 B2B accounts. Every morning someone asks 'what's everyone working on today?' and the answer comes back three hours later over Slack — or not at all. You're running on a mix of weekly syncs that run long, Slack threads nobody reads back, and a mental model of who owns which renewal that lives in one person's head. When a CSM goes on PTO, nothing is written down. Gainsight and ChurnZero would give you structured standups, but they cost six figures and require a CS-ops hire to configure. You need something that collects where everyone is on their accounts each morning and surfaces blockers before they become churned customers.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Customer Success Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A daily async standup that automatically collects each CSM's account status, flags, and blockers — no calendar hold required

A searchable archive of every standup response linked to the accounts discussed, so when a CSM is out you can catch up in 90 seconds

An automated summary pushed to your team Slack channel each morning with open blockers highlighted, so nothing gets buried in a thread

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 Project Management

Data sources & config

Starch syncs your Slack data on a schedule (channels and users) and connects directly to Gmail for any CSMs who prefer email responses. HubSpot is connected through Starch's integration catalog so the agent can query account names and owner assignments live when building summaries. Task Manager is built into Starch — no external connection needed.

Prompts to copy

Every weekday at 8:30 AM, send each CSM a Slack message asking: which accounts did you touch yesterday, what's your focus today, and do you have any blockers? Collect their responses and post a formatted summary to #cs-standup by 9:15 AM.

After the daily summary posts, scan it for any account mentioned alongside words like 'risk', 'unresponsive', 'delayed', or 'churn' and create a task in Task Manager assigned to that CSM with priority P1, due today.

Each Friday at 4 PM, generate a weekly standup digest: how many accounts were touched this week, which blockers were opened vs resolved, and which CSM had the most at-risk mentions — pull from this week's standup summaries.

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

Walkthrough

Step-by-step

1 Connect Slack in Starch — Starch syncs your Slack channels and user list on a schedule so it knows which channel to post to and which CSMs to ping each morning.

2 Connect HubSpot from Starch's integration catalog so the standup agent can look up account ownership live and validate that account names CSMs mention actually exist in your pipeline.

3 Tell Starch: 'Every weekday at 8:30 AM, send each person in the cs-team Slack user group a DM asking three questions: what accounts did you touch yesterday, what's your focus today, any blockers?' — this becomes your automated standup prompt.

4 Tell Starch: 'Collect responses until 9:10 AM. If someone hasn't responded by 9:05 AM, send them a one-line reminder DM.' — this replaces the manual 'hey did you fill in the standup' chase.

5 Tell Starch: 'At 9:15 AM, compile all responses into a formatted summary grouped by CSM. For each CSM, list their accounts, today's focus, and any blockers. Post to #cs-standup.' — this is the summary your whole team reads instead of three separate Slack messages.

6 Tell Starch: 'After each summary posts, scan for accounts mentioned alongside risk language — unresponsive, at risk, delayed, no response, churn — and for each one, create a P1 task in Task Manager assigned to the CSM who mentioned it, due today.' — blockers now become trackable work items automatically.

7 Open Task Manager in Starch and confirm the auto-created P1 tasks are showing up correctly. Adjust the risk-language trigger list with: 'Also flag any account mentioned with the word escalation or legal.'

8 Tell Starch: 'Every Friday at 4 PM, pull this week's standup summaries and generate a digest: total accounts touched, blockers opened, blockers closed, and the three accounts that appeared most frequently across standups. Post to #cs-standup with the subject line Weekly CS Digest.'

9 After two weeks of standup data, ask Starch: 'Which accounts have been mentioned as a blocker more than twice this month without a resolution?' — this surfaces your stickiest problems before the QBR.

10 Tell Starch: 'When I type /catchup [CSM name] in Slack, pull their last five standup responses and summarize which accounts they've been focused on and any open blockers.' — this is how you get up to speed when someone goes on PTO.

11 Review the weekly digest on Friday and tell Starch to create a P2 task for any account that appeared in three or more blockers this week: 'Create a task titled Account Review: [account name] assigned to me, due next Monday.' — this feeds your weekly account review queue.

12 Once the pattern is stable, tell Starch: 'Add a field to the standup prompt asking each CSM to rate their top account's health 1–5. Track this score week over week and alert me if any account drops two points in a row.' — this is your lightweight churn-risk signal without buying Gainsight.

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

Week of March 10, 2026 — Q1 renewal crunch

Sample numbers from a real run

Meridian Logistics (renewing March 31, $48K ARR)	48,000
Fenwick Group (expansion conversation stalled)	31,000
Arcato Health (new customer, 60-day onboarding)	22,000

On Monday March 10, all three CSMs responded to the 8:30 AM standup by 9:05. Sarah mentioned Meridian Logistics was 'unresponsive to the renewal doc sent Friday' — Starch flagged the account automatically and created a P1 task assigned to Sarah, due that day. Marcus mentioned Fenwick Group's expansion call had been rescheduled twice. Starch created a P2 task and included Fenwick in the weekly digest's 'appeared most frequently' list. By Friday, the weekly digest showed 14 accounts touched, 4 blockers opened, 2 resolved, and Meridian and Fenwick both flagged as appearing in 3+ standup responses. At the Friday team check-in, instead of spending 20 minutes reconstructing the week, the team read the digest in 3 minutes and spent the remaining time deciding whether to loop in the AE on Fenwick. Meridian's renewal closed March 28 — Sarah had the context she needed because the blocker was visible Monday, not discovered Friday.

Measurement

How you'll know it's working

Standup response rate — percentage of CSMs who respond before the 9:15 AM summary posts (target: 100% within 45 minutes)

Blocker-to-task conversion rate — percentage of flagged blockers that become tracked tasks with an owner and due date

At-risk accounts surfaced per week — how many accounts appeared in standup risk language before showing up in a churn conversation

PTO catch-up time — how long it takes a covering CSM to get up to speed on an absent colleague's accounts (target: under 5 minutes)

Renewal forecast accuracy — gap between what CSMs reported in standups and actual renewal outcomes at month end

Comparison

What this replaces

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

Geekbot (Slack standup bot)

Geekbot collects standup responses well but can't query HubSpot to validate account names, auto-create tasks from blocker language, or generate a searchable digest connected to your CS data — it's a form, not an agent.

Gainsight or ChurnZero

Purpose-built for CS health scoring and standup workflows, but both cost six figures, require a CS-ops person to configure, and assume a team larger than three — complete overkill for a 3-CSM, 250-account operation.

Slack + Google Docs (manual standup thread)

Free and familiar, but someone has to chase responses, write the summary, copy blockers into a task tracker, and remember to look at last week's doc before a renewal call — that person is probably you.

Notion standup template

Decent for async documentation but passive — it doesn't send reminders, doesn't flag risk language, doesn't push a summary to Slack, and doesn't connect to HubSpot to make account mentions actionable.

On Starch RECOMMENDED

One platform — task manager, founder inbox, 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

We use HubSpot as our CRM. Can Starch actually pull account data into the standup summaries, or is it just collecting freeform text from CSMs?

Both. Starch collects freeform standup responses from your CSMs via Slack, and separately queries HubSpot live from Starch's integration catalog when building summaries or validating account names. You can ask Starch to cross-reference a CSM's standup response against HubSpot deal stage — for example, 'if a CSM flags an account as a blocker and that account has a renewal date within 30 days in HubSpot, mark the task P1 instead of P2.'

What if a CSM forgets to respond? Does the whole summary break?

No. You tell Starch how to handle it — for example, 'if a CSM hasn't responded by 9:05 AM, send a reminder DM; if still no response by 9:10, post their section as No update submitted and continue.' The summary posts regardless. You can also tell Starch to tag you directly if the same person misses two standups in a row.

We also use Intercom for customer conversations. Can Starch factor in what's happening in support when flagging at-risk accounts?

Yes — connect Intercom from Starch's integration catalog and the agent queries it live. You could tell Starch: 'When an account is mentioned as a blocker in standup, check if that account has an open Intercom conversation older than 48 hours and include that in the task description.' That gives CSMs the full picture without switching tools.

Is this actually async, or does it require everyone to be online at the same time?

Fully async. The standup prompt goes out at 8:30 AM, the collection window closes at 9:10 AM, and the summary posts at 9:15 AM. CSMs respond whenever works for them in that window — from their phone, from Slack, from wherever. There's no meeting, no Zoom link, no waiting for someone to finish their thought.

We're not SOC 2 certified at Starch yet — is that a problem for us?

Starch is not SOC 2 Type II certified today — that's worth knowing if your company has strict vendor security requirements. If your CS team handles regulated customer data that requires SOC 2 compliance in every vendor, flag that with your security team before connecting HubSpot or Slack. For most small CS teams running internal standups, this isn't a blocker, but it's an honest limit you should evaluate for your situation.

What happens when a CSM goes on PTO? Can someone else quickly read their account history?

Yes — this is one of the most concrete things the standup archive solves. Tell Starch: 'When I type /catchup [name] in Slack, pull their last 10 standup responses and summarize which accounts they were focused on, any open blockers, and the last thing they said about each account.' A covering CSM can get the full picture in under five minutes without digging through Slack threads.