Direct answer
The best question to ask an automation consultant is who will own the workflows long after handover. Everything else follows from it: where they run, whose accounts they use, who is alerted when they break, and whether someone else could maintain them. A consultant who answers concretely and in writing is showing you how the work will be run.
The questions below are grouped by topic. For each one, the reason is given and a good answer described. They apply to any consultant, agency or freelancer, and to LATYNEX as well. For the choice of kind of vendor, see AI automation agency vs freelancer.
Scope
Ask: what exactly will be automated, and what will not? Why it matters: 'automate our operations' is not a scope. A good answer names a specific process, its trigger, the systems involved and the outputs, and lists what is excluded. Follow up with: what assumptions does the plan depend on, and what would change it?
A good consultant will also ask whether the process is decided before automating it. Automating a process nobody agrees on just makes the disagreement faster.
Hosting and accounts
Ask: where will the automations run, and in whose account? Why it matters: if they run inside the consultant's own tool account, you depend on that account existing. A good answer is that workflows run in an environment created in your name, or are handed over to one, with you holding the administrator login.
Ask what happens to the workflows if you stop working together. The answer should be 'they keep running in your account'. For a comparison of approaches, see custom automation vs Zapier.
Credentials and access
Ask: what access do you need, how is it granted, and how will it be removed? Why it matters: automations touch your CRM, mailboxes, files and finance tools. A good answer asks for the minimum access needed, prefers dedicated service accounts over personal logins, keeps secrets in a proper store rather than in messages or documents, and describes revoking access at the end.
- Do you use a separate account for the integration, or my login?
- Where are the secrets stored and who can read them?
- How will access be removed when the project ends?
- Which systems will you never need access to?
Error handling
Ask: what happens when a step fails, a record is malformed or a connected system is down? Why it matters: anyone can build the path where everything works. A good answer describes retries, what is logged, who is notified and how, how duplicates are avoided when something is re-run, and how a person takes over an item the automation cannot finish.
If the answer is 'it rarely fails', ask again. Reliable automation is designed around failure, not around its absence.
Documentation
Ask: what will I receive that lets someone else understand and change this? Why it matters: an undocumented workflow is a dependency on one person. A good answer includes a description of each workflow in plain language, a list of systems and accounts used, how to read the logs, and a handover walkthrough. Ask to see an example of documentation from a past project with confidential details removed.
Costs
Ask: what will I pay for besides your work? Why it matters: the tools, hosting and usage charges of connected services are separate costs you will carry. A good answer lists the running costs by name, says who pays them and whose account they are on, and says what is included in the build price. See workflow automation cost for what drives cost in general.
On the consultant's own pricing, look for one scope and one price agreed in writing before work starts. LATYNEX works this way and charges no discovery fee, and it is a reasonable expectation of any vendor.
Exit
Ask: if I want to stop, or move to someone else, what happens? Why it matters: your leverage is the ability to leave. A good answer says you keep the workflows, the accounts and the documentation, that the consultant will help hand over, and that nothing is locked to their tooling. Confirm this in the written scope and have a lawyer review the contract.
Red flags
Any one of these deserves a follow-up question; several together should slow you down.
- Workflows run in the consultant's own accounts with no plan to move them to yours
- Requests for personal passwords or full administrator access to everything
- No description of what happens when something fails
- Documentation described as 'available on request'
- A price with no written scope behind it
- Reluctance to describe the exit
- Claims that the automation will produce a specific business result, which a workflow cannot guarantee
Next step
Send the same questions to two or three consultants and compare the written answers. To see how LATYNEX would answer them for your process, start with workflow automation and systems integration. We would also say straight away if a simpler tool would do the job.
Questions
What is the single most important question?+
Who owns the workflows, and in whose accounts do they run, after handover. It exposes hosting, access, documentation and exit in one go.
Should I ask for references?+
Yes, and ask them practical questions: did the price match the scope, what happened when something failed, and could someone else maintain it afterwards.
Do I need a consultant at all?+
Not always. Simple, single-tool automations are often something a team can build itself. A consultant earns their place when several systems, exceptions and ownership are involved.
Can I ask these questions in writing?+
Yes, and it is better to. Written answers are easy to compare and to hold the vendor to later.
How many consultants should I compare?+
Two or three against the same written brief is usually enough. More adds noise more than information.