A repair workshop handling approximately €1M in annual money movement was operating through multiple Excel sheets, paper job records and processes heavily dependent on individual knowledge. Pricing was manually checked, information was repeatedly entered, and limited structured data made reporting and oversight difficult.
The underlying problem wasn't simply outdated technology. It was fragmentation.
Processes, data and business rules had developed over time but had never been brought together into one consistent operating model. Critical knowledge remained with individual employees, creating unnecessary administration, opportunities for error and operational dependency.
Rather than simply digitising the existing process, the workflow was reviewed and redesigned first.
The solution focused on three principles:
Using the organisation's existing Microsoft 365 environment, a lightweight solution was designed around SharePoint, Power Apps and Power Automate.
Mechanics would use a simple guided workflow to record repairs, while mandatory parts, pricing logic and document generation would be handled automatically. Administration would gain consistent data and invoice-ready outputs without introducing a large new enterprise system.
The redesigned system is intended to:
Reduce manual administration | Improve billing accuracy | Reduce dependency on individual knowledge | Create reliable operational data | Enable future reporting and automation
The initial implementation was designed as a 35–55 hour incremental project, beginning with a small pilot to minimise disruption and adoption risk.
This wasn't really an Excel problem.
It was a process and knowledge problem.
By understanding how the business actually works before choosing the technology, fragmented activity can be turned into a structured, scalable operating system — without automating unnecessary complexity.
Structure first. Automate second. Scale from there.
An eight-location bakery business relied on emails and text messages to manage next-day production orders. Every day, the owner or administrator had to collect submissions, chase missing orders, manually consolidate quantities and send the final production requirements to the bakery team — consuming approximately 1–2 hours every day.
The issue wasn't simply that the process was manual. It had become a business bottleneck.
Different submission formats increased the risk of missed orders and incorrect totals, while the entire process depended on one person's availability. There were also no systematic checks to identify unusual quantities before they reached production.
Rather than adding more administration, the workflow was treated as a process design problem.
The redesigned model focused on:
The objective was not to remove people from the process, but to use human judgement where it adds value.
A lightweight automation was designed using the organisation's existing Google Workspace environment.
Branches submit structured orders through a standard Google Sheet or Form. Google Apps Script consolidates the data, identifies missing submissions, applies validation rules and produces a single production summary. Management retains a short final review before production is confirmed.
The redesigned process reduces approximately 1–2 hours of daily administration to a short approval step, while improving accuracy, control and operational resilience.
5–10 hours saved per week | Fewer manual errors | Automated anomaly detection | Reduced key-person dependency | Scalable from 8 to 20+ locations
This wasn't really an ordering problem.
It was a scalability problem hidden inside a daily task.
The solution wasn't more people or more technology. It was redesigning the process so technology handles repetitive work, while people retain control where judgement matters.
Less friction. Better control. Built to scale.