Case study · automated document distribution
400 Envelopes Every Week → One 30-Second Script.
The situation
A utility in Louisiana. Four hundred employees, paid weekly, and every week the payroll staff spent two full days on paper: printing the pay documents, validating each one, stuffing 400 envelopes, sealing, stamping, and then chasing people down to hand them their stubs in person.
Two days. Every week. Skilled payroll people doing printer-and-envelope work. And when somebody was on vacation or out in the field, the chase could drag on for days after.
The build
A Python script now runs the whole thing. It pulls the approved hours straight out of the utility's ERP, generates an encrypted PDF for each employee, and delivers it to the email address already on file in their CRM. No new logins for anyone to forget. No new system for anyone to learn.
Thirty seconds, start to finish. Zero paper, zero envelopes, zero chasing.
The verified results
$8,500/yr in stamps saved
stamps saved (client-reported, year one).
| Result | Basis |
|---|---|
| $8,500/yr in stamps alone | Client-reported, year one: the actual stamp spend that stopped. |
| 832 staff hours/yr returned | 2 days/wk × 8 hrs × 52 weeks = 832. Shown, not asserted. |
Envelopes, paper, and toner add more; I'm not headlining a number the client didn't report.
Verified client results. Individual results vary; the inputs above are shown so you can judge for yourself.
The pattern
Any document you physically mail on a schedule (pay statements, invoices, compliance notices) is a script waiting to be written.
What are you still stuffing?
Email me the document run that eats your week. A human (me) reads it and answers within the hour, usually minutes.