Coily launches: certificates of insurance, issued in seconds and verified in every one.

Today we're launching Coily, a verification-first way to issue certificates of insurance. A request arrives in your inbox; a compliant, provable ACORD 25 leaves it in seconds instead of the better part of an hour.

The problem we started with

Certificates of insurance are the most repetitive work on an agency's service desk, and somehow also some of the riskiest. Every job site, every vendor agreement, every lease renewal produces another request. Each one has to be read closely, retyped into a management system, checked against the policy, and sent back, usually while the requester is calling to ask where it is.

The volume makes the work feel mechanical. The stakes make it anything but. A certificate asserts, in writing and under your agency's name, what someone else's insurance policy says. Assert something the policy doesn't back (an additional insured endorsement that isn't on the policy, a limit that changed at renewal) and the certificate becomes evidence in someone's errors-and-omissions file. Fast and correct have always pulled against each other. We built Coily so they stop being a trade-off.

What Coily does

Coily reads the request the way a seasoned account manager would, except it reads all of it, every time.

• It reads the request. The certificate holder, the named insured, each coverage line and limit, every endorsement and provision (additional insured, waiver of subrogation, primary and non-contributory), plus deadlines, pulled straight from the email or document. Nothing gets retyped.
• FormLock verifies every provision. Each requirement is checked against the policy's actual endorsement forms: the forms on file, not a checkbox in a management system. If the policy doesn't back a provision, Coily won't assert it. FormLock fails closed: anything ambiguous or unsupported routes to a licensed professional with the exact question attached.
• It issues a compliant ACORD 25. Verified requests become a finished certificate in seconds, ready to review and send.
• Every certificate ships with a Verification Report. The forms cited, the policy snapshot frozen at issuance, and a tamper-evident ID, so months later, "what did the policy say when you issued this?" is a lookup, not a reconstruction.

Where it works

Coily meets the request where it already lives. The Outlook add-in drafts the certificate right beside the request email; the Gmail add-on does the same in the side panel for agencies on Google Workspace. The dashboard holds your queue, clients, policies, and issued certificates in one place, and an API is available for teams that issue from their own systems.

We kept coming back to one design rule: the fast path and the correct path have to be the same path. If speed ever depends on skipping the check against the policy, the product has failed. Coily is what that rule looks like when you hold it all the way through: the certificate that goes out in seconds is the one that was verified, and the one you can prove. (the Coily team)

Verification is the product

Plenty of tools make certificates faster to produce. That was never the hard part: a certificate is a one-page form. The hard part is that the form is a representation of a live insurance policy, and the policy is the only source of truth that matters. So Coily treats verification as the product, not a feature: every provision on every certificate is checked against the policy's endorsement forms before the certificate exists, on every plan, with no way to switch it off.

That choice has a cost: Coily will decline to assert what it cannot verify, and will hand the edge cases to a human. We think that's exactly the behavior an agency should demand from software that signs its name.

Try it

Coily is available today at trycoily.com. You can paste a real certificate request into the live demo on the homepage and watch it get read, requirement by requirement, before you ever create an account, then set up your desk in about a minute.