
Sauna reads the onboarding plan in your project board and the customer's intake form, drafts the configuration checklist, writes the status updates, and chases the inputs you're waiting on.
What it does
Sauna turns the project scope into a configuration checklist in ClickUp, one task per setup step with the owner and dependency noted.
It reads the project board and drafts a weekly customer status email summarizing what's done, in progress, and blocked.
When a step waits on customer data, Sauna drafts a friendly email naming exactly what's needed and why it's blocking go-live.
It assembles a go-live runbook in Google Docs from the project steps so the cutover has a checked sequence.
Put Sauna to work on this.
Get started for freeIn context
Sauna shows up where you already work — the web app, Slack, email, iMessage, and Superhuman. It reads what it needs, does the task, and comes back with the draft for your approval.
Try it
The literal prompt for this job. Open it in Sauna and it picks up from there.
“Read the onboarding plan in ClickUp and the customer intake form, build a configuration checklist, and draft a status email noting what's blocked on their side.”
Plugs into the tools you already run — and thousands more, or any MCP server.
Good to know
No. Status updates and input requests are drafted and held; you approve before any message goes out.
It builds and tracks the checklist and runbook; the actual configuration stays in your hands.
Sauna reads only what you connect, and acts only after you approve. Your workspace and its memory are yours, not training data.
Keep exploring