Latch®

© 2026 Latch — churn-save agents for every team.

How it works

Simple path from signup to a working agent.

Latch is multi-tenant: each team gets a workspace, creates agents, and runs save plays with clear proof — not a demo console.

1. Sign up

Create a workspace with email and password. No Google login. Verify your email later in Settings if you want.

2. Add agents

Each agent watches for churn signals you care about — cancel language, failed payments, quiet accounts.

3. Connect tools

Link Slack, Google (Sheet + Calendar + Gmail drafts), and Stripe to the workspace. Tool login is separate from your Latch login.

4. Run a save play

Latch posts to Slack, writes the risk row, books a calendar hold, and leaves a Gmail draft. It never sends the customer email for you.

5. Keep the proof

Every step stores a real ID. If a step fails, Latch stops and rolls back what it can. The board stays honest.

What “good” looks like

Missing proof ID → the play goes red. No fake greens.

Partial write → Latch records a failure row and stops downstream steps.

Customer email stays in Drafts until a human sends it.

You can force a Slack failure to prove rollback works.

Tools

Built around tools you already use.

AppRoleStatus
GmailRisk signal in · save draft out (never sends)connected
Slack#cs alert · stores message_ts as proofconnected
Google SheetsRisk ledger · OPEN_SAVE / FAILED_* rowsconnected
Google CalendarSave-call hold on the owner's calendarconnected
Stripe (test)Second trigger path · signed webhooksconnected
HubSpotRisk record instead of Sheets ledgerplanned
IntercomConversation-level churn signalplanned
Create workspace Open app