Quoting. Doux it.
Applications read once and every market filled from the same answers, quotes back side by side. Commercial quoting automation for independent agencies.
Supplemental. Application. Loss runs. Portal after portal. Keying in the same answers again and again. Days per submission.
The application is read once. Every market filled from the same answers. Quotes back, side by side. You pick.
How it runs.
- Reads the application, supplementals and loss runs.
- Checks appetite before anything is submitted.
- Fills each carrier portal under your agency’s own logins, once you approve the submission.
- Collects the quotes into one comparison.
- Binding waits for you. Always.
What it touches.
Why it matters.
Commercial quoting is double entry. The same answers, keyed into every portal, for every submission. Days of an account manager's time to find out which markets want the risk.
Worse, every re-key is a chance to get an answer wrong. Wrong answers on an application become denied claims.
DouxProcess reads the application once. It checks appetite first, so nothing goes to a market that will not write the class. Then it fills each carrier portal from the same answers and brings the quotes back side by side. You pick. A licensed person binds.
Where it stops.
- Never changes an answer on the application.
- Missing information is asked for. Never assumed.
- Nothing goes to a market outside its appetite.
- Never submits without a person approving the submission.
- Binding is always a licensed person's decision.
Straight answers.
Which carriers and markets does it work with?
Yours. The carriers you are appointed with and the wholesalers you use, through their own portals and submission inboxes.
How does it know a market's appetite?
From each market's appetite guide, written down once: classes, states, limits and loss history. The same things your best account manager keeps in her head.
Which forms does it read?
Commercial applications for every line, carrier supplementals, loss runs and prior declarations.
How fast does a submission go out?
Usually the same day the application is complete. The slow part becomes waiting for underwriters, not typing.
Does it handle E&S submissions?
Yes. Submissions to wholesalers go out the same way, with the same approval step. Surplus lines filings and diligent search stay with your licensed surplus lines broker.
Take the recipe.
The procedures this workflow runs on, written as one file. Load it into Claude, ChatGPT or Gemini and run it on your own submissions today.
Watch it installed: Claude · ChatGPT · Gemini
Downloads open after you sign the kit license: you build it, you run it, you answer for it.
How to load it. Nothing to install.
- Claude: Settings, Capabilities, Skills, Upload skill. Pick the .zip.
- ChatGPT: start a Project or a custom GPT and paste the .md into its instructions.
- Gemini: make a new Gem and paste the .md into its instructions.
- Then use it: paste in the email or attach the PDF. You get a table and drafts back. You approve. You send.
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.
- Open the email.
- Click inside the message. Press Ctrl+A, then Ctrl+C (Cmd on a Mac).
- Paste it in the chat. Attach anything that came with it.
- Save the application and loss runs it carried.
- Search for the prospect and open the record.
- Documents › expiring declarations.
- Download as PDF, with any loss runs filed there.
- Attach them in the same chat.
- One page per market: classes, states, limits, minimum premium.
- Save as one PDF and attach it.
- None yet? Run it anyway. Every market shows “unknown”.
Nothing to connect, no password to share: you copy one thing and download the other. Not in your system? Get it from the carrier's website. Never from memory.
On its own it reads what you paste in and drafts the work. Want it wired into your mailbox, management system and carrier portals? The builder kit teaches your programmer every step: database, passwords, approvals, deployment. Or let DouxProcess run it for you.