One of our clients had a COI problem.
Every month, someone on their team had to pull a report of vendors with expired certificates of insurance, then manually email each one requesting updated documents. Copy the email address. Paste the generic request template. Add the property-specific details—owner name, location info, additional insured requirements. Send.
Repeat 25 times.
It wasn't technically difficult work. It was just tedious, predictable, and soul-crushing. The kind of task that makes capable employees dread the end of every month.
The Constraint That Forced Creativity
The obvious solution—automate the email sends from their existing system—wasn't possible. Their legacy CRM had no API. No integration points. No way to trigger automated workflows.
So we built around it.
We set up a lightweight vendor database in Google Sheets to serve as the automation layer. Yes, it requires double-entry when adding new vendors. Not ideal. But it gave us something their locked-down legacy system couldn't: programmable access to the data we needed.
From there, the automation was straightforward. A daily job checks for expired COIs. When it finds one, it pulls the vendor's email, the relevant property details, and the specific insurance requirements for that location. It composes and sends the request automatically.
No more copying and pasting. No more dreading the end of the month.
But We Didn't Stop There
Sending requests is only half the problem. You also have to process the responses.
COI documents come back in all kinds of ways. Sometimes the vendor replies directly. Sometimes their insurance agency sends it from a completely different email address. The attachments are named inconsistently. The formats vary.
We set up a dedicated inbox to receive all COI responses. Every incoming email gets checked: Is this the document we requested? Can we identify which vendor it belongs to?
When the system finds a match, it downloads the attachment, renames it to the company's standard format, and updates the spreadsheet with the new expiration date.
Fully automated. End to end.
The Math That Doesn't Tell the Whole Story
Let's be honest about the ROI.
The employee handling this task made about $80,000 per year. They spent roughly an hour per week on COI requests—maybe $2,000 worth of time annually.
But factor in the double-entry overhead for the new database, and the net savings drop to around $1,000 per year.
By strict ROI calculation, this automation barely breaks even.
So was it worth building?
The Owner's Answer: Absolutely
Here's what the numbers don't capture.
Some tasks drain more than just time. They drain morale. That monthly COI ritual wasn't just an hour of work—it was an hour of work that the employee dreaded. A recurring reminder that their job included boring, repetitive tasks that a computer should handle.
Now? They don't think about COIs at all. The system runs. Requests go out. Documents come back. The spreadsheet stays current.
That hour didn't just get saved. It got redirected. To customer relationships. To problems that actually require human judgment. To work that feels meaningful.
The owner put it simply: "Even if it saved us nothing, it would be worth it just to not have to assign that task anymore."
The Case for "Small" Automations
Not every automation needs to save 500 hours per year to be worthwhile.
If a task is predictable, repetitive, and makes someone's day worse every time they do it—that's a candidate for automation. The ROI isn't always in the hours saved. Sometimes it's in the frustration eliminated, the attention freed up, the small monthly dread that just... disappears.
Those benefits don't show up on a spreadsheet. But they show up in how your team feels about their work.