When choosing an automation company, request a defined scope of work you can check, written responsibilities and a clear handover. Before signing, ask for terms covering accounts, code usage, upkeep and transfer to another supplier. At handover, ask the supplier to explain how to keep operating the workflow using the documentation and files you receive.
Last checked: Updated:
How do I compare suppliers before signing?
Before comparing prices, compare written responsibilities and deliverables. Ask each supplier to explain your process plainly, including what they would leave manual for now. Compare offers covering the same work.
Separate the supplier decision from the tool decision. If the supplier hosts the workflow, ask which server it runs on and which licence applies to the tool.
If the supplier proposes building your automation with a tool called n8n, ask them to show how the tool works and read the tool's licence [1].
You may use or modify the software only for your own internal business purposes or for non-commercial or personal use [1].
Ask the supplier whether the licence suits your planned business use.
If you have a lawyer, ask them who owns the code and documents and what you may do with them. Request terms specifying what you receive, who controls accounts and how to transfer to another supplier.
How do I check that work can continue after handover?
To test the handover, select a workflow and ask the supplier how another professional would find and handle a fault.
Illustrative example, not a customer result: offer A lists the build; offer B also describes accounts, workflow files, operating instructions, recurring costs and handover. Ask for missing details before deciding, and for a live demonstration of the system.
You are defining a test before signing. For customer-facing systems, add a test script in Hebrew.
What answers should be in writing?
Ask for written answers to these questions:
- What outcome is required, and how will you check it was achieved?
- What may you do with code and documents, and what files are delivered?
- Who controls accounts, access keys and backups?
- What personal information enters the system, and who may access it?
- Who receives an alert when something fails, and which actions wait for a person's approval?
- Who maintains the system, what response time is agreed, and what costs extra?
- How do you stop working with the supplier and transfer operations to the next one?
Agree who monitors security advisories and installs fixes.
If the supplier proposes n8n, ask them to show that they monitor the tool's official security advisories on GitHub [2].
Ask how the supplier will handle a broken connection and confirm installation of an update. Agree the required response time in writing.
Questions about choosing an automation supplier
What should the agreement clarify about code ownership?
To establish ownership, have a lawyer review the agreement. Its terms should specify who owns the code, what usage licences apply and what is delivered at the end.
How do I check the supplier really built something that works?
Ask to see a system working for a customer and speak with a previous customer of the supplier. Ask about what happened after launch, not just the demonstration.
What should I ask about the price?
Ask what costs extra when the process changes, a system is added or support is needed. Request operating costs separately from the build cost.
Sources
- n8n Sustainable Use License, accessed 25.10.2026.
- Official n8n security advisories, accessed 25.10.2026.