01
One door for every request
Requesters start in one guided intake instead of a thread that dies in someone’s inbox. Finance, ops, and legal see the same starting record.
Why Coil
Software and services still start in email. Coil runs intake, approvals, and e-sign, then leaves the signed contract beside the draft.
Why Coil
Intake, the right approvals, e-sign, and the signed contract on one record.
01
Requesters start in one guided intake instead of a thread that dies in someone’s inbox. Finance, ops, and legal see the same starting record.
02
Routing follows your lanes: who must see spend, terms, and risk before anything moves. Approvals stay attached to the request, not buried in a CC chain.
03
When the path is ready, Coil prepares what signers need and runs e-sign. The signed contract lands next to the draft so the team keeps one trail.
04
Status updates show up where your team already works (Google Workspace). People know what is waiting without hunting a side portal.
05
Every step — intake, approval, signature — stays on one record. Month-end and vendor questions have a clear history.
For small teams
You do not need a procurement department to buy cleanly. Coil is built for lean US firms still purchasing indirect software and services on email.
One finished path replaces tribal knowledge, shared drives, and “who approved this?” ping-pong — with a clear review when judgment matters.
For cross-functional teams
Finance wants control. Ops wants speed. Legal wants the right terms signed.
Coil gives all three the same finished path: shared intake, clear approval lanes, e-sign, and the signed contract in one place. Process comes before AI. The system holds the path; people still make the calls that need a human.
Chat in. Ink out.
Talk to the team behind Coil.
Two ways to connect
Explore fit
See whether Coil is a fit.
Join early