The Standup Client Workspace Setup (Onboarding)

The Standup Client Workspace Setup (Onboarding)

1. 01

   Create the agency's own Standup account on the Free tier ($0, monthly) using the agency's shared inbox rather than an individual address.

   The Free plan already includes the daily digest at 07:40, the full searchable archive, and every release, advisory and outage, so no paid seat is needed to run the first client workspace. Membership at $5 monthly only pays for the polling, storage and sending, and removes ads.

2. 02

   Build a tracking list named for the client, then add only the vendors and repositories that client's stack actually runs.

   The Standup monitors GitHub, npm, Supabase, Netlify, Datadog, Elastic Cloud, Ubuntu Security, Cloudflare, Vercel and Microsoft. A WordPress, Stripe and Mailchimp client will not generate useful alerts from Datadog or Elastic Cloud, so leave those sources off the list.

3. 03

   Confirm the first digest lands at 07:40 and read the category tags before forwarding anything.

   Items arrive tagged patch-or-pin, open at your vendors, shipped, or worth knowing. The patch-or-pin items are the ones that justify a retainer line; the rest are context.

4. 04

   Test the searchable archive against one known past incident in the client's stack.

   Search the vendor name and the month of the outage. If the archive returns nothing, the source was never added to the tracking list and the client has a blind spot you are about to bill for.

5. 05

   Write the client-facing digest rule: which tags get forwarded same day, which wait for the weekly note.

   A workable default is patch-or-pin and open at your vendors go out the same morning; shipped and worth knowing roll into a Friday summary. This is the difference between managed oversight and a forwarded email.

6. 06

   Hand the tracking list to the delivery lead and record the handoff in the client file.

   The Standup aggregates alerts but does not automate remediation, so the named owner on the agency side is the only thing standing between an advisory and an unpatched client dependency.