A sales agent with CRM access can put wrong data on every lead in a list before anyone opens a record. Kortix is the open-source AI Operating System that runs the agent on its own cloud computer, and its write-back to HubSpot leaves a research note on the record and a draft a person still has to send.
Kortix’s own inbound flow sweeps HubSpot every 15 minutes, and the write on each record is what the next sweep reads.
New lead
The agent reads the lead, adds what it found, and leaves the deal fields where they were.
| Field | Before the sweep | After the sweep |
|---|---|---|
| Company | Acme, 40 seats, from the form | Acme, 40 seats, hiring two platform engineers |
| Research notes | empty | three lines, each with a source |
| Follow-up draft | none | written, waiting for a person |
| Deal stage | new | new |
| Owner | unassigned | unassigned |
One lead fails
Each lead in a sweep is handled as an independent unit, so a research or drafting failure on one never blocks the others.
Second sweep
Sessions share no state between sweeps, so the marker written onto the record is the only thing the next run can read.
The sweep, the marker, the approval gate and the scoped credentials, quoted from the lead follow-up flow Kortix publishes.
A scheduled trigger sweeps HubSpot every 15 minutes for new leads, and each firing spawns a fresh session in its own sandbox.Sessions don't share state between sweeps: the marker written back onto each HubSpot record is what carries forward.Only the drafts it produces are written back out.The agent researches and drafts freely, but nothing goes out on its own: every follow-up stops at a human approval gate as a draft for a person to review and send.Credentials are encrypted in the secrets manager and injected at runtime, scoped to the agents you grant them to.Kortix runs the agent and keeps every record of it; AiSDR and Artisan sell the sending. The rows that differ are the ones about what a person can read afterwards.
| Product | Open source | CRM systems | What the write covers | What sends on its own | The record of a write | Who sets the rule | Cost shape |
|---|---|---|---|---|---|---|---|
| Kortix | Yes | HubSpot, through a scoped connector | Research notes on the record, plus a draft | Nothing; its lead follow-up flow holds the send for a person | Every action is recorded; log access depends on plan | You, in files a change request reviews | Credits for the agent computer, per second while it runs |
| AiSDR | No | HubSpot; Salesforce on larger plans | Sequences, replies and contact activity | The campaign, once you launch it | Contact activity logging in the CRM | You pause outbound; plan features agreed with sales | $1.50 per person contacted |
| Artisan | No | Salesforce and HubSpot, both directions | Replies handled, meetings booked for reps | Ava runs by default, adjustable in Artisan | Audit logs, named on its pricing page | You, through approvals and escalation rules | A quote sized by lead volume, mailboxes and seats |
Rival cells come from each vendor’s own pricing page, checked October 2026. Kortix cells come from its published lead follow-up flow and its docs. The Kortix vs AiSDR page takes the per-contact trade-off further.
Open-source AI sales agent · Approval controls · Self-hosted AI sales agent · Kortix on GitHub
Short answers on what exists, and what each one charges.
Yes. AiSDR and Artisan sell an agent that sends outbound for you, and Kortix runs a sales agent you own, which writes research notes and a draft into the CRM; its lead follow-up flow holds the send for a person. The comparison hub sets the managed tools beside it.
AiSDR bills $1.50 per person contacted, and Artisan quotes per account with no published rate. Kortix bills credits for the agent computer, per second while it runs and nothing while it is stopped.
Start with one record and one rule on the tool call that touches HubSpot.