Our story

Born on a service desk. Built by breaking it.

It started with a 17-year-old and one contractor quote. Here is every step since, including the ones that went wrong.

00 · Day zero

A kid with a shortcut.

Before any of it had a name.

  1. A 17-year-old did it first.

    A part-time CSR got tired of typing the same contractor application into a wholesaler’s quote portal. So the kid scripted it. Typed once. Filled everywhere. That is the whole company. Scaled.

  2. The tools caught up.

    Claude Code put an agent on the command line. Custom MCP connectors let it work inside our software, not beside it. For the first time, the shortcut could run the desk.

01 · Orion

The brain.

July 2026. Write everything down.

  1. The inbox, first.

    Every email in the agency, read and sorted against a written rulebook. Rule one, on day one: nothing goes to a client or a carrier without a person.

  2. A direct line into the AMS.

    We built our own MCP server so the agent could read and write the agency management system itself.

    What broke24 duplicate clients. The system said error. It had actually worked. We retried.

    What it taughtRead back every write.

  3. Orion, the second brain.

    Every decision, every procedure, every lesson in one place the system reads before it acts. Its founding law: never hand work back.

  4. Clean up, out loud.

    What broke4,913 duplicate contacts in the CRM. An unattended push ran every day, unwatched.

    What it taughtA fix isn’t live until the thing running it restarts.

  5. The lessons file opens.

    Every mistake becomes a written rule the system checks before it decides. Number one was written that day. There are 39 now.

02 · Luma

The first product.

Late July. Show it to people.

  1. It gets a name. Luma.

    A customer portal, live. Then the founder ran his own blind test.

    What brokeThe blind test quoted $0. Carrier logins had expired overnight.

    What it taughtConnect to every carrier first thing, every morning.

  2. The first private-equity demo.

    It went well.

    What brokePausing jobs for the demo silently skipped that morning’s brief.

    What it taughtPaused means missed. Nothing catches up on its own.

  3. Count what’s real.

    What brokeThe system said our book was 4,629 policies. In force: 294.

    What it taughtCount what is real, not what is recorded.

03 · Doux v1

The first rewrite.

August. Make it a business.

  1. Doux v1.

    A real web app. Our own second agency signs up as customer number one.

  2. We hired our own attackers.

    Before it touched a single mailbox, we paid people to break it. They found 29 ways in. We closed every one.

    What it taughtPassing your own tests is not the same as being safe.

  3. getdoux.com goes live.

    A landing page and a waitlist.

  4. The email that sent itself.

    What brokeA script sent a real email just by being loaded.

    What it taughtNothing runs unless it is told to.

  5. Throw it out.

    About 4,278 files, archived in one afternoon. The order on the folder: do not resume it.

    What it taughtStarting over is a decision, not a failure.

04 · The Console and the Desk

Rewrites two and three.

August into September. One screen.

  1. The Founder Console.

    One screen that stays empty until something needs a human. 115 commits in four days.

  2. The Desk.

    A cockpit for the service team. Then we measured it honestly.

    What brokeThe Run button had run nothing. Four attempts, zero cases.

    What it taughtThe hard part was built. The wiring was missing.

  3. First real quotes.

    The desk runs live quoting for the agency. This is the day the counter starts.

    What brokeThe desk’s tools reached the model on one turn in ten.

    What it taughtBuild the tools into the engine, not beside it.

  4. Watch the meter.

    What brokeA stray key turned a flat subscription into about $40 a day.

    What it taughtCheck who is paying before anything runs.

  5. New machine. Retire both.

    The Console and the Desk, retired the same day. Everything we learned, kept.

05 · Luma desks

Rewrite four. The cloud.

September to now. Off the laptop.

  1. The laptop hands off.

    Intake moves to its own servers in the cloud. Nobody has to leave a computer on.

  2. First live case, end to end.

    The old new-business machine archived.

    What brokeIt left 391 launch tests nobody had marked.

    What it taughtDone is a check you run, not a feeling.

  3. The first HALO.

    When the system is not sure, it asks a person one clear question. It holds instead of guessing.

  4. Our first agency’s mailbox, in the cloud.

    First cycle: 23 of 23 applied. Replayed against a year of past decisions: 86% agreement. Zero wrong archives.

  5. The first UMBRA.

    A question nobody answered escalates on its own. Nothing sits.

  6. Two agencies. One service line. DouxProcess.

    Both agencies run on the same desks. The name grows up.

Today

Four rewrites. 39 written lessons. One rule that never changed.

A person signs off. It was rule one on July 20. It is rule one now.

Database queries…
Workflow actions completed…

Live, from the agency where it was born. Running DouxProcess since Aug 24, 2026.

Doux a demo