No regulation behind this one, just unbilled hours
Thirty-five certificates a week and the agency bills for exactly none of them.
A general contractor emails asking for a cert before Monday. Somebody opens the policy file, reads the subcontract requirements, and rebuilds an ACORD 25 by hand. Forty-five minutes. Again tomorrow.
No regulator requires this. That is the honest version. It is a money tool, not a compliance tool.
01 / Watch it work
One request email. Watch the certificate build itself.
This is the kind of email that lands in a commercial lines inbox all day. Tap the button and watch the requirements come off it.
Being straight with youThis runs a scripted pass over one fixed sample so you can see the workflow end to end. It is not calling a live model in your browser, and it has never seen your paperwork. The real thing reads your actual documents. This shows you what it would do with them.
02 / What it would cost
One price. No per-seat math.
- —Reads the request however the contractor wrote it: email, PDF subcontract, or a forwarded thread
- —Pulls additional-insured wording exactly as demanded, including primary and non-contributory
- —Flags a requirement the policy does not actually carry, before the cert goes out
- —Drafts the ACORD; a human still signs it
- —Every certificate searchable by holder, project or job number
- —Catches a renewal that would expire mid-project
- —Nothing to install. It reads the inbox you already have
This page is the prototype. If the workflow above is close to yours, tell me what is wrong with it and I will change it before you pay anything.
Email me what is wrong with it