Internal Comms & Meetings

How to run an async standup as Small Marketing Teams

Internal Comms & MeetingsFor Small Marketing Teams4 apps12 steps~24 min to set up

Your three-person team runs standups over Slack threads that die by noon. Someone posts a blockers update at 9am, the lifecycle manager replies at 2pm, and by Thursday nobody remembers what was agreed on Monday. You're chasing the contractor for a blog post update, the paid lead doesn't know the content calendar shifted, and you're manually compiling a 'what did we ship this week' summary for the CEO by copy-pasting from Notion, HubSpot activity logs, and your own memory. You have no EA, no ops manager, and your PM tool — if you use one — isn't connected to any of the places work actually lives.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Marketing Teams4 apps12 steps~24 min to set up

Outcome

What you'll set up

A recurring async standup that pulls each teammate's updates from Slack, Notion, and Gmail into one structured summary — no meeting required

An action-item tracker that captures commitments from standup threads and flags anything that's overdue before your next sync

A weekly digest you can forward directly to your CEO showing what shipped, what's blocked, and what's at risk across demand gen, content, and lifecycle

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

Project Management Task Manager Meeting Notes Email Agent

Data sources & config

Starch connects directly to Slack from its integration catalog, querying it live when the standup automation runs. Starch also connects directly to Notion from its integration catalog for the content calendar and campaign brief data. Starch syncs your HubSpot data on a schedule (contacts, deals, owners) to power the weekly MQL summary. Gmail is connected as a scheduled-sync provider so the Email Agent can draft and send the CEO digest. The Notion content calendar and Slack channel are both queried live each time an automation fires.

Prompts to copy

Every Monday at 9am, message each person on my marketing team in Slack asking: what did you finish last week, what are you working on this week, and what's blocked? Collect their replies and post a formatted summary to the #marketing-standup channel by noon.

After each standup summary is posted, extract every action item mentioned, create a task in Task Manager for the right person with a due date, and send me an overdue report every Friday at 4pm for anything that wasn't completed.

Every Friday at 3pm, generate a one-page summary of the week's marketing activity — campaigns launched, MQL volume from HubSpot, top content pieces, and open blockers — and draft an email to the CEO I can review and send with one click.

Build me a project board with columns for Briefing, In Progress, In Review, and Published — pre-loaded with our Q2 content calendar from Notion — so I can see every blog post, email, and ad creative in one place.

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

Walkthrough

Step-by-step

1 Connect Slack from Starch's integration catalog and tell Starch which channel your team uses for standup updates and who the three team members are.

2 Connect Notion from Starch's integration catalog so Starch can read your campaign briefs, content calendar, and project databases — query it live each time an automation runs.

3 Tell Starch: 'Every Monday at 9am, DM each team member in Slack with our three standup questions and collect replies through noon.' Starch builds the scheduled automation and handles the Slack messages automatically.

4 Tell Starch: 'After replies are collected, format them into a structured summary with three sections — Done, Doing, Blocked — and post it to #marketing-standup.' Starch generates and posts the digest without any manual formatting.

5 Start the Project Management app and load your Q2 content calendar from Notion into a Kanban board with columns matching your actual workflow: Briefing, Draft, In Review, Published.

6 Tell Starch: 'After each standup summary posts, extract every action item and create a task in Task Manager assigned to the right person with a due date parsed from the message.' Starch reads the summary and builds the tasks.

7 Set up a Friday 4pm overdue report: 'Every Friday, show me every task from the marketing standup board that was due this week and isn't marked complete, and message me the list in Slack.'

8 Connect Gmail as a scheduled-sync provider and tell the Email Agent: 'Every Friday at 3pm, draft a weekly marketing summary email to the CEO — include MQL volume from HubSpot, campaigns we launched, content we published, and anything still blocked — and put it in my drafts for review.'

9 Sync your HubSpot data on a schedule so the Friday CEO digest can pull live deal and MQL counts without manual exports.

10 Add the contractor to a limited Slack channel Starch monitors, and set up a prompt: 'If the contractor hasn't posted a status update on their current deliverable by Wednesday noon, DM me a reminder so I can follow up.'

11 After two weeks, tell Starch: 'Show me a report of which standup blockers took more than three days to resolve and who owns the most recurring blockers.' Use this to run a short retro with the team.

12 Publish your standup automation to your team's Starch workspace so the lifecycle and paid leads can fork it for their own sub-team rhythms without starting from scratch.

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 push standup cycle

Sample numbers from a real run

Content (blog + email)	3
Paid (Meta + Google)	2
Lifecycle (Customer.io flows)	1
Open blockers captured	4
Tasks auto-created in Task Manager	6
Minutes spent on standup coordination	0

It's the week before Q1 close. The content lead is finishing the March nurture email, the paid lead is watching CPL creep up on Meta, and the lifecycle lead just discovered a broken trigger in a Customer.io flow. On Monday at 9am, Starch DMs all three in Slack with the three standup questions. By 11:45am, all three have replied. Starch formats the replies into a structured #marketing-standup post: Done (March newsletter drafted, Google campaign paused for creative refresh), Doing (finishing the webinar follow-up sequence, rebuilding the Meta audience), Blocked (Customer.io flow broken — needs eng ticket, blog contractor hasn't delivered the SEO draft due Friday). Starch extracts four blockers and creates six tasks in Task Manager — two for the lifecycle lead, two for the content lead, one flagged for engineering, one for the contractor follow-up — all with due dates parsed from the standup messages. By Friday at 3pm, the Email Agent drafts the CEO summary: MQL volume down 12% week-over-week per HubSpot, two campaigns launched, one blog post published, two open blockers still unresolved. The content lead reviews the draft, adjusts one number, and sends it in one click. Total time spent on standup coordination for the week: zero scheduled meetings.

Measurement

How you'll know it's working

Standup participation rate — percentage of team members who respond before the noon cutoff each week

Blocker resolution time — average days between a blocker being flagged in standup and the task being marked complete

Task completion rate — percentage of action items created from standups that are resolved before the next standup

CEO digest send rate — whether the Friday summary actually goes out every week or gets skipped when things get busy

Contractor delivery adherence — percentage of external deliverables flagged in standup that arrive on time

Comparison

What this replaces

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

Geekbot (Slack standup bot)

Geekbot collects standup replies in Slack but doesn't create tasks, connect to HubSpot for context, draft your CEO email, or let you build a custom project board on top of the data — you still assemble the summary manually.

Notion + manual Slack updates

Your team already has Notion, but someone has to remember to post, read every update, copy action items into a tracker, and compile the CEO summary — it's the coordination overhead Starch eliminates.

Asana or Linear

Full-featured PM tools with async check-in features, but they require manual setup, don't generate CEO digests from your HubSpot data, and add another monthly SaaS line to justify to finance.

Loom async video standups

Good for nuanced updates that need tone, but the summaries aren't searchable or extractable into tasks, and you still need someone to watch every video and pull the action items out.

On Starch RECOMMENDED

One platform — project management, task manager, meeting notes 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 send Slack messages, or does it just read them?

Both. Starch connects to Slack from its integration catalog and can read channel messages and post to channels. Your standup automation sends the DMs to teammates, collects their replies, and posts the formatted summary — all without you touching Slack manually.

What if one teammate doesn't reply before the noon cutoff?

Tell Starch what to do: 'If someone hasn't replied by 11:45am, send them a Slack reminder.' You can also instruct Starch to post the summary anyway and mark that person's section as 'no update received' so the rest of the team isn't blocked.

Can Starch pull MQL numbers from HubSpot automatically for the CEO digest?

Yes. Starch syncs your HubSpot data — contacts, deals, owners — on a schedule, so when the Friday digest automation runs, it can pull current MQL counts and deal-stage movement without you exporting anything from HubSpot.

We use Customer.io, not a tool Starch has a deep integration with. Can it still include lifecycle campaign data?

Starch connects to Customer.io from its integration catalog and queries it live when your automation runs. You can include campaign send counts, open rates, or active segment sizes in your weekly summary — describe what you want and Starch pulls it.

Is our standup data stored somewhere I can search later?

Yes — Starch archives the standup summaries and extracted tasks in your workspace. If you need to find out when a specific blocker was flagged or what was agreed three weeks ago, you can search for it. Worth noting: Starch is designed for live operational data surfaces, not long-horizon data warehousing, so this is team memory for the past several months, not a multi-year archive.

Will this replace our PM tool entirely?

For a three-person team, Starch's Project Management app handles what most small marketing teams actually need: Kanban board, list view, task assignment, due dates, and priority levels. If you're already paying for Linear or Asana and getting value, you don't have to abandon it — Starch can pull from those tools via its integration catalog. But if you're paying for a PM tool mostly out of habit, this is a real alternative.

What if our contractor or agency isn't on Slack?

Starch can send Gmail follow-ups through the Email Agent instead. Tell Starch: 'If the contractor hasn't confirmed delivery by Wednesday, draft a follow-up email from my Gmail account and put it in drafts for me to review.' Same logic, different channel.