Internal Comms & Meetings

How to run an async standup as Professional Services Founders

Internal Comms & MeetingsFor Professional Services Founders2 apps11 steps~22 min to set up

Your 12-person consultancy runs on Slack and good intentions. Every Monday someone forgets to post their standup, three people post at different times, and by 11am you're still DMing Jordan to find out if the Meridian deliverable is on track. You've tried Geekbot, you've tried a Slack reminder, you've tried a Google Form. What you actually need is a system that collects updates, surfaces blockers, and ties back to what's in your project tracker — without you chasing anyone down. Client work doesn't pause for your internal ops.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Professional Services Founders2 apps11 steps~22 min to set up

Outcome

What you'll set up

An automated async standup that collects updates from every team member each morning, surfaces blockers without a meeting, and posts a rolled-up digest to Slack so you see the whole picture in 60 seconds

A task and project view that links each standup response back to live work items — so 'blocked on client approval' actually references the task, not just a Slack message that disappears

A personal task layer for yourself so your own commitments (proposal due, invoice to chase, renewal call to prep) don't get buried under client work

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

Data sources & config

Connect Slack from Starch's integration catalog — the agent queries it live to send prompts and post digests. Wire Project Management and Task Manager as internal surfaces. Starch syncs your Google Calendar data on a schedule so the automation knows to skip standup on days with no working events (holidays, all-hands).

Prompts to copy

Every weekday at 9am, message each team member in Slack and ask: what did you finish yesterday, what are you working on today, and is anything blocked? Collect their replies and post a summary digest to #standup by 9:30am. Flag any blockers in bold.

When a team member says they're blocked, create a task in the Project Management board under the relevant project, assign it to me, mark it P1, and set the due date to today.

Every Friday at 4pm, post a weekly wrap to #standup: how many tasks were completed this week, which projects had blockers, and which items are still open heading into Monday.

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

Walkthrough

Step-by-step

1 Connect Slack from Starch's integration catalog. This is where your team already lives — Starch sends the standup prompts and posts the digest without anyone changing their habits.

2 Connect Google Calendar as a scheduled-sync provider. Starch reads your team calendar to skip standup prompts on holidays, internal offsites, or days when the whole team is on a client site.

3 Install the Project Management app from the Starch App Store. Set up one project per active client engagement (Meridian rebrand, Kellner ops audit, etc.) with tasks already in flight.

4 Set up your personal Task Manager for your own to-dos: proposals to send, invoices to follow up on, retainer renewals to prep. These don't belong in the client project boards but they can't live in your head.

5 Describe the standup automation in natural language: 'Every weekday at 9am, DM each team member in Slack with three questions: done yesterday, doing today, any blockers. Collect replies and post a digest to #standup by 9:30am.'

6 Add a blocker-escalation rule: 'If anyone reports a blocker, automatically create a P1 task in the relevant project board, assign it to me, and include the original message text as the task description.'

7 Test with yourself first — run the prompt, reply with a fake standup, and confirm the digest looks right and the blocker-to-task path works before rolling it out to the team.

8 Roll out to the team. Because it runs through Slack (a tool they already use), adoption friction is close to zero — no new login, no new app to check.

9 Add a Friday wrap automation: 'Every Friday at 4pm, post a weekly summary to #standup showing tasks completed, blockers that came up, and items still open. Pull from this week's standup data.'

10 Each Monday morning, review the digest in Slack and the open blockers in your Project Management board. Your 30-minute weekly team call, if you still want one, becomes a decision meeting instead of a status meeting.

11 At month-end, use the standup history and task completion data to cross-reference utilization — who was carrying blockers on which engagements, and whether that shows up in the Harvest data you're already pulling separately.

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 17, 2026 — Meridian rebrand crunch week

Sample numbers from a real run

Team members who posted standup by 9:30am	9
Team members who needed a Slack nudge	3
Blockers surfaced automatically	4
P1 tasks auto-created from blockers	4
Minutes spent by you chasing updates	0

Monday morning, Starch DMed all 12 team members at 9am with the three standup questions. By 9:25am, nine had replied. At 9:30am Starch posted the digest to #standup — you read it in 90 seconds over coffee. Two replies mentioned the same blocker: the Meridian brand guidelines PDF hadn't been shared by the client, so two designers were sitting idle. Starch auto-created two P1 tasks in the Meridian project board, assigned both to you, and flagged them in bold in the digest. You sent a client email by 9:45am. The three non-responders got a second Slack nudge at 10am and all replied by 10:15. By comparison, the previous week — before the automation — you'd spent 40 minutes on Monday DMing people individually to piece together the picture, and the Meridian blocker didn't surface until Tuesday afternoon when a designer mentioned it in passing.

Measurement

How you'll know it's working

Standup participation rate (target: 100% of team posted or replied by 10am without a manual chase)

Blocker-to-escalation time (how quickly a reported blocker becomes an assigned task and gets acted on)

Average number of active blockers per client engagement per week

Percentage of weekly team calls that turn into decision meetings vs. status updates

Friday-to-Monday open task carryover rate (how many unresolved items roll into the next week)

Comparison

What this replaces

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

Geekbot

Geekbot runs solid async standups inside Slack, but it's a standalone tool with no connection to your project board — blockers stay in Slack and don't automatically become tasks or escalations.

Slack reminders + Google Form

Free and zero setup, but collecting responses requires you to read a form, the digest is manual, and nothing ties back to your project work — you're still the router.

Linear or Asana built-in check-ins

Requires the whole team to work inside Linear or Asana, which means a migration and training overhead that a 12-person consultancy billing by the hour can't afford right now.

Kantata / Projector / Deltek

Enterprise PSA tools have standup and status modules, but they're priced and scoped for 200-person firms — implementation alone takes a quarter, and you don't need 80% of what they offer.

On Starch RECOMMENDED

One platform — project management, task manager 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 the whole team need to sign up for Starch?

No. The standup automation sends prompts through Slack — your team replies in Slack the way they always do. Starch reads those replies and builds the digest. Only you, as the operator, need a Starch account.

What if someone replies late or misses the standup window entirely?

You can set a second nudge — 'If someone hasn't replied by 10am, send them a follow-up Slack DM.' You can also configure the digest to post at 9:30am with whoever's responded, and update it if late replies come in. The specifics are whatever you tell Starch to build.

Can Starch connect to Harvest or Float for utilization data alongside the standups?

Harvest and Float are web-based tools, so Starch can automate them through your browser — no API needed. That said, for a true utilization view pulling standup data, project tasks, and Harvest hours together, you'd describe a custom dashboard and Starch builds it. If you use Slack, Google Calendar, or HubSpot as part of the standup flow, those connect directly from Starch's integration catalog.

Is Starch SOC 2 certified? Our clients ask about data security.

Not yet — Starch is not currently SOC 2 Type II certified. If a client engagement requires SOC 2 for any vendor touching project data, that's worth knowing upfront. It's on the roadmap.

We use Notion for project documentation. Can the standup data go there?

Yes. Starch syncs your Notion data on a schedule and can write standup summaries or blockers to a Notion database. Tell Starch: 'After each standup digest, log this week's blockers to the Blockers table in Notion.' It handles the rest.

What's the difference between the Project Management app and the Task Manager here?

Project Management is for client work — one board per engagement, shared with whoever is staffed on it, with kanban and workload views. Task Manager is for your personal to-do list as a founder: the proposal you owe a prospect, the invoice you need to chase, the retainer renewal you can't miss. They're separate surfaces because your personal commitments and client deliverables shouldn't compete for space on the same board.