Work

Real systems, built around real operations.

A business system for a local studio, two service brands launched online, and five systems built inside a heavy-civil contractor’s equipment operation. Each one started with how the work actually runs.

Field notes

Five systems inside a working equipment operation.

Built by RootN’s founder as an engineer inside a Western Canadian heavy-civil contractor’s equipment operation. Measured where the work happens.

01 Admin & workflow automation From paper timesheets to a digital workflow handling about 90 a day Paper timesheets were collected, checked, copied and filed by hand. A digital form, a Power Automate flow and a PDF template replaced the handling. 60,000+ timesheets processed, over more than two years~90 timesheets a day 02 Equipment lifecycle cost Quarterly lifecycle-cost analysis, from 2–3 weeks to about 6 hours Lifecycle-cost models for each equipment model were built by hand every quarter. A Python engine now applies the same logic to every model and produces the outputs for review. 8 h → ~20 min per equipment model2–3 wk → ~6 h for the full quarterly analysis 03 CMMS, ERP & field data Weekly meter-hour updates from 4 hours to 20 minutes Several weekly fleet tasks had predictable inputs but were done by hand. Power Automate flows (cloud and desktop) now do the work. 4 h → 20 min weekly meter-hour update≈190 h of admin time a year back (3 h 40 min × 52 weeks) 04 Admin & document automation Payroll sorting from 2 hours to about 5 minutes, every two days Payroll files, department documents and contractor confirmations were all handled by hand. Three Python tools now do it. 2 h → ~5 min payroll file sorting, every two days≈96% less time on that task 05 Equipment cost visibility Maintenance labour cost by machine and component, from timesheets you already have Labour was tracked as a department total. A Python tool now maps every timesheet entry to a machine and a component category. Per machine labour cost visibilityPer component cost breakdown by category

A note on where the field notes come from

Each system was designed and built by RootN’s founder as an engineer inside a Western Canadian heavy-civil contractor’s equipment operation. They are not RootN client engagements, and we don’t present them as such. The employer and the names of its systems are left out. The figures are the founder’s, from inside the operation, and we’re happy to walk through how each one was measured.

Next step

Recognize your business in one of these?

A familiar bottleneck is a good place to start. Tell us what your team would like to stop doing by hand.

Request a 30-minute call

With the engineer who would do the work. Reply within one business day.

contact@rootn.ca · +1 (825) 436-3300