Most guides to this question are written by one of the candidates. This one is too. I have put myself third, and I have written down the cases where you should hire someone else instead.
§1 Start with the honest question
The useful question is which of these five situations is yours.
If you know the process, you need a builder, and you should pay builder rates. If you do not, a builder will build whatever you point at, and you will find out in three months that you pointed at the wrong thing. That second case is a different purchase, and it costs more.
§2 The five kinds of provider
Deloitte, Accenture, and the rest. They are the right answer when the change crosses several departments, when a board needs to sign off, and when the risk of getting it wrong is measured in millions.
They are the wrong answer for a twenty-person company with a broken invoice process. You will pay for a team, a methodology, and a deck. The deck will be correct. It will also cost more than the problem.
Firms such as Itinera take the operations seat at companies of ten to a hundred people, connect the systems that do not talk to each other, and write the processes down. Their own promise is that you own everything they build.
Hire this kind of provider when the problem is the whole operation rather than one workflow. You want someone in the business often enough to see how it really runs.
The limit is the same as the strength. A fractional COO is a part-time executive, not a specialist in any one tool. If your problem turns out to need deep integration work, they will bring in someone like the next two categories anyway.
This is where I sit, so read the next paragraph knowing that.
The shape is one person who does the analysis and the build. You get a business analyst who maps the current-state process, decides which steps should stay human, and then implements what is left. The advantage is that the person who wrote the diagnosis has to live with it, which is a strong incentive to be honest in the diagnosis.
The limit is capacity. One person cannot staff a project with a deadline that needs four people. If you need parallel workstreams, you need category 1 or 2.
Agencies built around one platform, usually n8n, Make, or Zapier. They are fast, they have seen your problem before, and they have a bench, so they survive one person getting sick.
Hire them when you know what you want built and you want it built properly. The tradeoff is that a shop built around a tool tends to find problems that the tool solves. Specialists in any trade do this.
Upwork, Fiverr, and similar. Cheap, fast, and genuinely right for a contained job: fix this workflow, connect these two systems, build this one thing.
Here is a number I measured rather than guessed. On 11 September 2026 I opened three n8n job posts on Upwork that advertised rates between thirty-five and sixty-five dollars an hour, or fixed budgets of one to two hundred dollars. Upwork publishes what each client has actually paid across their hiring history. Those three clients had paid an average of $6.65, $6.83 and $8.90 an hour. Two of them had posted over seven hundred jobs each and spent under twenty thousand dollars in total.
Read that as a warning in both directions. As a buyer you can get work done cheaply there. You should also expect that the people bidding at those rates are carrying a lot of jobs at once, and that your project gets the attention the price pays for.
§3 Three questions that sort the categories
Do you know which process to automate? No means you are buying an assessment, not a build. Categories 2 and 3.
Does the work cross departments? Yes, with a budget holder in each, means category 1, however much you dislike the price.
Can you describe the finished thing in one sentence? Yes means category 4 or 5, and you should not pay for discovery you do not need.
§4 What to ask whoever you shortlist
That third question is worth dwelling on. Automation fails quietly. A workflow that stops firing does not send you an alert saying it stopped firing, and the people who depended on it work around the gap for a week before anyone reports it.
I can answer it with two mornings from one project. A client in Austin, Texas ran into an error at half past midnight my time; I saw the message when I woke at half past five, read the execution log, found that the model had returned text outside the required format, and changed the prompt to force the format. The following day she wrote at four in the morning to say a post had not gone out. I answered at five, found a second cause, and fixed that too. She apologised for waking me. She had not: my phone is silent at night, and I happened to be awake.
I also had her publishing credentials and a working pipeline that morning, and I did not run it. The posts would have gone out under her name without her having seen them. What I wrote to her instead was that I had left it built but not executed, because I did not want to put her articles up.
§5 When not to hire anyone
§6 Where I fit
Nineteen years of enterprise business analysis at KPMG, E.SUN Bank, and Mercedes-Benz Mobility, now applied to AI automation. CBAP and PMP certified. I map the current-state process, decide what should stay human, then build the rest with n8n and Claude, in your accounts, with the documentation to maintain it.
I take on clients in the United States, Canada, the United Kingdom, and Taiwan, and work remotely. For a small US company, here is how that works in practice.
I am the wrong choice if you need four people on it by Friday, if the work is mostly front-end product build, or if you have already decided what to build and want it done at marketplace rates. Categories 1, 4 and 5 above are better answers to those.
If you are not sure which category you are in, that is what the first call is for, and I do not charge for it.
Related: what a document project looks like when the answer is to build.