How it Works - Sauna Labs

01

We watch how your team actually works

Sauna Labs connects to the tools your team already uses and listens. When a recurring workflow runs, the system records which actions happen in which order and across which tools.

No configuration, no tagging, no mapping sessions. The observation layer stays in the background and captures real sequences from real work.

After a few repetitions of the same workflow, you have a data set that reflects how your team actually operates, not how a consultant documented it six months ago.

02

Patterns emerge from repetition

After seeing the same workflow run three or more times, Sauna Labs identifies the canonical sequence: the steps that always happen, the tools they span, the order that holds across different people.

Variations get weighed against the core pattern. The system distinguishes between steps that are always part of the workflow and steps that depend on context, and it notes both.

The output is a playbook draft, ready for you to review. What it includes and what it marks for human judgment is based on observed behavior, not templates.

03

Your playbook, ready to run

The playbook is a structured list of the steps Sauna Labs will handle automatically, plus the steps it hands back to you for approval or input before proceeding.

You review it once, adjust anything that looks off, and activate it. From that point, each time the workflow trigger fires, Sauna Labs runs the assembly steps and pauses at the judgment steps for your sign-off.

Every playbook is visible and editable. You can see exactly what it will do, change any step, and turn it off at any time.

Playbook: Deal Handoff

AUTO Create handoff record in Notion

AUTO Pull context from Salesforce deal

YOU Review and send welcome email

AUTO Assign onboarding tasks in Linear

AUTO Notify CS lead in Slack

04

You keep the send button

Every judgment step in a playbook pauses for your approval. Sauna Labs queues the output, surfaces it to the right person with context, and waits. Nothing goes out until you decide it should.

This is not a safety net added after the fact. Human approval is built into the playbook structure from the start. You define which steps require your sign-off and which ones Sauna Labs can handle end-to-end.

The result is automation that you can trust with the work that matters, without handing over the decisions that define it.

Awaiting your review

Welcome email - Acme Corp

Hi Sarah, welcome to the platform. Your onboarding session is scheduled for Thursday 2pm...

CS assignment - Bright Corp

Waiting on previous step...

Common questions

Common questions about how Sauna Labs works

What tools does Sauna Labs connect to?

Sauna Labs connects to the tools that ops and revenue teams use most: Salesforce, HubSpot, Pipedrive, Linear, Notion, Asana, Slack, Gmail, and Intercom. The connection is read and write - it observes actions in those tools and can take actions in them on your behalf once a playbook is active. New integrations are added on a rolling basis.

How does it handle sensitive data?

Sauna Labs processes workflow metadata and action sequences, not the underlying content of your records. When a playbook step requires reading content (to draft a handoff email, for example), that content is processed in-transit and not stored beyond the task completion. Data handling details are in the privacy policy and available on request.

Can I customize which steps it automates?

Yes. After a playbook is generated from observation, you review each step and choose whether it should run automatically or pause for your approval. You can edit the step description, change its type, remove it entirely, or add a step that was not observed. The playbook is yours to shape.

What if my workflow changes over time?

Sauna Labs continues observing even after a playbook is active. If it detects a drift between the playbook steps and how the workflow is actually being run, it surfaces a suggested update. You decide whether to adopt the change. The system does not auto-update a live playbook without your review.

How long until a playbook is ready?

It depends on how often the workflow runs. Sauna Labs needs to see a workflow complete three or more times before it generates a playbook draft. For workflows that happen weekly, you might have a draft within a month. For workflows that happen daily, it could be within a week. You can also manually mark a workflow for observation to prioritize it.

Get started

Ready to see it work for your team?

Connect your tools and let Sauna Labs start observing. The first playbook draft usually appears within a few weeks of normal use.