How it works

DIY - At your own risk.

Free under the DouxProcess kit license. The DouxProcess™ name and Doux Certified™ badge are reserved for licensed agencies. Read the license

The machine

01

We take the language model.

It reads. Emails, carrier letters, supplementals, client texts. It doesn’t decide. Your procedures do.

02

We build your workflows.

Your procedures manual, built into workflows. Quote. COI. Endorsement. Payment. Renewal. Same steps, every account, every time.

03

We put them in the cloud.

Dozens of jobs running at once, each doing one thing.

04

They run continuously.

Every two minutes. Nights, weekends, holidays. Checking every inbox and every open file.

05

They plug into what you use.

Your agency management system. Accounting. Phones. E-signature. Carrier portals, under your agency’s own logins.

06

You approve.

Your account manager signs off. Every step documented, time-stamped, on the file.

Behind the curtain

What runs behind one agency. Every month.

The same stack a live agency runs on today.

The language modelReads every email, form and letter. Subscription plus usage.
Cloud workers, 24/7Always-on machines. Quoting, filing, packets, and the one that hands out the work.
Browser machinesSecure browsers in the cloud that work carrier portals and your CRM under your logins.
Scheduler, mail sorter, dashboard, backupsThe small machines that keep the big ones honest.
DatabaseEvery file, every step, every timestamp. The record.
AccountingYour books, connected. Commissions, fees, refunds.
CRMPipelines and follow-ups.
Phones and phone menuThe line your clients call instead of your cell.
E-signature with paymentSign, sign, pay. Then the bind is requested.
Agency management system add-onsThe connections into your system of record.
Running itBefore anyone builds a single workflow.
Included

All of it runs on us and is included in your price. Your own AMS and email seats are not.

Do the math

Build it. Staff it. Or Doux it.

Build it yourself
Months before day one
  • Running ityour bill
  • Developer who knows insurancefull-time

And when your developer quits, so does your agency.

Staff it
$4,500 / mo
  • One US licensed rep, on contract~$4,500
  • Hours a week40

Forty hours. One desk. A client calls at 5:01.

Doux it
$2,500 / mo
  • Builtdone
  • Running24/7
  • Producers included3
  • Each additional producer+ $500 / mo

Doesn’t go home. Doesn’t call in sick. Same procedure on every account.

Free · DouxProcess kit license

The recipe cards. Eight of them.

Every workflow’s procedures, written as one file you load into Claude, ChatGPT or Gemini. Nothing to install. Take them.

Inbox triageSorts the inbox, flags losses and cancellations first.Free skill →CertificatesChecks the request against the policy, drafts the certificate.Free skill →EndorsementsBuilds the carrier change, tracks the follow-up.Free skill →Payment follow-upCatches non-pay notices, counts the days, drafts the reminder.Free skill →QuotingReads the application once, checks appetite, compares quotes.Free skill →RenewalsRenewal against expiring, line by line. Flags when to remarket.Free skill →Call coverageWrites the busy-line greeting, the switch and the undo. Ranks the call-backs.Free skill →Stuck signingReads the signing record, proves the packet, resends the same link.Free skill →
Free · DouxProcess kit license · The whole kitchen

DIY - At your own risk.

Everything we learned building DouxProcess inside a real agency, written for an in-house programmer. Load it into Claude and it teaches the build step by step and checks the work. Comes with a working starter you can run today: no installs, fake mail, the full approve-and-audit loop.

Download the builder kitOne-file version for ChatGPT or Gemini (.md)

Watch it installed: Claude · ChatGPT · Gemini

Downloads open after you sign the DouxProcess kit license: you build it, you run it, you answer for it.

Before the first run

Installing it is half the job. The first run needs these from your own systems. Gather them first: a minute or two each.

1. How you do it today, written downFrom you
  1. Pick ONE job you repeat every week.
  2. In a blank document, write it the way you'd tell a new hire: where it arrives, what you check, who approves.
  3. File › Download (or Save as) › PDF.
  4. Attach it with: Help me plan this. Every change request on service@, drafted for my approval. I don't code, and I want to approve everything.
2. Four facts about your setupFrom you
  1. Your email: the part after the @ in your work address.
  2. Your agency system: the name on its sign-in page.
  3. Where it could run: a cloud account, an office server, or a laptop for now.
  4. Your programmer's language, if you have one.

Step 0 runs on fake mail, so nothing from your systems is needed to start. Access to your mailbox and agency system comes later, granted by whoever runs each. Nobody ever pastes a password into the chat.

  1. 01ArchitectureThe one loop every workflow runs on. The model proposes exact actions; code checks them; a person approves.
  2. 02Passwords and keysWhere every secret lives, how code reads it, and why the model never sees one.
  3. 03DatabasePostgres or Supabase schema, row-level security, an audit log nobody can edit.
  4. 04EmailYour email, read-only, locked to one mailbox.
  5. 05Model callsChecked JSON, never prose. Cost, caching, choosing a model.
  6. 06Management systemMatching mail to the right client. Search, write, read back.
  7. 07Carrier portalsDriving a portal by what a person sees. Two-factor stays human.
  8. 08Approval queueOne screen. Licensed approval for anything that leaves the agency.
  9. 09DeploymentScheduled, monitored, backed up. Silence means fine, never dead.
  10. 10TestingFixtures from real cases, shadow mode, the wrong-action rate.
  11. 11ComplianceLicensing, E&O, data security, texting consent. The go-live checklist.

The same procedures we run on: the model proposes, your procedures decide, a licensed person approves anything that leaves the agency. Nothing in the kit removes that line.

Qualify