Kylon vs Attio
Attio works inside the CRM. Kylon works where the team talks.
Kylon is a workspace where agents sit with the team, read the thread and the tools you connected, and hand back the records, the dashboard and the email draft for one person to approve.
01 Which one is the right answer
Not every team should pick the same one.
Attio is the right answer when
The team wants the data model itself to be the product: custom objects shaped to how the business actually works, fast views over them, and an assistant that operates on that model.
Kylon is the right answer when
The work spans more than the CRM. The context is a mailbox thread, a document and a chat at once, and the team needs to see what was asked and what came back, not just the record that changed.
02 Operating model
How each one works
Every statement about Attio below cites Attio's own documentation. Checked 2026-09-16.
Where the work happens
Data sits as records inside standard or custom objects, worked from all record views, individual record pages and lists, in table or kanban form. A record page combines its attributes with activity, emails, meetings, notes, tasks, files, calls and relationships.
Source: Define your data model: objects, lists, and views, Attio
The work happens in the room where the team already talks about the account. The request, what the agent read, and the records it produced are one thread that people and agents both read.
Who keeps the records current
Records arrive from members with write access, imports, integrations, workflows, Ask Attio, email forwarding and email or calendar sync. Attio enriches person and company attributes where source data is available and updates them as it learns more, while values entered by hand are left alone.
Source: Enriched data, Attio
An agent reads the mailbox, the calendar and the thread you granted it, then writes the contact, the company and the stage change as a proposed change you can see before it lands.
What the assistant does
Ask Attio searches and summarises records, lists, notes, calls, emails and calendar events, researches the web, builds workflows, proposes record, note and task changes, and drafts emails.
Source: Chat with Ask Attio, Attio
An agent answers with the work attached: the record changes it proposes, the view it built and the email it drafted, each with the message or file it came from.
Who approves what it does
Ask Attio asks the person who prompted it to approve proposed record, note and task changes before they are applied, and its email drafts are reviewed and sent by hand. A workflow starts as a draft and runs once an authorised member publishes it.
Source: Chat with Ask Attio, Attio
Approval works the same way and lands somewhere different. The proposal arrives in the team's thread rather than one person's chat, and a single approve control covers the records, the view and the draft together.
Reaching email and calendar
Each member connects a Gmail and Google Calendar or a Microsoft 365 account from their account settings. Attio imports eligible past and future email and events, keeps new activity in sync, shows it on related record pages, and can create people and company records according to the workspace record creation settings.
Source: Sync your email and calendar, Attio
The mailbox and calendar are workspace connections the agent reads directly, and outbound email comes back as a draft card in the thread rather than a send.
What setting up automation takes
Any workspace member can build a workflow from scratch, duplicate one, or describe it to Ask Attio. The builder needs one or more triggers, connected blocks and their inputs, and then publishing. Triggers cover record, list, attribute, note, task, schedule, webhook and manual events.
Source: Create a workflow, Attio
You describe the outcome in the room. If it should repeat, the same request is saved as a scheduled or event driven run, and its output stays in the room.
Questions people ask
- Attio already asks before it changes a record. What is different here?
- Where the asking happens. In Kylon the proposal lands in the team's room next to the discussion that prompted it, so a colleague can see it, and one approval covers the records, the view and the email draft together.
- Can we keep Attio and use Kylon?
- Yes. Connect the account to the room and the agent reads and writes through it.
- Does anything send on its own?
- No. Email is drafted for a person to send, and anything that changes a record outside the room waits for approval.
Keep reading
The record is one output. The work is the whole thread.
Put an agent in the room where the account is discussed, connect the mailbox and the CRM, and approve what it hands back.