What a Power Automate consultant actually does (and when you do not need one)

Most people who search for a Power Automate consultant have a specific irritation in mind: an approval that happens by email and gets lost, a report someone sends every Monday by hand, attachments that need saving to the right folder, data that gets copied between two systems that do not talk to each other. Power Automate is the Microsoft tool for exactly that, and it is included in most Microsoft 365 business licences. So why pay someone?

What the job is

The tool is not hard to open. The work is in three places that are easy to underestimate.

Working out what the process actually is. Before a flow can run a process, someone has to write the process down, including the exceptions. “Approve the invoice” turns out to mean “unless it is over £5,000, or from a new supplier, or arrives on a Friday afternoon when the approver is out”. A consultant’s first job is to ask those questions and get the answers into a shape a flow can follow.

Designing for failure. A flow that works on the happy path is a demo. A flow that hits a missing file, a renamed column or a bad row and tells the right person, instead of silently stopping, is a tool. Error handling and a notification path are the difference, and they take longer to build than the flow itself.

Knowing what the connectors can and cannot do. Excel Online has limits on table size and on what it will do inside a flow. SharePoint lookups behave differently from Dataverse ones. Some actions need a premium licence. Knowing this before you start saves rebuilding halfway through.

What a good flow looks like

A good flow is boring. It fires when it should, does the same thing every time, and tells someone when it cannot.

On a job earlier this year, a mortgage brokerage had one master Excel workbook that needed splitting into 29 private copies, one per adviser, every time it changed. Someone was doing it by hand. The flow I built does it with Power Automate and Office Scripts in Excel Online: the master changes, the copies follow, and each adviser sees only their own. The write-up is in the case studies.

Nothing about it is clever. It is correct, it has a failure path, and it has not needed attention since handover.

Could AI just do this?

It is the other question I now get in the first conversation, and the answer is mostly no, and it should not. An approval chain, a Monday report or a file that needs saving to the right folder is a procedural problem: the same steps, in the same order, every time, with exceptions you can write down. That is exactly what a flow is for. It does the steps the same way at three in the morning as at nine, it runs on the licence you already have for most connectors, and it tells you when it cannot continue.

A language model reasoning its way through each run is the wrong tool for that job. It is slower, it costs money every time it runs, and when it gets something wrong it does not know that it has. For a process that touches invoices or customer data, that is a risk taken on for no gain. Where AI does earn its place is a single step that needs judgement inside an otherwise fixed process: reading a free-text email to decide which queue it belongs in, say. Build the process in Power Automate and put the model in that one step, if there is one.

How engagements tend to run

Most start small: one process that costs someone an hour a day. Once that works there is usually a list, and the list gets worked through on a fixed quote per flow. You should get the flow, the written process it follows, and an explanation you could repeat to a colleague. If a consultant wants to keep you dependent on them for every change, ask why.

For the flows I build, the pricing page sets out the two ways I charge and where scope tends to creep.

When you do not need a consultant

• The template already exists. Power Automate ships with hundreds of templates (“save Outlook attachments to OneDrive”, “post a message to Teams when a form is submitted”). If one matches your process exactly, use it.
• A single-step approval. The built-in Approvals action with one approver and one outcome is a ten-minute job you can do yourself.
• The real problem is the spreadsheet. If the data you want to move is a mess, automating the move spreads the mess faster. Fix the source first. Sometimes that is an Excel job, not a Power Automate one.
• It only happens twice a year. Automation pays back on frequency. If the task takes an hour twice a year, a checklist is cheaper.

Questions to ask whoever you hire

1. What happens when this flow fails, and who finds out?
2. Which of these actions need a premium licence, and have you costed that?
3. Will I be able to read and change this myself afterwards?
4. Can you show me one you built that has been running for more than six months?

If the answers are vague, keep looking. If you would like mine, the Power Automate page describes the work and the contact page is the quickest way to start.