Automated Waste Route Revenue Report
Every Monday, WebRun opens Routeware to read last week's route completion counts, cross-references the billed amounts in QuickBooks for each route, calculates revenue per route and per stop, logs the breakdown to a Google Sheet, and posts the weekly revenue summary to your ops Slack channel.
How can I automatically get a weekly revenue breakdown by waste route?
WebRun opens Routeware every Monday to read last week's route completions, cross-references billed amounts in QuickBooks for each route, and calculates revenue per route and per stop. The full breakdown is logged to Google Sheets and posted to your ops Slack channel so leadership starts the week knowing which routes are performing.
- Leadership gets a revenue-by-route ranking in Slack every Monday
- Route performance trends visible in Google Sheets week over week
- Routes with missing billing flagged before finance closes the period
Built for waste hauling operations managers · waste company leadership · finance teams · recycling service companies
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.routeware.comin a real browser with your saved login - no setup, no API keys. -
1
Routeware - read last week's route completion data
routeware.com
WebRun opens Routeware to read last week's route completion data. - Open Routeware and navigate to the weekly route completion report
- Read the total stops completed, missed, and total stops serviced for each route for the prior week
- Capture the route name, driver, and service area for each route
Done when Last week's completion counts are captured for every active route.
-
2
QuickBooks - pull billed amounts by route
- Open QuickBooks and pull invoices sent and revenue collected for the prior week
- Group billed amounts by route or service area to match the Routeware route names
- Calculate revenue per stop for each route using the billed amount and completed stop count
Done when Revenue and revenue-per-stop figures are calculated for each route.
-
3
Google Sheets - log revenue breakdown for trending
google.com
WebRun opens Google Sheets to log revenue breakdown for trending. - Open the revenue-by-route tracking Google Sheet
- Append this week's route revenue data including route name, stops, revenue, and revenue per stop
- Update any rolling chart or summary ranges to include the new week
Done when This week's revenue-by-route data is logged and the trending sheet is updated.
-
4
Slack - post weekly revenue summary
slack.com
WebRun opens Slack to post weekly revenue summary. - Post the weekly revenue-by-route summary to the ops or leadership Slack channel
- Rank routes by total revenue with the top and bottom performers highlighted
- Link to the Google Sheet for the full breakdown and historical trending
Done when Leadership has this week's revenue-by-route summary and a link to the Sheet in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does this share financial data outside the company?
No. The revenue report is internal only. It posts to your ops Slack channel and logs to a private Google Sheet. No financial data leaves your team.
Can it break down revenue by service type as well as by route?
Yes. If your QuickBooks invoices include a service type or class, WebRun can group revenue by both route and service type in the same report.
What if some routes do not have matching QuickBooks entries yet?
Routes without billing data are flagged in the Slack summary so your finance team knows which route invoices are still pending for the prior week.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.