Settle the whole conversation before your platform touches it.
You build what clients half-describe. Klate settles every turn and failure path in one document the client approves before your build starts.
Klate opens to everyone soon. Until then, a person answers every email.
People at these vendors design in Klate
Settle the design where change is cheap.
In Klate you design the agent before anyone builds it in Sierra, Decagon or your own stack: example turns, every branch and the tool contract behind each answer, approved by the client before the sprint. Today the only place to show a client the agent is the platform you build it in, so the design argument lands where a change costs a sprint. In a document, adding a path takes minutes.
Your build starts from an approved design.
- Step 1
Map the whole flow
Example turns on branching paths, the whole shape on one surface. The client sees the agent’s behaviour before anyone opens the platform.
- Step 2
Specify the tool contracts
Method, endpoint, auth, side effect, idempotency, what it returns and what it says on failure. You can specify a call before the API exists, and filling it in is what surfaces the third system nobody mentioned.
- Step 3
Design the failure paths
Fork from any turn: the lookup times out, the API returns the wrong customer, the caller has lost patience. Handing over to a human is a real ending with a turn of its own, designed alongside the happy case.
- Step 4
Get approval before the sprint
A stakeholder approves from an emailed link, with no account to create. The design locks, and reopening it is recorded like every other step.
- Step 5
Build against it, and keep it current
Your coding agents read the full design over MCP and write changes back, and in Claude the design renders in the chat as a readable document. When scope moves, re-approval is one emailed link.
Specified the way your engineers wish clients wrote.
Everything a build needs sits on the turn it belongs to.
Response budgets
Turns and tool calls carry response-time budgets in milliseconds, set at design time.
Structured content
Eleven block types, validated server-side as one schema, so a turn parses end to end.
Shared libraries
Tools, forms, cards and subagents are specified once per client and reused across designs.
Version diffs
Named versions compare turn by turn, so what moved since sign-off has an exact answer.
Approval locks
An approved design rejects edits until someone deliberately moves it back to draft.
Free approvers
Clients approve from an emailed link, without an account or a seat.
Asked before the first sprint.
Doesn’t this become a second source of truth that goes stale?
A design goes stale when updating it costs more than ignoring it. In Klate a change takes minutes, compares turn by turn against the approved version, and can be re-approved by email the same day. Coding agents read and write the same design over MCP while the build runs.
Does Klate generate our platform configuration?
No, there is no export to a platform. Over MCP your own tooling reads the design in full and generates whatever your stack needs.
Can we bring Klate into client engagements?
Yes. Run the workspace yourself, or let the client own it with your team joining as editors. Each client is a separate customer with its own designs and tool library.
What does it cost for a team like ours?
Team includes three editor seats, and more can be added, up to fifty. Reviewers and approvers cost nothing, and the free plan is permanent.
Settle it before you build it.
Send us one flow your client needs, failure paths included, and we will show you how it looks as a Klate design.