How One Accounting Firm Saved 1,000+ Hours a Year Through SOP Automation

Your team spends hours every week on repetitive tasks they could describe in their sleep, yet nothing is written down, and no one has time to fix it. Sound familiar? 

In this episode, Shannon Smit, owner of the award-winning accounting firm Smart Business Solutions, and her son, Ryan Smit, the firm’s dedicated Systems Champion, reveal how they turned documented processes into real SOP automation, saving over 1,000 hours a year. They share why a process-first mindset is the non-negotiable foundation for any AI or RPA project and how appointing a dedicated champion changed everything. 

Whether you run an accounting practice or any service business, this conversation is packed with practical lessons you can act on this week. 

👤 TODAY’S GUESTS, SHANNON & RYAN SMIT

Shannon Smit is the owner of Smart Business Solutions, an award-winning Australian accounting firm with over 20 team members. Shannon has built her practice on a foundation of innovation, operational excellence, and a commitment to staying ahead of industry change. Her son, Ryan Smit, joined the firm as its dedicated Systems and AI Champion. Despite being early in his career, Ryan’s methodical questioning, natural curiosity, and organisational instincts have made him the driving force behind the firm’s systemisation and automation efforts.

Together, Shannon and Ryan prove that the right approach matters more than decades of experience when it comes to building a business that runs without you.

Website: smartbusinesssolutions.com.au

📋 From Documentation to Automation: 8 Lessons from Smart Business Solutions

Based on the interview with Shannon and Ryan Smit, Smart Business Solutions

Shannon and Ryan’s story is a masterclass in what happens when a business commits to a process-first approach. Below are the eight key lessons from their journey, from appointing a Systems Champion to quantifying the return on SOP automation.

The Systems Champion Is a Strategic Hired Role

Most business owners try to drive systemisation themselves or delegate it to an already-overloaded department head. Shannon took a different path by making the Systems Champion a dedicated, strategic position within the firm. Ryan’s sole focus is extracting knowledge from the people who hold it, translating that tribal expertise into clear documentation, and keeping the systemisation project moving forward. The lesson is clear: if you want systems to actually get built, someone’s primary job has to be building them.

Cultivate the ‘What If’ Mindset

A good Systems Champion does more than record what happens on a normal day. Ryan’s strength lies in constantly asking “What if?” and “Why?” during every extraction session. He pressure-tests each process for exceptions, errors, and edge cases that experienced team members may not think to mention. This questioning approach produces SOPs that are robust enough to survive real-world conditions, not just textbook scenarios. It also surfaces hidden inefficiencies that have been accepted as “just the way we do it” for years.

Use the Systems Champion Role as a Business Education

For someone stepping into leadership, or a family member joining the business like Ryan, the Systems Champion role offers an unmatched education. Rather than learning the business solely through financial statements or a single department, the champion gains a deep, operational view of how every function connects. This holistic understanding accelerates the transition from technician to true business leader, making the role a powerful development pathway for your next generation of management.

Process-First Is Non-Negotiable for AI Success

This is the episode’s headline lesson. Smart Business Solutions could not have built their AI-powered file-noting bot without first having a clearly documented process in systemHUB. The sequence matters: document the process, confirm it works with your team, then look for automation opportunities. Businesses that skip straight to AI tools without this foundation end up automating chaos, not creating efficiency. A process-first mindset, supported by a platform designed for documentation, positions you to capitalise on new technology the moment it becomes available.

Quantify the Automation ROI

Numbers make the case. Before automation, Smart Business Solutions staff spent 8 to 10 hours per week on routine file noting across multiple platforms. By converting that documented process into a bot-driven workflow, the firm now saves well over 1,000 hours annually. That freed capacity is not just an efficiency win; it redirects both administrative and high-value financial planning time toward revenue-generating work. When you can show your team (and your accountant) a clear before-and-after, investment in systemisation and automation sells itself.

Lead the Conversation on Team Buy-In

Automation triggers a natural fear in any team: “Is this replacing me?” Shannon and Ryan tackled this head-on by framing AI as the tool that removes the most boring, tedious, and compulsory parts of each role. The goal was never to reduce headcount; it was to create capacity for team members to move into higher-value, more engaging work such as business consulting and advisory services. When leadership communicates this clearly and consistently, resistance drops and curiosity replaces anxiety.

Treat Upskilling as a Mandatory Investment

Shannon views training, including programs like the Systems Champion Academy, as essential rather than optional. The opportunity cost of not investing is steep: you risk losing talented staff to competitors who do embrace new technologies, and you leave high-value team members performing mundane tasks when they could be generating revenue. Ongoing upskilling keeps the team engaged, positions the firm at the forefront of the industry, and future-proofs the business against rapid technological change.

Systemise for Freedom, Resilience, and Value

The ultimate return on systemisation goes beyond the balance sheet. Documented processes ensure the business is not dependent on any single person, eliminating the classic “hit by a bus” risk. They create the operational resilience needed for the owner to take extended leave without the business stalling. And when the time comes to sell, a fully systemised business commands a significantly higher valuation. Think of it as the McDonald’s model: the system runs the business, and the people run the system. That is the freedom SYSTEMology is designed to deliver.

Shannon and Ryan’s story cuts through a common misconception: that automation is a technology project. It is not. It is a documentation project with a technology payoff. Their 1,000-hour saving did not start with a bot; it started with Ryan sitting down, asking “what if this step fails?”, and writing the answer into a system.

If your team is drowning in repetitive work and you have not documented the process behind it, that is your starting line. Pick the one task your team complains about most, record how it is done today, and capture every exception. That single documented process becomes the foundation everything else builds on.

Want to see business systemisation in action? Watch Dave walk through how to document your first business process step by step.