Receipts by WhatsApp, 35 hours back
A construction and real estate company spent on materials, subcontractors, permits, and site costs. Receipts came as photos. Invoices came as PDFs. Staff typed each line into QuickBooks, then typed it again into a budget sheet. Staff now send one photo, PDF, or short message on WhatsApp. The agent reads amount, date, vendor, category, and project. It asks in the same chat when a field is unclear. It checks each entry and blocks duplicates. It writes once to QuickBooks and the budget sheet.
Start with one job only. Fill in the three lines. Keep the bot on that job.
The one job this bot does: ______________________________
What it may do on its own: ______________________________
What it must ask me first: ______________________________
Two lines from this case, side by side. No new figures.
A construction and real estate company spent on materials, subcontractors, permits, and site costs. Receipts came as photos. Invoices came as PDFs. Staff typed each line into QuickBooks, then typed it again into a budget sheet. Staff now send one photo, PDF, or short message on WhatsApp. The agent reads amount, date, vendor, category, and project. It asks in the same chat when a field is unclear. It checks each entry and blocks duplicates. It writes once to QuickBooks and the budget sheet.
The builder reports 80% less manual finance work. The team saves more than 35 hours a week. Reconciliation now runs all the time, not at month-end. Budget overruns trigger an email alert when they happen. The company is not named, and no transaction count backs the 35 hours. The source warns that a wrong category corrupts each report built on it, so checks matter more than extraction.
The after line is the source's claim, not our measurement.
smalloffice.space · Get a case like this in your inbox each morning. Subscribe free
Read this case on your phone now, and keep it for later. Type your email. We send this case to that address, and you get the next cases each morning too.