Hiring an n8n consultant versus an n8n agency
The two words describe different amounts of the same job. An n8n consultant reviews how your operation runs, decides which processes belong on n8n, and leaves you with a build plan. An n8n agency does that and then ships it, monitors it and hands it over with documentation.
Which one you need comes down to whether you have an engineer who will own the build. If you do, buy the plan and let them execute it. If you do not, the plan on its own will sit in a folder.
We do both and scope them separately. A consulting engagement produces the workflow map, the ranked list of what to automate first, and the architecture decisions: self-hosted or cloud, where custom nodes are needed, how the error handling and alerting should work. That document stands on its own. Plenty of teams take it and build in-house.
What to check before you hire an n8n expert
Ask to see a real workflow, not a screenshot of the canvas. A production n8n build has error branches, retries, alerting and a naming convention. Demo workflows have none of that, and the difference only shows up the first time an API returns a 500 at two in the morning.
Ask who hosts it and who holds the credentials. Self-hosting is one of the main reasons teams choose n8n over Zapier, and it comes with a server, an upgrade path and a backup policy that somebody has to own.
Ask what happens when you want to change something. The workflows should be readable by your own team, broken into sub-workflows with clear names, and documented well enough that the next person can extend them. Anyone who cannot hand the work over is selling you a dependency.