Questions to ask before hiring an automation agency
Use the same questions for every supplier, including us. They cover proof, access, cost, ownership, support and exit, and they apply equally to an agency, a freelancer and a software vendor. Sometimes the right answer is a feature you already pay for.
Define the workflow before you contact anyone
Suppliers can only be compared fairly against the same description of the work. Write it first, in your own words.
- 01
Describe the trigger and the finished state
Say what starts the work, what a good result looks like and who receives it. If two suppliers read the same brief, they should be able to price the same thing.
- 02
Name the person who owns the result
Someone on your side has to accept the work and run it afterwards. If nobody can, the first task is to find that person, not a supplier.
- 03
Write down what is not in scope
List the systems, customer messages and decisions the project will not touch. A supplier who accepts the boundary without comment is worth asking why.
Questions about proof
Proof from similar work is useful. Treat it as evidence to examine, and notice what is missing as well as what is shown.
- 01
Ask what was built, for whom and how it was measured
A description of a real piece of work, with the measure used and who took it, tells you more than a headline figure. Ask what the supplier is not allowed to disclose.
- 02
Ask for a conversation with someone who has used the work
Where a client reference is possible, ask what went wrong and how it was handled. Where it is not, ask for a worked description or a demonstration against your own process.
- 03
Ask how the supplier explains the work to you
You should be able to understand what each part of the workflow does and why it is there. If the explanation stays vague after follow-up questions, the system may be hard for your team to run later.
Check native and off-the-shelf options first
A feature of a system you already use is sometimes the cheapest route. A supplier should be willing to look at that with you before proposing something new.
- 01
Ask which existing feature was considered
The answer should name a specific tool or setting and say why it falls short. "It cannot do this" without a reason is not an answer.
- 02
Ask whether the supplier is tied to one platform
A supplier may be paid by, or trained on, a single product. That is not wrong in itself, but you should know it when you read the recommendation.
- 03
Compare an implementer with a software vendor on the same task
A vendor sells a product, and the set-up may be left to you. An implementer configures and connects the pieces, which is a cost of its own. Decide which of those two jobs you need done.
Access and approvals
A project can only work with the access it is given. Keep that access narrow, and keep control of the accounts.
- 01
Ask for a field-by-field list of the data needed
A narrow first test needs a short list. A request for broad access to everything is a reason to ask what the design is.
- 02
Ask whose name is on each account
Where practical, accounts should be in your company's name, with the supplier given scoped access. Ask for this in writing, before work begins.
- 03
Ask which decisions stay with a person
Approvals, exceptions and anything that affects a customer should have a named human owner. If the workflow handles personal data, ask the supplier to explain what is processed and where, and take legal advice where the answer matters.
Total cost
A quote is one number. The cost of the work includes the charges that continue after it.
- 01
Separate set-up from running costs
Ask for the one-off scope and the recurring costs as separate lines. Licences, usage charges and hosting should each be named, with the provider that bills them.
- 02
Ask who pays each third-party provider
Some suppliers bill their tools through you and some resell them with a margin. Either can be fair, but you should know which, and what happens to the bill if you leave.
- 03
Ask what changes the price
Volume, extra systems and changes to the rules all alter the cost. Ask what a change request looks like and how it is priced before you sign, and compare quotes only where the scope matches.
Acceptance and handover
Agree how the work will be judged before it begins, and agree what you will hold at the end.
- 01
Agree acceptance checks in advance
Write down the cases that must work, the failure route and what you will compare against. This gives both sides a way to say the work is finished, or is not.
- 02
Ask what you receive at handover
Documentation, the configuration, an export of your data and the credentials should be yours. Ask for a list, not a promise.
- 03
Ask who supports it afterwards, and on what terms
Support scope, hours and any response expectations should be written down, together with what costs extra. A change of supplier should not stop the workflow working.
When not to commission a build
In several cases the right advice is to do less, or to wait.
- 01
The process is still changing
Automating a route the team has not settled usually repeats the confusion more quickly. Settle the process first, then decide whether it needs software at all.
- 02
A tool you already pay for covers the need
Switch on the feature, change the setting or train the team. A supplier who tells you this has saved you the cost of a project.
- 03
Nobody can own it afterwards
A workflow with no owner tends to drift out of date. Wait until a person can be named, or choose a simpler design that someone can run.
Eight questions to put to every supplier
Ask them in the same order and write the answers down. The file below holds a fuller list with space for three suppliers.
- 1.Which existing feature or tool could do this, and why is it not enough?
- 2.What similar work can you describe, and what are you not able to show?
- 3.Which data and permissions do you need, and in whose name will each account sit?
- 4.What happens when a step fails, and who is told?
- 5.Which costs are one-off, which recur, and who pays each provider?
- 6.What will be tested before go-live, and against what baseline?
- 7.What do we receive at handover, and who supports it afterwards?
- 8.What happens if we end the contract?
Download the supplier comparison checklist (CSV) A plain spreadsheet file with room for three suppliers. Edit it freely; it opens in any spreadsheet program.
Continue with the decision you need
These pages cover the next level of detail.
Bring your shortlist and your questions
Tell us what you are comparing. We will say plainly if a feature you already have, or another supplier, is the better fit.