What it touches, and what
it can do without you

What does it touch?

The systems your answers are already scattered across, and nothing else. In practice that is your management system, your email, your carrier and MGA portals, and your CRM. Payments, e-signature and phone are in build and are described honestly as such on the integrations page.

With your credentials, inside your environment. The logins live in your own tenant. We do not hold a copy, and no other agency's instance can reach them. Where a portal offers no usable API, the agent operates the portal the way a person would — same login, same screens, same appointments.

It replaces nothing and migrates nothing. Your management system stays the book of record. Every policy, note, task and certificate lands exactly where it always did. There is no Doux database holding a second copy of your book. Switch Doux off tomorrow and your book is untouched, because your book was never anywhere else.

Writes are read back. Management systems sometimes commit a record and then fail while answering, so Doux never treats an error as a failed write — it re-reads the record and confirms the real end state before anything is reported as done.

What can it do without me?

The clean line, and the one worth remembering: on its own it does the research. It does not make the decision. Reading, gathering, cross-checking, assembling and presenting all happen unattended, because none of them change anything. That is the part that was eating your week, and it is the part that comes back.

Anything that changes something stops and asks, with the evidence attached — what it found, where it found it, and what it recommends. Anything irreversible, anything that leaves the agency, and anything that changes coverage always requires a person, regardless of how many times you have approved one like it before.

You author the rules, one at a time, explicitly. Doux starts by proposing and executing nothing at all, so you can watch whether its judgement matches yours before it is trusted with anything. When you have approved the same kind of call enough times, it offers to handle that one on its own. You confirm once, deliberately. Everything outside the rules you wrote keeps coming to you.

And the shape of a good day: about eighty percent of the work arrives done. The last twenty percent is the part that genuinely needed you — which is the offer, not a caveat.

What is Doux?

Doux is an agent team, not an assistant. A chatbot answers a question; Doux signs in to your management system, reads the contract exhibit, checks the forms actually endorsed, assembles the picture and puts the recommendation in front of you. The output is an answered question and finished work in your book of record, not a draft you still have to execute.

It is built for one industry: commercial property & casualty agencies in the United States. That narrowness is the point. It knows what an ACORD 25 is, why a blanket additional insured form that stops short of completed operations is a problem, and what a stale experience modification does to a renewal.

And it is built for whoever holds the desk where the final call stops — the principal, or whoever leads service, billing or certificates.

How it works

• Work arrives where it always did. An email, a carrier notice, an x-date coming due, a voicemail, a declined payment. Nothing to forward and no new intake process.
• A specialist is opened for each place the answer lives. The management system, the policy, the carrier portal, the contract, the ledger — whichever the question needs.
• They walk in parallel, with your credentials, in your environment. This is the part that took a person twenty minutes and takes a program seconds.
• You get one assembled picture, with the recommendation and the evidence attached.
• Everything is written down — what was done, on what basis, and who approved it.

The orchestrator

You do not manage a roster. You make one request — "get me ready for the Henderson renewal" — and Doux breaks it into parts, opens a specialist for each, lets them work in parallel, and hands back a single finished package.

There is no fixed headcount. The team is assembled around the job. A renewal might open four specialists; a certificate request opens one. They close when the work is done.

Each specialist gets only the access its desk needs. The certificate specialist does not hold the billing credentials, which is both a scoping decision and a containment one.

Approvals and rules

Doux starts by proposing and executing nothing at all, so you can watch whether its judgement matches yours before it is trusted with anything. That period is not a trial gimmick; it is how the rules get written.

When you have approved the same kind of call enough times, Doux offers to handle that one on its own. You confirm once, explicitly. Anything outside those rules keeps coming to you. Irreversible actions — anything that leaves the agency or changes coverage — always require a person, regardless of how many times you have approved one before.

Doux vs Claude on its own

Claude is the foundation Doux is built on, and you can run it yourself. Doing that gives you full control and, with it, full responsibility: you would be building the insurance knowledge, the drivers for your management system and carrier portals, the deterministic action layer, the approval queue, the audit record and the tenant isolation.

Doux is that foundation already fitted to an agency, with the boundaries built in. The security page sets the two out side by side, row by row.

Doux vs a chatbot

A chatbot produces text from what you paste into it. You still do all the walking — you open the management system, find the policy, read the forms, check the portal — and then you paste the result in and get it worded nicely. The research, which was the expensive part, is untouched. Only the drafting moved.

Doux does the walking, and then produces state changes in your systems — a policy recorded, an endorsement ordered, a certificate delivered, a task closed — each one read back and verified, each one attributable.

Doux vs workflow builders

A workflow tool runs the path you drew. It is excellent when the work is identical every time, and it breaks the moment reality is not: a contract that words the additional insured requirement differently, a carrier that returns a binder with the DBA missing, a renewal where the payroll is stale.

Doux reads the situation and decides, then acts through a deterministic layer. The judgement is flexible; the execution is not.

Doux vs your management system

Your management system is a system of record. It stores what happened; it does not do the work. Doux is the layer that does the work and writes the result into it. They are not alternatives, and Doux is not asking you to leave yours.

FAQ