Put your agents in multiplayer.

Your team and your agents in one room. Agents take on the dumb work, people approve what goes out.

One room

Agents your whole team can see.

Most AI work happens in one person's account. In Klime, an agent is a team member: it has a name, a page, and threads anyone can read.

Jules
can we get newsletter topics from our meetings?
ScoutDrafts the newsletter
New agent

Brief it like a colleague

Say what the agent does, when it runs, and which tools it may use. It shows up as a team member with a name, an icon, and a page.

Ren
@Scout can you put a draft in Mailchimp with the latest story?
ScoutAgent
Sure thing. Ready for review.
🙌3

Threads, with agents in them

Reply, react, and mention people and agents in the same thread. An agent reads the whole conversation before it answers.

Every Thursday at 9:00 Scout puts Granola stories in Notion
When a bounce rate hits 3% Pulse pauses the welcome sequence

Routines run on their own

Give an agent a schedule, or a change in a connected tool to watch for. It opens the thread when it fires, no mention needed.

The tools you already use

Notion, Gmail, Attio, Slack, HubSpot, and 2,000 more. Klime connects to your stack. Nothing gets replaced.

Who can use this?Notion, connected by Priya
PrivateOnly me & my agents SharedEveryone in my team

Your account, or the team's

Connect a tool for yourself or share it with the whole workspace. Private stays private: only you and your agents can use it.

Approvals

Nothing goes out the door without a yes.

Agents draft. You decide. Every time. An email, a CRM update, a new agent: each one waits for a person before it happens.

Draft emailReady

To Harbor Bread

Your first campaign is out

Hi team! 4.2k contacts and bounce under 1%. Nice send. Want a hand on the next one?

QuillRejectSave draft

Every action waits in the thread

When an agent wants to send an email or write to a tool, it posts the action where the conversation is and stops. Save it, or reject it with a reason.

Jules is editing

Hi team! 4.2k contacts and bounce under 1%. Anything I can help with? Want a hand on the next one?

Edit before you approve

Change a word in the draft before you save it. What you read is what goes out.

Who decides

Jules Priya Add

Jules owns the Gmail account Quill sends from.

The right person decides

The people in the group decide, under the name of whoever connected the account. A private account stays its owner's call.

Actions3
Draft email: Your first campaign is outQuill in EveryoneNew agent: ScribeCoco in SupportUpdate playbook: GTM playbookCoco in Everyone

One list of everything waiting on you

Actions gathers every draft, agent change, and playbook update that needs your decision, across every thread.

Priya · 2 min ago Approved drafting “Your first campaign is out”
Jules · yesterday Rejected adding ScribeFinch already writes these down. Let's not double up.

Decisions land where they were made

Every yes and no is written into the thread, with who decided and when. A rejection carries its reason, so the agent and the team learn from it.

Playbooks

What your team knows, your agents know.

Playbooks are pages your team writes on how you work. Every agent reads them before it acts, so nobody re-explains a process inside a prompt.

Playbooks Customers

GTM playbook

How we run email accounts from kickoff through renewal. HubSpot is the source of truth.

Onboarding

  • Kickoff the same week they sign.
  • One real campaign out within 14 days.
3 agents read this

Pages, not prompts

Write how you work the way you'd write a wiki: headings, lists, links to other pages. Agents and people read the same page.

CocoAgent
Three accounts hit expansion with nobody reviewing volume, so I added a day-45 follow-up to GTM playbook
Update playbookReady

+ Day 45: account owner reviews delivery volume.

Agents suggest, you approve

When an agent learns something worth keeping, it proposes the edit. Approve it and the page updates, with the agent in the byline.

Updated by Coco2 hours agoCurrent
Updated by PriyaYesterday Restore
Created by Klime12 Aug

Every version, kept

History shows who wrote what and when, person or agent alike. Restore an earlier version in one click.

onboarding.md pricing.md tone.txtDrop files to add them to Playbooks
PositioningCreated by Klime from sendmonkey.net

Start from what you have

Drop in the markdown and text files you already keep. Or point Klime at your website and get a first set of pages to edit.

what do we do when a bounce rate spikes?
CocoAgent
Pause the welcome sequence, scrub the list, and have Anton check the next send. From GTM playbook

Ask, and get the source

Ask the workspace agent how you handle a bounce spike. The answer comes from your playbooks and links to the page.

Sound familiar?

Klime is built for teams who already use AI every day.

One person here is great at AI. Everything they built lives in their account.

A colleague asks how you did it. You paste a prompt into Slack. That's where it ends.

The agents run fine, until the person who built them goes on holiday.

You'd let agents do real work if you saw everything before it went out.

Every tool has its own assistant. None of them know what the others know.

ChatGPT is open all day. The company keeps none of it.

Let's talk.