Internal Comms & Meetings

How to run an async standup as Solo Media and Creator Founders

Internal Comms & MeetingsFor Solo Media and Creator Founders3 apps11 steps~22 min to set up

You're a one-person media business. There's no Monday standup because there's no team — it's just you, a content calendar in Notion, a Stripe dashboard you check when anxiety spikes, and a Gmail inbox where sponsor follow-ups go to die. 'Staying on top of things' means remembering what you shipped last week, what's due tomorrow, and whether that sponsor paid their second installment — all while also recording, editing, and writing. You lose 30-45 minutes every Monday morning just reconstructing where things stand across YouTube Studio, Beehiiv, and your sponsorship tracker before you can do any actual work.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Solo Media and Creator Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A weekly async standup that automatically surfaces what shipped, what's overdue, and what's due next — pulled from your actual tools, not from memory

A task and project view that captures follow-ups from your standup in one click, so nothing lives only in your head after Monday morning

A Slack or email digest you can read in 3 minutes and act on immediately, replacing the 45-minute 'reconstruct my life' session at the start of every week

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

Task Manager and Project Management are the core surfaces for tracking content tasks and sponsor deliverables. Starch connects directly to Gmail (scheduled sync) so sponsor emails and unanswered pitches surface automatically in your standup. Slack is connected from Starch's integration catalog — the agent queries it live to post your Monday digest. Notion can be connected from Starch's integration catalog if you want your editorial calendar pulled in. Starch automates any web-based tool (like YouTube Studio or Beehiiv) through your browser — no API needed — to pull published and scheduled content into your weekly summary.

Prompts to copy

Every Monday at 8am, pull my overdue tasks and anything due this week from Task Manager, summarize what I shipped last week based on tasks I marked complete, and send me a standup digest to Slack

After I read my standup digest, create follow-up tasks for anything I flag as needing action — assign priority P1 or P2 based on due date proximity and add them to my content production project

Triage my Gmail inbox and surface any sponsor emails, partnership pitches, or unanswered follow-ups that are more than 3 days old — include them in my Monday standup digest as a 'needs reply' section

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

Walkthrough

Step-by-step

1 Connect Gmail to Starch (scheduled sync) — Starch syncs your messages so sponsor threads, partnership pitches, and unanswered emails from the past week are available when your standup runs.

2 Connect Slack from Starch's integration catalog so the agent can post your Monday standup digest to a private channel or DM — you'll read it like a message, not log into a dashboard.

3 Open Task Manager and load or import your current content and sponsor tasks — due dates, priorities (P1–P4), and completion status are the fuel for your standup summary.

4 Set up a Project Management board for your content production workflow (recording → editing → published, sponsor → invoiced → paid) so the standup can report project-level status, not just individual tasks.

5 Tell Starch: 'Every Monday at 8am, pull my overdue tasks and anything due this week, summarize completed tasks from the past 7 days, and send a standup digest to my Slack.' Starch schedules this automation.

6 Add a Gmail triage step to the same automation: 'Include any sponsor or partnership emails older than 3 days that I haven't replied to — list them in a needs-reply section at the bottom of the digest.'

7 Add browser automation for Beehiiv or YouTube Studio: 'Check what I published last week on Beehiiv and include the post title and open rate in the standup summary.' Starch automates this through your browser — no API needed.

8 Read the digest on Monday morning — it's 3 minutes, not 45. It tells you: what shipped, what's overdue, what's due this week, and which sponsor emails need a reply.

9 When you spot a follow-up in the digest, tell Starch: 'Create a P1 task to reply to the Notion partnership pitch by Wednesday and add it to my sponsor ops project.' The task is created, prioritized, and filed without touching a form.

10 At the end of each week, run a quick completion check: 'Show me tasks I completed this week vs. tasks I created — what's my completion rate?' This becomes your personal velocity metric.

11 Refine the standup prompt over time — add your Stripe data once Stripe is connected (scheduled sync) to include 'did any sponsor invoices go unpaid this week' in the digest, so your financial and content ops live in one Monday check-in.

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

Monday standup digest — week of March 9, 2026

Sample numbers from a real run

Tasks completed last week	6
Tasks overdue (not completed by deadline)	3
Tasks due this week	8
Sponsor emails older than 3 days, no reply	2
Beehiiv posts published last week	2
Open rate on Wednesday issue (#47)	41

It's Monday, 8:04am. You haven't opened a laptop yet. Your Slack shows one message — from Starch. Last week you completed 6 tasks: finished the episode edit for the Figma interview, sent the invoice to Athletic Greens for the March slot, wrote and scheduled issue #47, and three smaller tasks. Three things are overdue: you haven't replied to a potential sponsor pitch from Superhuman (4 days old), you missed sending the March media kit to one warm inbound lead, and the episode transcript for repurposing is still sitting in Descript. Eight tasks are due this week including the April editorial calendar, the Stripe payout reconciliation, and recording the next episode intro. The digest also tells you issue #47 hit a 41% open rate — up from 37% the week before — pulled from Beehiiv via browser automation. You spend 4 minutes reading it, type 'create a P1 task to reply to the Superhuman pitch today and a P2 task to finish the transcript by Thursday,' and your week is structured before you've had coffee.

Measurement

How you'll know it's working

Weekly task completion rate (tasks completed / tasks created, tracked in Task Manager)

Sponsor email response time — days between inbound pitch and first reply (surfaced in standup digest from Gmail sync)

Newsletter open rate week-over-week (pulled from Beehiiv via browser automation)

Overdue task count at standup time — target is zero carry-over from prior week

Sponsor invoice status: invoices sent vs. paid this month (from Stripe scheduled sync once connected)

Comparison

What this replaces

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

Notion + manual weekly review

Notion holds your editorial calendar well but won't pull in Gmail threads, task status, and published content automatically — the Monday reconstruction is still manual, still 45 minutes.

Linear or Asana standup bots

Good at surfacing task status from within their own system, but they don't touch your inbox, your Beehiiv stats, or your sponsor tracker — you still need to check four tabs to get the full picture.

A weekly template in Google Docs you fill out yourself

Zero cost, full control, and you'll stop filling it out by week three because it requires you to do the work the standup is supposed to replace.

Slack standup bots (Geekbot, etc.)

Great for teams — asks each person what they did and what's blocked — but when you're solo there's nobody to ask, and the bot doesn't know what's actually overdue in your task list or what emails you've been ignoring.

On Starch RECOMMENDED

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

I don't have a team. Why do I need a standup?

You don't need a standup in the team-meeting sense. What you need is a weekly forcing function that reconstructs where your business actually stands — tasks, inbox, content, sponsors — without you spending 45 minutes doing it manually. The async standup is really a Monday morning briefing for an audience of one.

Can Starch pull my Beehiiv or Substack stats automatically?

Yes, via browser automation — Starch automates Beehiiv or Substack through your browser, no API needed, and can pull published post titles and open rates into your standup digest. It's not a native sync, so it's not stored historically in Starch, but it shows up in your Monday digest accurately.

What if my sponsor tracker is a Google Sheet?

Connect Google Sheets from Starch's integration catalog and the agent queries it live when your standup runs. You can tell Starch to surface rows where payment status is 'unpaid' or where the follow-up date has passed — so your Monday digest includes a sponsor ops section alongside your task summary.

Is my Gmail data stored in Starch?

Starch syncs Gmail on a schedule — messages sync in pages of 30 to avoid errors on long HTML threads, and labels sync too. One honest heads-up: the Gmail OAuth consent screen currently shows the underlying connector's name rather than Starch's — that's on the roadmap to fix, and it doesn't affect how the sync works.

Can I use this if my editorial calendar is in Notion?

Yes — connect Notion from Starch's integration catalog and the agent queries your pages and databases live. You can include a 'what's scheduled this week' section in your standup digest pulled directly from your Notion editorial calendar.

What if I want to change what's in the standup over time?

Just tell Starch. The automation is defined by a natural-language prompt, not a rigid config. 'Add a section that shows my YouTube video published last week and its first 48-hour view count' is a prompt edit, not a workflow rebuild. You're not locked into any fixed format.