Power Automate consultants who know what it can carry, and where it stops.

What is Power Automate good at?

Power Automate is the workflow tool inside Microsoft 365, and it is genuinely good at plumbing: routing approvals, sending notifications, moving files, copying data between Microsoft 365 apps, and triggering one system when something happens in another. If a job can be written as "when this happens, do that", Power Automate can usually run it, and most Microsoft 365 business plans already include the rights to do so with the standard connectors.

In practice that looks like a leave request that routes itself to the right manager, an email attachment that files itself into the correct SharePoint folder, a Microsoft Form that becomes a task the moment someone submits it, or a Teams alert when a large invoice lands in accounts. None of that is artificial intelligence and none of it needs to be. It is rules, rules are cheap to run, and a mid-size office has dozens of jobs that fit them. We build from our base in Ardross, and since a flow runs the same in any state, plenty of this work is done for clients well outside WA.

Where does Power Automate fall short?

Anywhere the work needs reading, writing or judgement. Power Automate follows rules, so it cannot read a messy supplier invoice, decide how firm a quote follow-up should be, or turn a month of job data into commentary a manager would sign. Long processes with many branches get fragile, error handling is easy to skip and painful to retrofit, and premium connectors and desktop automation cost extra on top of your Microsoft 365 plan.

There is also a governance problem nobody warns you about. Flows are easy to make, so people make them. A few years on, a business has dozens or hundreds of flows built under the accounts of staff who have since left, running jobs nobody can list, failing without telling anyone. We see it constantly, and a good share of our Power Automate consulting is not building new flows at all. It is finding, documenting and consolidating the ones already there.

What does Power Automate plus AI look like?

Power Automate does the plumbing and AI does the judgement, with a person approving anything that matters. The flow watches an inbox or a folder, the AI reads the document or drafts the message, and the flow carries the result into the next system. Neither is enough on its own. Together they cover most of the repetitive work in a mid-size office.

Take purchase order chasing. The flow already knows which orders are open and how old they are. What it cannot do is put any judgement into the chase, or tell which overdue order is a genuine problem. Add AI and each chase is drafted from that supplier's history, sent on a sensible schedule, and the flow escalates the exceptions to a person with the paperwork attached. Invoices follow the same pattern: the flow catches the document when it arrives, the AI reads it and matches it to the order, and the entry lands in MYOB or Xero with a person giving final approval. So does monthly reporting, where the flow gathers the numbers on schedule and the AI drafts the pack and the plain-language commentary before the month closes.

That split, plumbing plus judgement plus a person, is the pattern behind Better Looking Shutters, where automating the office work removed about $250k a year of admin cost while revenue doubled. It is the heart of our AI automation work, and the whole subject of our page on automating admin if the office side is where your hours go.

Who looks after the flows once they are live?

Someone has to, and in most businesses nobody does. Flows usually run under the account of whoever built them, keep working until that person leaves or a connector changes, then fail quietly. Every flow we build is documented, has error handling and a failure alert, and belongs to a named owner in your business, not to us.

When we take on a business that already uses Power Automate, we start by listing what is actually running. Then we retire the duplicates and the dead flows, move anything critical off personal accounts, add alerts so failures surface the day they happen, and write the one-page description each flow should have had from the start. Where a flow reaches outside Microsoft 365, into accounting software or an industry system, we treat it as AI integration work: monitored, tested and owned, not wired up and forgotten. If you do not know what you have, that is a normal place to start, and our AI audit maps it in half a day alongside the rest of your operation.

Is Power Automate already included in what we pay Microsoft?

Mostly, yes. The common Microsoft 365 business and enterprise plans include the right to build cloud flows using standard connectors, which covers SharePoint, Outlook, Teams, Excel Online and OneDrive. Premium connectors, connections to on-premises systems and desktop automation are licensed separately, per user per month with pay as you go options.

Our standing rule is to exhaust what you already pay for before buying anything more. A surprising amount of office admin runs on standard connectors alone, and when a job genuinely needs premium licensing we say so in plain words, along with what the alternative would cost you in effort instead. We do not resell Microsoft licences, so nothing pushes us to talk you into a bigger plan. That independence runs across all our Microsoft AI work: we recommend the tool, not the invoice, and sometimes the honest recommendation is a person and a checklist.