For teams that deliver client work

Your CRM should not just track client work. It should help finish it.

Agents turn every inquiry into research, proposals, reports and follow-ups, and keep the pipeline current while they do it. Your team approves before anything goes out.

Get started

The product, running

Several agents, one client record

Research, the proposal and the report are different jobs, and they disagree the moment they run off different copies of the truth. Here they read and write the same record in the room the client work already lives in, and the outbound piece stays a draft until a person approves it.

The room mockup that runs on kylon.io, with the account list open beside the thread. Companies, people and figures are invented.

Inquiry to delivered work, in one thread

Each of these starts as a message in the room the account already lives in. When it should repeat, the same work is saved as a workflow on a schedule or a record change, and every run keeps its history.

01

Inquiry to qualified record

A form or an email arrives. The agent researches the company, writes the account record with what it found, and says in the room which sources it read.

You read the record before anyone replies to it.

02

Brief to proposal

The brief is in the thread. The agent writes the proposal against it, pulling scope, history and pricing inputs from the record instead of a renamed document.

The proposal waits as a draft. A person sends it, or rewrites it.

03

Delivery to client report

A scheduled run pulls what happened this period from the tools the work lives in, writes the client report, and posts it where your team argues about it first.

Anything it could not verify is named in the report rather than estimated.

The inquiry arrives
How it goes nowSomeone copies it into the CRM later, if the day allows it
With an agent on the recordThe agent opens the record from the mail or the form and writes down what was actually asked
Research
How it goes nowFive tabs and a colleague who answered this last quarter
With an agent on the recordThe agent reads the company, your history with them and the thread above, then posts what it found in the room
The proposal
How it goes nowLast quarter's document, renamed
With an agent on the recordA draft written against this brief, with the numbers taken from the record rather than retyped
The report
How it goes nowAssembled by hand the night before the call
With an agent on the recordWritten from the same record every agent shares, on the schedule you set
Approval
How it goes nowApproval happens when someone remembers to ask for it
With an agent on the recordThe draft waits in the thread, with the evidence and the approve control in the same place
Delivery, and the record
How it goes nowThe record is updated last, or not at all
With an agent on the recordSending is the same step that writes the stage, the note and the next task

What the record carries, and who may touch it

  • One record per client, shared by every agent working the account, so the research, the proposal and the report do not contradict each other
  • The thread the work is already discussed in, rather than a separate intake form
  • The CRM you already run, read and written through its own connection. Nothing has to move
  • Mail, documents and tasks, so the follow-up lands where the rest of the client work lives
  • Memory across runs, so last month's decision does not have to be explained again
  • Scoped permissions. An agent sees the accounts and connections you granted, and nothing else

Where the result goes

CRM
Salesforce · HubSpot · Pipedrive · Close · Dynamics 365
Tasks
Linear · Jira · Asana · Trello · ClickUp · monday.com
Docs
Notion · Google Docs · Google Sheets · Confluence
Comms
Slack · Gmail · Outlook · Microsoft Teams

How it works

  1. 01

    Put an agent in the room where the account is already discussed, and connect the CRM and mailbox that work lives in.

  2. 02

    Say what should happen when an inquiry lands, in plain language. The agent researches, writes and keeps the record current.

  3. 03

    Approve what leaves the room. Sending is the step that updates the record, so the pipeline is current without a second pass.

What Kylon does not do

This is not an autopilot for client relationships. An agent does not decide pricing, does not send on its own, and does not sign anything. It prepares the work and stops where judgement starts, which is the point at which a person reads it.

Tracking the work is not the same as doing it.

Put an agent on the account, approve what leaves the room, and let the record write itself on the way out.

Get started
Setup
Connect your CRM
Outbound
Drafts until approved
Record
Written in the room