Free tool

AI Deployment Routes

Assisted work, built tooling, or systematic automation. Most teams reach straight for the last one, which is the one they should reach for last. Route up to five workflows and find out what each one actually needs.

  • Describe up to five workflows
  • Answer the routing questions for each one
  • Your routes, timing, cost and main risks are emailed together

Every AI-suitable workflow belongs on one of three routes. Route A is assisted work, where a person does the task and AI speeds up the thinking and writing, deployable in days to weeks. Route B is built tooling, a small internal tool doing one defined job, deployable in weeks. Route C is systematic automation, where a defined process runs at volume with monitoring and escalation around it, taking months. Route C is where the word agent belongs, and it requires five criteria to be met without exception. Rushi Vyas routes workflows this way inside the AI Process Audit.

The three routes

What each one means before you pick

Route A. Assisted work

A person does the task, the tool speeds up the thinking and the writing. Drafting, summarising, comparing documents, first pass analysis, turning something technical into something readable. Delivered as chat based and role specific assistants, connected to your own documents where useful.

Days to weeks. Low cost.

Main risk is uneven adoption, where two people get excellent results and nobody else changes habits.

Route B. Built tooling

Someone builds a small internal tool or automation that does a defined job. The kind of thing that historically sat in a queue for eight months because it was too small to prioritise and too fiddly to do by hand. Internal applications, data cleanup routines, report generators, and bridges between systems that do not talk to each other.

Weeks. Moderate cost.

Main risk is building something nobody maintains once the person who built it moves on.

Route C. Systematic automation

A defined process runs at volume with limited human involvement, with monitoring and escalation around it. This is where the word agent belongs, and it is the route people reach for first and should reach for last.

Months. Highest cost.

Main risk is quiet failure, where the process looks fine while producing subtly wrong outputs that nobody checks, because the entire point was to stop checking.

Route your workflow

Answer each workflow separately, then receive one combined result

Does this task need human judgement on most occurrences, rather than following the same steps each time?

Where should I send your result?

Complete every routing question first. 0 of 1 workflows ready.

I send you the result and, occasionally, something genuinely useful about AI adoption in Australia. No list swapping, no spam, unsubscribe any time.

Questions

What people ask before they start

Why is Route C last?

Because its failure mode is quiet. The process looks fine while producing subtly wrong outputs nobody checks, since the entire point was to stop checking. It earns its place only when five criteria are all met.

Is Route A worth doing if it is just chat?

It is usually what pays first. In one university finance function, assisted work took approval processing from more than four days to under two, with no agents and no core system changes.

Can one workflow use more than one route?

Often, over time. Most start on Route A, earn a Route B tool once the pattern is proven, and only a few ever justify Route C.