Two people, one agent
You set it going. Your colleague picks it up, redirects it, and neither of you has to explain the thread to the other. Say why you turned something down and it becomes a rule — not for you, for everyone.
Two people, one agent
Your messages, documents, tasks and the tools you already use, in one place — with agents alongside your team, doing the work on a schedule and bringing you what needs a decision.
Automations
Automations
Choose from real agents that take the busywork off your team, or add capability it never had.
Every agent belongs to a team and runs its own set of jobs, on its own cadence. Turn on the ones you need, where you need them.
Chief of Staff
Weekdays 08:00 · before every meeting
One voice for everything your agents did. A brief each morning, written for you rather than for the team, and prep waiting before each meeting in your calendar.
The platform runs these from the moment you sign up. Everything else is yours to turn on.
It reads up on you
Loam researches your company as you sign up, and has something to tell you about your market before you have finished looking around.
It keeps itself current
Connect a tool once and what Loam knows about it stays fresh. There is no sync button, and no one has to remember to press it.
It remembers the decisions
What was decided, by whom, and why — picked out of the conversation you were already having. Nobody types it in.
It gets you ready
Before a meeting on your calendar, what you need to know about the people and the history is already waiting.
An agent drafts the post, writes the proposal, finds the fix. Then it stops and asks. Accept it, edit it before it goes, ask it a question, or bin it — and if it needs more than a yes, it becomes a task on the board with the reason it is waiting written on the card.
Say no and say why, and that becomes a rule — not for you, for everyone. Your rules always apply, and what worked carries more weight than what did not. Every agent keeps a page of what it has concluded, so you can read its reasoning rather than trust it. Experiments end promoted or retired; nothing sits half-finished.
Automations
A team of agents, each with their own week.
AI assistant
Ask in the channel you are already in, from your IDE, or from your phone. Same answers, same rules about who sees what.
Does any task
One assistant, the same answers, the same rules about who sees what.
Run a skill with a slash command. `/catchup` tells you what you missed.
AI assistant
One question. The answer, and where every part of it came from.
CRM
Every person and company you deal with, inside your company and outside, on one record that the work keeps current.
Not built — The graph behind this — people, companies and the relationships between them — is real today. The screen is not. /platform stays in WIREFRAME_ROUTES until it exists.
One company's record, from first contact to renewal. Every line arrived from work somebody was already doing.
March
They email your founder for the first time
Connected mail
March
A record appears, with the people on the thread
Loam
April
An intro call goes in the diary
Connected calendar
May
Your team agrees the terms in a channel
A channel in Loam
May
The decision is recorded, with who made it
@loam
June
The signed agreement lands on the record
Connected drive
August
An agent reads the record and preps the renewal
An agent
Big companies buy a customer data platform to get one view of a customer. This is that, for everything your business deals with.
CRM
Every line on this record arrived by itself.
Knowledge
Loam remembers every document, conversation and decision you make, in every tool you use. It connects it all and keeps it fresh.
Slack, email, docs, CRM, calendars, support tickets — Loam plugs into everything your team produces and normalises it into one live, governed stream.
Your data, where it lives. Loam reads — it never owns.
01 / 05
Your ultimate knowledge base, made automatically.
Communication
Your Slack, your email, your WhatsApp — bring them all. Or use ours, and stop explaining your company to your software.
A huddle in a Loam channel. Two people, one agent, the transcript running, and the document somebody just asked about.
One channel in Loam
The agent in the call
It is in the room with you, answers when asked, and picks up what you agreed to do.
The transcript
Every call is transcribed as it happens, and everyone sees that before they speak.
The document
Someone mentions last quarter's plan. It is on screen before anyone goes looking for it.
Afterwards
What you decided is on the record, and nobody had to write it up.
An outside tool carries the words and nothing else. In here the room carries the context, the record, and the people and agents who can act on it.
No pasting, no "here's the context", no re-explaining the decision you made on Tuesday. Your agents were there on Tuesday.
Communication
Two people, one agent, and the document nobody had to go and find.
Collaboration
All the best collaboration tools in one place, with an army of Loam agents to plan, advise or simply do it.
You set it going. Your colleague picks it up, redirects it, and neither of you has to explain the thread to the other. Say why you turned something down and it becomes a rule — not for you, for everyone.
Two people, one agent
The other half of multiplayer. Several agents working at once, each on its own job, and everything that needs you waiting in one place.
One person, many agents
People and agents in the same document at once. An agent drafts, you edit over the top, and nobody is sending versions around.
Pages, written together
Drop in a raw idea. An agent researches it — seeing only what you can see — and brings back a scoped, sourced plan. Approve it, and it becomes a ticket.
Research it, then make it a task
Two people. One agent. One rule that stuck.
Project management
Ideas, conversations and your agents' own findings all become tickets on one board — where the person doing the work is sometimes not a person.
Ideas is a real column, not a metaphor. Time is a sort inside a column, never a column of its own.
Ideas
Raw and half-formed, written down before it is lost.
To do
Scoped, sourced, agreed.
Active
Someone is on it.
Blocked
And it says why.
Done
With the decision that got it there.
The board, with agents among the people
A raw idea goes to an agent. It researches under your permissions rather than its own, and hands back something scoped and sourced. You approve it, and it is a ticket.
With its status, its last run and its next one on the card. Real data, not a badge.
Half of this board belongs to agents.
Security
Loam's security intelligence scopes access dynamically — per room, per conversation, per memory — across everything your company knows, source permissions honoured.
Two people ask the same thing on the same day. What comes back depends on what each of them is allowed to see.
“What are we paying the new engineering hire?”
The founder asks
The number, the band it sits in, and the thread where it was agreed.
A new starter asks
That this is not something Loam will discuss with them.
Two accounts, one question, two replies
Every answer is checked against what you may see before the model is asked anything. It is not a filter on the way out.
Not per folder, not per file. Every memory carries its own scope, so your company can share far more of what it knows rather than less.
Loam sets the scope from where the conversation happened. The model does not get a vote.
An agent has the access of the room it works in. Send one to research something and it sees what you see, and nothing else.
Every decision, allowed or refused, with its reason.
Where it lives, who processes it, and what we do with it.
Same question. Two people. Two answers.