Every engagement ends with an approved design.
Draft the agent’s conversation in the client workshop, then hand the build team a design the client has already approved.
Klate opens to everyone soon. Until then, a person answers every email.
People at these firms design in Klate
The argument is always about behaviour nobody wrote down.
Klate is where a consultant designs the agent’s conversation, branch by branch, down to the hand-off to a human, and gets the client to approve it before the build starts. A deck describes the agent and a Miro board draws its shape. Neither pins down what the agent does, so month four becomes a change-request fight you usually absorb.
One document, from kickoff to handover.
- Step 1
Run the workshop in the design
Draft on the canvas while the client talks. The room reacts to each branch as it appears.
- Step 2
Shape the draft between sessions
Describe a flow and the assistant writes the paths, turns, tool calls and brief, waiting on your approval for every change.
- Step 3
Put it in front of the client team
Invite them by email and they browse and comment for free. Roles are set per person, so a client can read everything and edit nothing.
- Step 4
Get the sign-off
The sponsor approves from a private read-only link, with no account to create. The design locks, and the name, the time and the note stay on the record.
- Step 5
Hand it to the build team
Whoever builds it reads the tool calls and failure paths off the same page. When the scope shifts, there is an approved version to point at.
Built for a firm with many clients.
Every client in its own space, all under one login.
Separated by client
Each client is its own customer in Klate, with projects, brand, designs and a tool library of its own. People from one client never see another client’s designs.
Viewers are free
Fifty free viewers per workspace on paid plans. Only the people who edit need a paid seat.
Your seat travels
Pro is personal and follows you into any workspace that invites you.
Locked to their domain
Restrict a client’s customer to their own email domain. A link forwarded outside it grants nothing.
Stored in the EU
Designs, account data and uploaded files are all stored in the EU. AI requests go to US model providers.
No connection to their systems
Tool calls are written as examples, results included, so Klate never needs access to a client system.
The full procurement answers are on the security page.
Asked before the client kickoff.
Can my client approve without creating an account?
Yes. The sponsor opens a private read-only link and approves, with no account created. Browsing and commenting take a free viewer sign-in.
Who owns the workspace, my firm or the client?
Your firm by default: each client is a separate customer, and their people see only their own designs. If a client wants long-term ownership they move to Team, which includes three editor seats, and your seat comes out of their subscription.
We sell our own method. Does Klate replace it?
No. You fill Klate with your own brief format and your own review ritual, and the client signs off on your method. Klate sits upstream of the build, so you can design before the client has picked a platform.
Your method, approved by the client.
Run your next client workshop inside the design.