Plain automation
Eight hours a day to three minutes: a daily file review, automated
Several files arrived every morning. Each had to be opened, scanned for accounts not yet in the system, keyed in, and checked against the file. The same hunt, every day.
- By hand
- About 8 hours a day
- Scheduled job
- About 3 minutes a day
Who did it, and how long it took
About 8 hours a day, every working day: roughly 2,000 hours a year on one task.
What we built
A scheduled job that runs before the office opens. It reads each file, compares the records against what is already in the system, loads the new accounts, and sets aside anything that does not fit the rules with a note on why. Plain automation. No AI.
Time to running
The first files were running through the job in the client's operation within the first-deliverable window, with a person reviewing every exception list until the rules had been seen against real data.
Before and after
- By hand
- About 8 hours a day
- Scheduled job
- About 3 minutes a day
About 8 hours a day is roughly 2,000 hours a year. About 3 minutes a day is roughly 13 hours a year, mostly a person reviewing the exceptions.
First-year return
Roughly 2,000 hours a year came back to the team. At the calculator's illustrative fully loaded cost of $45,000 a year for one person, that is about $45,000 of time in the first year, every year the task exists. An illustration of the value of the time, not a cash figure.
What came next
The exception list got shorter as the rules were tuned, and the same shape of job was pointed at the next file that arrived every morning.
The task page has the same example with what shapes the scope: Automate reviewing daily files to find new accounts.
Have a task like this?
A file that arrives every morning, a portal someone checks all day, a report only one person can build. Tell us about it. The evaluation is free, and the quote is fixed.
Free evaluation. Fixed quote before work begins.