Skip to content

How to choose automation software without buying the wrong tool first

A platform can be useful only after the business process, source record and ownership are clear. This is a vendor-neutral decision guide, not a list of products Durward sells or endorses.

Start with the job to be done

A feature comparison is useful only when the team knows which process it is trying to improve.

  1. 01

    State the outcome in operational terms

    Define the work that should happen more reliably, such as assigning an enquiry, recovering an unanswered quote or preparing a review pack.

  2. 02

    Capture the current workaround

    Note the spreadsheet, shared inbox, manual copy-and-paste or informal hand-off people rely on now. It often reveals the real requirement.

  3. 03

    Identify the decision that stays human

    Keep the commercial, customer, professional or sensitive action with the accountable person. The tool should support that route, not hide responsibility.

Compare implementation routes before product names

The question is often whether the current system can do enough, rather than which new platform has the longest feature list.

  1. 01

    Native capability

    Check whether the system already in use can create the reminder, field, status change or report needed for the first route.

  2. 02

    Connected workflow

    Use a controlled connection when two approved systems need to pass a known record, task or status between them.

  3. 03

    Limited build or AI-assisted step

    Consider a small purpose-built route or AI-assisted preparation only when the data, review standard and exception path are clear.

Assess the operational fit

A useful tool decision checks whether the software can be run, reviewed and changed by the people who own the work.

  1. 01

    Verify data and access

    Confirm the source record, available fields and authorised access needed for the first test. Do not begin with a broad data import.

  2. 02

    Test the exception route

    Ask what happens when a record is missing, a customer reply is unclear or a rule does not fit. A usable route has a named recovery path.

  3. 03

    Keep the first commitment reversible

    Start with a bounded scope, acceptance checks and a clear owner. A larger platform commitment can follow when the operating route is proven.

Use one transparent decision framework

A useful comparison checks operational fit, not only feature coverage. These are the questions to answer for each route before a product is selected.

  1. 01

    Integration and source record

    Can the route use the authoritative record through an approved connection, and is the trigger clear enough to avoid duplicate or incomplete work?

  2. 02

    Data and access

    Which fields, permissions and retention choices are necessary for the defined workflow? Broad access is not a substitute for a specific design.

  3. 03

    Approval and audit trail

    Which decisions remain with a person, where is an exception held, and what record shows what happened when the normal route did not fit?

  4. 04

    Reliability and change control

    Who can see a failure, pause the route, test a change and decide whether the workflow should be extended or stopped?

  5. 05

    Cost, ownership and exit

    Record the implementation effort, ongoing ownership, licence or usage costs and the practical route for exporting or replacing the workflow later.

Fill in a decision worksheet

The downloadable worksheet puts the routes side by side, so the choice rests on written answers rather than on a demonstration.

  1. 01

    Compare native, configure, integrate and build in one table

    Each row is a question with a column for each route. Fill in the native column first. A route that cannot be described in the same terms as the others has not been compared yet.

  2. 02

    Write down the access and maintenance each route needs

    Record the accounts, permissions and administrator login, and who changes the route when a rule or a connected system changes. Choose the narrowest access that lets the first test run.

  3. 03

    Find the unit the supplier counts

    Suppliers meter use in different units. Zapier's help centre describes tasks, and Make's describes operations and credits. Find the unit in the supplier's own current documentation and estimate how many your first route would use before you compare plans.

  4. 04

    Add your own time and the exception load

    Include set-up effort, review time and the time spent on cases the route cannot finish. These costs sit in someone's day rather than on an invoice.

  5. 05

    Read the terms on who may build

    Terms can limit who may create or change a workflow. The licence FAQ for self-hosted n8n, for example, separates use inside your own organisation from letting outside people build or configure workflows. Read the terms that apply to how you will use the product.

  6. 06

    Write the exit before you commit

    Record what you would keep, how your data and the workflow definition can be exported, and what notice or minimum term applies.

  7. 07

    Date every source

    Supplier documentation changes. Put the page address and the date you read it beside each answer, and read it again before you commit.

Turn the comparison into a decision

A buyer should leave the assessment knowing what to configure, connect, build or leave alone for now.

  1. 01

    Write the recommendation in process language

    Record the process, chosen route, source system, owner and constraints. This makes the decision useful without relying on a vendor pitch.

  2. 02

    Define the first test

    Agree the cases, duration or batch for the first route and the evidence that will confirm whether it is completing and routing work properly.

  3. 03

    Set the review point

    Decide who reads the outcomes and exception pattern, then whether to improve, extend or stop the route.

Questions to answer before choosing automation software

A technology shortlist should follow these operational answers, not replace them.

  1. 1.Which process outcome needs to improve first?
  2. 2.Which system currently holds the authoritative record?
  3. 3.Which step is repeated and which decision remains with a person?
  4. 4.Which data and access are necessary for a narrow test?
  5. 5.How will an exception be seen, paused and resolved?
  6. 6.What would show that the first route is useful enough to keep?

Download the software decision worksheet (CSV) A plain spreadsheet file with a row for each question and a column for each route. Edit it freely; it opens in any spreadsheet program.

Discuss one software decision in the context of the work

Bring the process, the current systems and the practical problem. We can help clarify the smallest viable implementation route.