Solutions · Sales
You have the conversation.Machine does everything around it.
The research, the pre-call brief, the notes typed back into the CRM, the follow-up drafted from what was actually said. An agent picks up the work on either side of the call. Set sending to Ask, and nothing leaves the building until you say yes.
Drafts, not sends · every action logged · your CRM, your rules
- Reaches
- Your CRM, your inbox, your sheets
- Credentials
- Kept server-side, never in the machine
- Sending
- Set it to Ask and the run waits for you
- Every call
- Lands in an audit record
01The handoff
Hand off the half of the job that isn't selling.
Nobody joins a sales team to update a CRM. But your pipeline is only as good as its data, and the data is only as good as the last hour someone spent on admin. That hour is what you hand off.
Job 01
The pre-call brief
Before a meeting, it pulls together what you would have skimmed anyway: the account history in the CRM, the open threads in your inbox, what the company has said in public since you last spoke, and the two things that changed. One page, in your inbox, before the call.
Job 02
Call notes into the CRM, in your fields
Paste your notes or drop the transcript in a thread. It writes them into the right record, moves the stage, sets the next step, and flags anything it can't place with confidence instead of guessing at a picklist value.
Job 03
The cleanup nobody gets to
Duplicate accounts. Opportunities with a close date in the past. Contacts with no owner. Deals that haven't moved in six weeks. You get the list with a proposed action on every row, not a dashboard telling you the list exists.
Job 04
Account research that's actually current
It reads what the company has published, checks it against your own qualifying criteria, and tells you whether the account fits and why. When it doesn't fit, it says so. That's often the more useful answer.
Job 05
The follow-up, written from what was said
Drafted from the notes and the account record, not a template with a merge field. It lands in the CRM or your inbox as a draft, and you can require approval before anything sends.
Job 06
Renewals and expansion, watched for you
A scheduled session checks which contracts are coming up, which accounts have gone quiet and which have grown. Then it opens a thread with the shortlist and a first draft for each account.
02What comes back
A worklist with the next step already drafted on every row.
A report tells you what's wrong. A sales session hands you the rows and the exact thing it wants to do with each one, already drafted and waiting for your yes. That difference is the whole product.
| Account | Stage | Last touch | Drafted action |
|---|---|---|---|
| Northwind Logistics | Proposal | 31 days | Follow up on the pricing question |
| Acme Robotics | Discovery | 19 days | Re-book: champion changed role |
| Globex Health | Negotiation | 12 days | Send the security review pack |
| Initech Retail | Proposal | 44 days | Close-lost: no reply to three touches |
Drafted isn't sent
Every message it writes lands as a draft in the CRM or your inbox. Want a hard stop before anything goes out? Set the send action to Ask, and the run pauses at that call until you answer.
It shows what it read
Every row carries the record and the thread it came from. A claim about an account that you can't trace to a source isn't one you should act on, so it doesn't make one.
It shows up where you already work
Connect Slack and the shortlist lands in a thread you can push back on. Reply in that thread and you're talking to the same session, not starting over.
03Where it reaches
Your CRM and your inbox. No keys handed over.
A sales agent is only useful if it can reach the systems your pipeline lives in. Connect each one once for the whole project. The credential is decrypted on our side and attached to the outbound call, so it never lands in the machine the model is driving.
Salesforce, HubSpot
Both are in the Easy connect catalogue. Click through the OAuth screen and the connection belongs to the project. It reads accounts, opportunities and activity, and writes back only the fields you allow.
Gmail and Outlook
It reads the threads on an account and drafts the reply. Reading and sending are separate actions with separate answers, so "may read the thread" never quietly means "may send as me".
Google Sheets and Drive
The forecast in a spreadsheet, the pricing sheet, the account plan. It reads them as source material and writes the worklist back where your team already looks.
Slack
The one live channel. Mention it in a thread to start a session, and the answer comes back to the same thread. Microsoft Teams is built, but stays off until your deployment turns it on.
Whose account it acts as
Pick one project-managed connection the whole team shares, or personal authorization where every member acts as themselves. With personal authorization, an automated principal can't act at all.
Easy connect covers 3,000+ apps through their own OAuth screens. If your sales stack has something outside that catalogue, like an internal quoting service or a regional CRM, you can still reach it through OpenAPI, GraphQL, raw HTTP or a remote MCP server.
04How it runs
Before the call, mid-week, and at 07:00 on a Monday.
Same session machinery, started three ways. What changes is when it runs, never what it's allowed to do.
01 · On demand
"Brief me on Northwind before eleven"
Ask in a Slack thread or in the web app. The session starts, does the reading, and replies in the thread with the brief attached as a file.
02 · Human-assisted
It stops at the send
Set the send action to Ask and the run holds at that call, showing you the message and who it's going to. Approve and the same call completes. Deny and the session carries on without it.
03 · Automated
The Monday list, written overnight
A cron trigger runs the cleanup and the gone-quiet sweep before anyone's at a desk, then posts the worklist to the channel. Each trigger names the agent it runs as, so the overnight session gets no more reach than the daytime one.
05Control
Nothing goes to a customer without your yes.
In sales, an agent's mistake is one your customer sees. So here are the defaults, stated plainly instead of reassuringly.
01
Approval gates are off until you turn them on
Out of the box, Machine is permissive: an action runs unless you've said otherwise. In a sales project, the first thing to do is set outbound actions to Ask and destructive ones to Block. We'd rather tell you that than let you assume the safer default was picked for you.
02
An approval pauses the run. It doesn't fail it.
A gate that throws an error teaches an agent to work around it. A Machine gate holds the call open, so you answer while the session is still mid-task, and it picks up exactly where it stopped.
03
Rules can read the arguments
"May the agent send email?" is rarely the real question. Conditions match on the values inside the call, so a rule can allow email within your own domain and stop everything else. Anything a rule can't decide falls back to less access.
04
Connector credentials never enter the machine
The sandbox holds one project-scoped Machine token and no third-party keys. Your CRM credential is decrypted server-side and attached to the outbound request. Turn a connector off and it takes effect on the next call. There's nothing in the sandbox to rotate.
05
Every call it made, and who allowed it
Each record holds the connector and exact action, the agent, the person or trigger behind the session, the outcome, and who released a held call. No path to a connected tool skips the step that writes the record.
06Other teams
Same machine. Every other team.
One project, one set of connectors, one memory that keeps growing. Each team writes the skills for its own work. Nobody builds a second system.
- MarketingProduction work in your voice, because the voice is a fileOpen
- ProductFeedback turned into specs, with the evidence attachedOpen
- EngineeringReproduce it, patch it, open the change requestOpen
- FinanceThe close, the reconciliation and the variance note, with the working shownOpen
- PeopleScheduling, kits and onboarding, never the hiring decisionOpen
- ITRunbooks that run, and a platform that passes your reviewOpen
- Data ScienceA real machine, a real query, an analysis you can re-runOpen
- All solutionsEvery team on one page, plus the rules that never change between them.Open
Sales
Give it the admin.Keep the conversations.
One governed platform for your sales agents. Any model, your keys, every action on the record.
- One machine per session
- Lands as a change request
- Every action recorded