Who you are buying from

Why we built this

Every CRM has AI in it now, and almost all of it is the same move: take software designed for a person clicking through screens, attach a model to the side, and call the result agentic. The agent gets a chat box and a slice of the API, and the first time it needs to do something structural it hits a wall that says you will have to do that in the interface.

That is not software for agents. It is the previous product with a new front door, and you can tell because the agent is a guest in it.

Building for an agent starts from a different question: if something that is not a person is going to operate your customer records, what does it actually need? It needs the whole surface, including the parts a vendor usually keeps behind an admin screen, so shaping a pipeline or defining a new kind of record is a call it can make rather than a ticket it has to raise. It needs to retry a write without creating a duplicate, and to ask what a write would do before committing to it.

And because something that writes at machine speed also gets things wrong at machine speed, the record has to answer a question a CRM built for people never had to: who asserted this? Every value here carries the actor that set it. An agent's summary is stored as that agent's claim rather than as something we know. Either can be undone, at the field.

That is the whole idea. Not a CRM with an agent bolted on, but a CRM an agent can run, built with the guarantees that makes necessary. How it works is the same argument with the tool calls in it.

Reaching a person

One address, read by someone who can act on it: hello@indraft.io. There is no support tier, no ticket queue, and no chatbot in front of it.

Expect a reply within one working day. If something is broken rather than confusing, say so in the subject line and it goes to the front.

Your records are yours

Not as a policy, as a property of the product. Everything in your workspace is exportable by you, whenever you want, in formats that other tools read. You never have to ask us for it and you never have to wait.

• Everything is exportable, at any time, by you. One spreadsheet per table, the whole workspace as one document, and a written explanation of how the files join up. It opens in Excel, Numbers, Sheets and LibreOffice with no conversion, and your next vendor can load it. Nothing is left out and nothing is trimmed to fit.
• The history comes with it. The record of who changed what, when, and how they came by it is part of the export rather than a view that only exists in our application.
• It is a button, not a request. No ticket, no export window, no negotiation about format. Above 100 MB in one file the button refuses rather than handing back a partial export, and we run it for you instead. Deletion and portability covers the rest, including erasing it just as completely.

Worth checking rather than believing. Export your workspace on day one and open the file.

What we run on, and who else touches your data

Three subprocessors, each named with what it processes and why: Cloudflare for hosting, WorkOS for identity, and Stripe for billing. No CRM record reaches Stripe. The full list is on Subprocessors, and Security covers how the data is held.

The paperwork

• Terms of service
• Privacy policy
• Data processing agreement, which applies automatically rather than on request
• Subprocessors
• Deletion and portability

Governing law is Illinois. If your procurement process needs something that is not here, ask and you will get a straight answer.