One of the most common questions we get is, “Can you help us with Xero, WorkflowMax, Unleashed, automation, training, or bookkeeping?”
The answer is always yes — but first we take a step back.
Because at the core of everything we do is the simple principle that we need to understand your process before suggesting change.
It Starts With “What Actually Happens?”
Before recommending software, training, automation, or an AI-assisted tool, we need to understand how work really flows through your business.
That means starting at the very beginning, from the moment a customer places an order or a lead requests a quote, and then following what happens next.
We look at who is involved, what systems are used, where information goes, and how decisions are made along the way — whether that is in Xero, WorkflowMax, Unleashed, Microsoft 365, or a mix of spreadsheets, inboxes, and manual workarounds. Sometimes this process is clearly understood across the team, but just as often it lives in people’s heads or differs slightly depending on who is doing the work.
In practical terms, this is a business process analysis: we are looking at the sequence of activities, handovers, decisions, systems, data inputs, outputs, and exceptions that sit behind a piece of work. A good process review is not just about asking whether people are busy or whether the software is working. It is about understanding the full workflow, where value is created, where time is lost, where risk is introduced, and where the process depends too heavily on one person’s memory or workaround.
We also look at whether the process is repeatable and scalable. A process may work perfectly well when a business is small, or when one experienced person is managing it, but that does not always mean it will work as volume increases, staff change, or the business adds new services, locations, or systems.
What We Typically Find
While every business is different, there are some very consistent patterns we see.
Manual Processes That No Longer Need to Be Manual
Often, processes are being done manually where they don’t need to be. A common example is printing invoices or keeping manual records simply for peace of mind. In reality, systems like Xero already provide the visibility and control needed, but there can be a lack of awareness around what’s possible or where to find information.
From a process perspective, manual work is not automatically wrong. Sometimes it is appropriate because judgement is required, the volume is low, or the cost of automation would outweigh the benefit. The problem arises when manual steps are being used to compensate for missing knowledge, poor system setup, lack of trust in the data, or habits that were formed before the software had better functionality. In those situations, manual work can create unnecessary handling, increase the chance of error, and make it harder to see what is happening across the business in real time.
For example, a business may still print supplier invoices or manually tick off payment records because that process has always felt safer. In practice, Xero may already provide audit history, attachments, approvals, reporting, and searchability, giving the team stronger visibility without the extra paper-based step.
Individual Workarounds and Siloed Information
Just as often, individuals create their own ways of working to avoid missing something. This usually comes from a good place, but over time it leads to people working in silos. Consultants might maintain their own quoting spreadsheets, team members track tasks differently, and the same information exists in multiple places in slightly different forms. This creates duplication, inconsistency, and a lack of shared visibility.
Technically, this is often a control and visibility issue. The business may not have a single source of truth, so each person creates their own control point. One person trusts their spreadsheet, another trusts their inbox, another relies on notes, and another tracks tasks in a separate app. Each workaround may make sense individually, but collectively they create fragmented data, duplicated effort, and competing versions of the same information.
A process review looks for those informal control points and asks why they exist. Are people creating extra records because they do not trust the system? Because they cannot find information quickly? Because approvals are unclear? Or because reporting has not been set up in a way that gives the team confidence?
For example, consultants may keep separate quote spreadsheets because their WorkflowMax job management process does not clearly show quote status, follow-up dates, margins, or responsibility. The spreadsheet helps each person feel in control, but it also means management cannot easily see the full pipeline or rely on one shared version of the truth.
Unnecessary Complexity Across Systems
We also regularly see unnecessary complexity across systems. This can show up as manually entering the same data into multiple platforms, using several apps that overlap in functionality, or not fully using tools that are already in place, such as Xero, WorkflowMax, Unleashed, or Microsoft 365. More recently, we are seeing the same pattern with AI: people dipping into different AI tools to solve immediate problems, but without a clear strategy for how those tools fit into the wider business process, data, security, or team workflow. In many cases, the issue isn’t a lack of software — it’s that the existing tools aren’t being used to their full potential, and new tools are being added before the current process is properly understood.
This is where it helps to separate the process from the technology. The software stack should support the workflow, not become the workflow. When systems are added one at a time to solve immediate problems, the business can end up with overlapping tools, duplicated data entry, unclear ownership, and weak integration between platforms. The result is often more administration, not less.
A more technical review looks at where data is first captured, whether it is captured once or repeatedly, how it moves between systems, who validates it, and where the authoritative record lives. It also considers permissions, security, version control, reporting needs, and whether the current toolset can support the process before introducing anything new.
Sometimes the right answer is not another off-the-shelf app. It may be a small AI-assisted tool or workflow designed to fill a specific gap between systems, provided the problem is clearly defined and the process has been properly understood first.
For example, a customer order might begin in an email, then be copied into a spreadsheet, entered again into accounting software, and finally updated in Unleashed Inventory. A better-designed workflow would capture the information once, validate it at the right point, and allow it to move through the process more reliably.
Reference: Netskope’s Cloud and Threat Report: Shadow AI and Agentic AI 2025 notes that generative AI adoption is increasing quickly, but that unmanaged or unsanctioned AI use can create data, security, and governance risks when organisations do not have visibility over the tools being used.
Missed Updates and Better Ways of Working
Another pattern is that people become used to using software in a particular way and simply keep working like that. Over time, the software itself often changes — with new features, shortcuts, integrations, and better ways of doing things — but those updates can go unnoticed. As a result, businesses may continue using manual workarounds or outdated habits within software they are already paying for, without realising there is an easier or more efficient option available.
This is especially common with cloud software because the product is constantly evolving. New settings, integrations, automations, reporting options, approval features, and collaboration tools are released without the business revisiting its original way of working. The process then becomes a mixture of old habits and new software, rather than a deliberate design.
A process review helps identify whether the business is using current functionality effectively. This is not about chasing every new feature. It is about checking whether there are now safer, faster, or more consistent ways to complete work that was previously manual, duplicated, or dependent on one person’s knowledge.
For example, a business may continue emailing documents around for review, creating multiple versions and long email trails, when Microsoft 365 already supports shared files, version history, permissions, comments, and collaborative editing. The better process may simply be to use the tools already available in a more deliberate way.
Once We Understand the Process — Then We Can Improve It
Only after we’ve properly mapped and understood how things currently work do we move into improvement.
Improvement usually starts by deciding what type of change is needed. Some processes only need small refinements, such as removing duplicated steps or clarifying who is responsible. Others need standardisation, where everyone agrees to use the same workflow, naming conventions, records, and controls. In some cases, the process needs redesign, where the current approach is no longer suitable for the way the business now operates.
The aim is not to make the process more complicated. In fact, good improvement work usually simplifies the workflow by removing unnecessary steps, reducing rework, improving data quality, and making responsibilities clearer. Only after that should automation be considered, because automating a poor process usually just makes the poor process happen faster.
For example, before setting up transaction processing automation for invoice capture or approval routing, it may be better to review the accounts payable process first. If supplier coding is inconsistent, approval rules are unclear, or invoices are being checked twice by different people, automation could simply speed up the confusion rather than solve it.
Find the Champion
For any change to work, there needs to be someone internal responsible and motivated for driving it forward. This person needs both authority and context. They need to understand how the business operates and be able to make decisions that stick.
Without a clear champion, even the best ideas can lose momentum or get stuck in discussion.
The champion also becomes the link between the technical solution and the real business context. They help confirm whether the proposed workflow will actually work day to day, whether exceptions have been considered, and whether the team understands why the change matters. This role is important because process improvement cannot sit only with an external advisor or software provider; it needs internal ownership.
For example, a finance manager or operations lead may be the right champion because they can make practical decisions about coding rules, approval thresholds, system permissions, and team responsibilities. They also understand how those decisions affect day-to-day work, not just the software setup.
Choosing the Path of Least Resistance
We don’t aim to overhaul everything at once. Instead, we look at the structure of the current process and identify where improvement can move most naturally — with the least disruption and the greatest impact.
This reflects the idea that people and systems tend to follow the path that feels easiest or most familiar. Rather than fighting that tendency, we try to work with it by designing changes that fit naturally into the way the business already operates, while still moving the process in a better direction.
Taking this approach makes change more manageable and increases the likelihood that it will actually be adopted.
In practical terms, this means looking for the change that gives the business a meaningful improvement without creating unnecessary friction. Sometimes that is a system setting. Sometimes it is a new naming convention, a clearer handover point, a shared dashboard, or a small change to when information is captured. The best first improvement is often the one that reduces effort for the team while also improving accuracy, visibility, or control.
For example, rather than asking the team to adopt a completely new follow-up system, the first improvement might be to replace a separate spreadsheet with a shared status field or task list inside WorkflowMax or another system they already use every day. This reduces friction while still improving visibility and accountability.
Reference: Robert Fritz, The Path of Least Resistance for Managers, explains that energy moves along the path of least resistance and that the underlying structure of an organisation influences behaviour. His work highlights that lasting change often comes from redesigning the structure so better outcomes become easier to achieve.
Why Change Is Hard (and Completely Normal)
It’s important to acknowledge that resistance to change is completely natural.
People get used to doing things a certain way, and over time they become efficient at it. Even if a new approach is better, it requires more thought and effort, at least in the beginning. That temporary slowdown can feel frustrating and uncomfortable.
This is why change isn’t just about systems. It’s about people, habits, and confidence.
This is why we pay attention to cognitive load. If a new process asks people to remember too many steps, switch between too many systems, or interpret rules differently each time, adoption will be difficult. A good process should make the right action obvious, reduce decision fatigue, and provide enough structure that people do not need to invent their own workaround.
For example, a team may resist a new approval process not because they disagree with the idea, but because the rules are unclear, the approver changes depending on the situation, and no one knows where to check the current status. Simplifying the rules and making the status visible can make adoption much easier.
Reference: Jason A. Hubbart, “Organizational Change: The Challenge of Change Aversion” (2023), discusses how resistance to organisational change is often linked to discomfort with uncertainty, loss of control, and a preference for familiar ways of working.
Designing Change That Actually Works
Successful change needs to be designed with people in mind.
That means understanding what motivates the team, making changes as simple and intuitive as possible, and providing support during the transition. It also means recognising that not everyone will move at the same pace.
In some situations, strong resistance can point to deeper issues that sit outside of systems and processes and move into HR-related challenges.
Good design also includes governance. That means deciding who owns the process, who can change it, how exceptions are handled, what needs to be documented, and how success will be measured.
For example, documenting the agreed month-end process might include cut-off dates, responsibilities, review steps, reporting deadlines, and what happens when information is missing. This gives the team a shared reference point and reduces the risk of the process changing informally over time.
Testing Matters More Than People Expect
One of the biggest risks in any improvement project is implementing something that doesn’t work properly.
That’s why testing is such a key part of the process. Before anything is rolled out more broadly, it needs to be proven in practice. The process needs to work from start to finish, edge cases need to be considered, and the team needs to feel confident using it.
Without that, trust in the change is quickly lost.
Testing should include normal transactions as well as exceptions. It is easy to test a perfect scenario, but real businesses need to know what happens when information is incomplete, a supplier sends the wrong document, a staff member is away, an approval is delayed, or a customer changes their mind. Testing also helps confirm whether reports, audit trails, permissions, and handover points are working as expected.
For example, a new invoice approval workflow could be trialled with a small group before it is rolled out to everyone. The test should include standard invoices, urgent invoices, disputed invoices, and invoices with missing purchase order details, so the business can see how the process works in real conditions.
The Hidden Benefit: New Ideas Emerge
Interestingly, once a process starts to change, something else happens.
People begin to see new possibilities. They ask better questions, spot further opportunities, and start thinking differently about how work could be done.
Often, it’s only when something shifts that these ideas surface. You don’t know what you don’t know until you see a different way of doing things.
A new process doesn’t just solve the original problem — it opens the door to better ways of working overall.
This is one of the reasons process reviews are so valuable. The first conversation may be about bookkeeping, training, Xero, WorkflowMax, Unleashed, or a single system issue, but once the workflow is visible, the business can often see broader opportunities. Better data capture can improve reporting. Clearer handovers can improve customer service. Consistent processes can reduce onboarding time for new staff. Stronger system use can support future transaction processing automation or carefully designed AI-assisted tools more safely.
For example, after improving quote tracking, the business may realise it can also measure conversion rates, identify delays, improve follow-up timing, and forecast workload more accurately. What started as a simple visibility issue can become a much better source of management insight.
Final Thought
Whether we’re supporting bookkeeping, systems, training, Xero, WorkflowMax, Unleashed, transaction processing automation, or an AI-assisted tool to fill a specific gap, the goal is never just to fix a task.
It’s to build processes that are clear, consistent, and work for the whole team — processes that can scale as the business grows and support the right tools in the right places.
And that always starts with understanding how things work today.