Category: Tech News

Most businesses only know AI as a chatbot. There is a second category, the decision model, built to make structured decisions for software rather than write answers for people, and most people evaluating AI have never heard of it. If you are building an AI agent, that gap matters, because a well-built agent uses both kinds.

Why most people have only seen half the picture

Every AI model most businesses have used, ChatGPT, Claude, Gemini, works the same way: you ask a question and get a written answer back. That is what most people mean by “AI model”, and it is only half of what exists.

An AI agent is a workflow, not a conversation. Most of the decisions inside that workflow were never meant to be read by a person. Is this transaction worth flagging? Which queue does this ticket belong in? Does this application clear the bar? A model built to write paragraphs can answer all three, but it is the wrong tool for the job, slower and more expensive than the decision needs.

Feature	Text model (ChatGPT, Claude, Gemini)	Decision model (Jev)
What it returns	Written text: answers, summaries, code	A typed answer (a choice, a score or true/false) with a probability, plus a confidence level on choices and scores
Who or what reads it	A person	Your software
Best for	Drafting, explaining, conversation, anything a person reads or approves	Classifying, routing, scoring and checking at high volume
Speed	Seconds or longer per response	70 to 500 milliseconds (TypeSafe’s published range for Jev)
Cost	Priced per token on input and output	Jev: $0.042 per million input tokens, output free (TypeSafe’s published pricing)
Main risk	Can state wrong things fluently	Can pick the wrong option, sometimes with high confidence
Human fallback	Usually, for anything that matters	Yes, for low-confidence cases

How a decision model works

A decision model takes two things: a block of information about the situation, and a set of narrow questions about it. It does not write a reply. For each question it returns a structured answer and the probability behind it. Choice and score questions also return a confidence level. Your own software decides what happens next.

The questions come in a few simple types: pick one option from a list, score something against a rubric, or check whether a statement is true. Each question is evaluated separately, so you can ask several at once and combine the answers with ordinary logic. If confidence is high, the workflow acts automatically. If it is low, the case goes to a person.

That last step matters most. The model’s job is not to be right every time. It is to tell your software how sure it is, so the software knows when to ask for help.

A real example of a decision model: Jev

In September 2026, TypeSafe AI released Jev, which it calls the first “System One” model, a nod to the fast, intuitive thinking Daniel Kahneman described. Jev does not generate text. TypeSafe describes it as a function call powered by AI: information goes in, typed decisions come out, in 70 to 500 milliseconds. Input costs $0.042 per million tokens and output is free. TypeSafe describes Jev as being in early access, and independent testers have been running it through providers such as OpenRouter.

Be careful with the headline numbers. TypeSafe claims Jev is 193.6 times faster and 444.6 times cheaper than standard models on its own workflow tests, and the company itself says those figures are on the higher end of real-world gains. Independent testers have since published their own results, and they agree on speed and cost more than on accuracy. In one independent email-classification test, Jev cost 12 to 27 times less than Claude Haiku 4.5. In a legal benchmark run by Vals AI, it finished last of twelve systems on raw accuracy, while tying the best systems on claim verification. The accuracy depends on the task.

Where a decision model fits in an AI agent

In the six-stage build in our guide to building your first AI agent, this sits in the tools stage: what the agent is connected to and able to act through. A well-built agent does not send every decision through one kind of model. A text model handles anything a person needs to read or approve. A decision model handles the high-volume calls that need an answer, not a paragraph.

Two practical points before you build

First, ask small questions. Decision models work best on narrow, gut-check judgements, so split a complex call into several simple questions and combine the answers in your own logic. In the same email test, accuracy jumped when one broad question was split into five narrower ones and the answers were combined by a simple classifier trained on labelled examples. Second, treat the confidence score as something to test. “Cannot hallucinate” means the model cannot return an answer outside the options you defined. It can still choose the wrong option, so thresholds and a human fallback matter, and the scores should be checked against your own data before you trust them.

In one independent evaluation, accuracy barely moved as the confidence threshold rose from 0.5 to 0.95, and only reached 100% at 0.99, where 60.2% of cases still qualified. In that test, a threshold that looked sensible did nothing until it was very high.

Before you automate any decision, record how long it takes and what it costs today, the same baseline-first approach we cover in how to measure AI ROI.

Choosing between competing text models is a separate decision, which we cover in our piece on AI model fatigue.

Where Australian businesses can use a decision model

Four places the same pattern shows up, one for each sector we work in, with the evidence behind each.

Sector	The decision	Example question	Why it is worth a look
Retail	Return, or return fraud	“Given item condition, return history and time since purchase, does this look genuine or need review?”	A Griffith University-led survey of 5,900 online shoppers in Australia, the US, the UK and Canada found 17% admitted to return misconduct in the past year. The report recommends risk scoring to send high-risk returns to a second person for review.
Fintech	Flag a transaction	“Given amount, location and account history, is this likely fraudulent?”	Australians reported more than $2 billion in scam losses in 2025, according to the National Anti-Scam Centre’s Targeting Scams report. Spotting a suspect transaction quickly is the kind of narrow, high-volume call a decision model is built for.
Real estate	Triage a maintenance request	“Given the description and property type, is this urgent or routine?”	Almost 70% of Australian property service businesses use AI, ahead of finance and insurance (64%) and business services (61%), according to NAB’s 2026 SME survey.
Professional services	Review, or proceed	“Given this contract’s terms and our standard playbook, does this need partner review, or can it proceed as is?”	Business services is one of the most AI-active sectors in Australia, at 61% of SMEs (NAB, 2026). Contract and proposal generation is among the most widely adopted AI tasks in a PYMNTS Intelligence study of wholesale firms. That is drafting. This is the review decision that follows.

Picture a Melbourne insurance broker handling property claims (an illustrative scenario, not a client case). A claim comes in and someone has to make a fast call: does it look straightforward enough to fast-track, or does it need a loss adjuster on site? Today that first read often falls to whoever is free. A decision model in that step can make the same fast-track-or-flag call in seconds, using the same criteria every time, and leave the adjuster’s time for the claims that need a person.

A few things worth knowing

Some work is too repetitive for skilled people but too messy for simple rules. Think invoices arriving in 30 formats, enquiries that need a judgement call, or a report pulled from 4 systems every Monday. That’s the work AI automation services are built for: handling more work without costs rising at the same rate.

This guide covers what AI automation services are, the 6 main types, the key AI automation trends in Australia, how to choose the right approach, and how to work out ROI.

Key takeaways

• AI automation services combine AI with workflow tools to handle tasks that used to need human judgement.
• There are 6 main types: workflow automation, conversational AI, document intelligence, AI agents, data and analytics automation, and RPA.
• Choose the type of automation before you choose a provider. Most failed projects start with the wrong type.
• Start with one high-volume process, measure the return, then expand.

What are AI automation services?

AI automation services design, build and run systems that combine artificial intelligence with workflow tools to handle manual, repetitive business tasks. They include AI agents, automated workflows, document processing, chatbots and integrations between your business systems.

Unlike a basic script, AI automation can read unstructured information such as emails, PDFs and chat messages, handle exceptions, and pass anything uncertain to a person.

A complete AI automation service covers more than the build:

1. Strategy and audit: Mapping workflows and ranking them by return.
2. Design and build: Creating the automation and choosing the right tools.
3. Systems integration: Connecting your CRM, ERP, finance and operations platforms.
4. Testing and human review: Setting where people approve or check AI output.
5. Support and optimisation: Monitoring, fixing and improving after launch.

AI automation vs traditional business automation

Traditional business automation follows fixed steps, while AI automation interprets inputs and decides the next step.

A scheduled task that exports a report every morning is traditional business automation. It works until the file format changes, then it stops. An AI system processing supplier invoices can recognise that “Invoice No.” and “Inv #” mean the same thing, read PDFs from dozens of suppliers, and flag unusual amounts for review instead of failing silently.

	Traditional business automation	AI automation
Logic	Fixed “if this, then that” rules	Interprets inputs and decides next steps
Inputs	Structured and consistent	Varied formats, wording and sources
When inputs change	Breaks	Adapts, and escalates what it can’t handle
Output	Identical every time	Can vary, so review steps matter
Running cost	Very low	Model usage, plus monitoring
Best for	Payroll, backups, scheduled transfers	Enquiry triage, document reading, lead qualification

Rule of thumb: AI automation becomes useful when inputs vary in format, wording or source. If they’re always identical, traditional business automation is cheaper and more reliable. Most strong builds combine both: rules for the predictable path, AI for the steps that need judgement, and people for high-stakes approvals.

The 6 main types of AI automation services

1. Workflow automation

What it is: automation that connects your apps so one event triggers a chain of actions, with AI handling steps that need interpretation.

Example: a new website enquiry creates a CRM record, AI scores the lead and drafts a reply, sales gets an alert, and the source is logged.

• Common tools: n8n, Make, Zapier, Microsoft Power Automate
• Best for: approvals, data entry, notifications, data syncing, and sales and marketing follow-ups
• Not ideal for: old desktop software with no API

Read more: What is AI workflow automation? and our workflow automation services.

2. Conversational AI & customer service

What it is: chatbots, voice agents and AI receptionists that handle customer enquiries 24/7, route support tickets, and qualify leads.

Example: an after-hours enquiry is answered instantly, the AI asks qualifying questions, books a call and updates the CRM.

• Best for: customer service, lead qualification, bookings and repeat questions
• Not ideal for: complaints, sensitive conversations, or anything where a wrong answer creates legal risk
• Must have: a clear route to a human

Read more: Every AI customer service failure has the same shape and our customer service automation services.

3. Document intelligence

What it is: AI that extracts, classifies and checks data from unstructured documents, then sends it into the right system.

Example: supplier invoices arrive by email in different layouts. AI reads each one, matches it to a purchase order, and flags mismatches for review.

• Best for: accounts payable, onboarding, claims, contracts and applications
• Not ideal for: low volumes, where setup won’t pay back

4. AI agents (agentic systems)

What it is: AI that plans multi-step tasks and uses your tools, such as your CRM, email or databases, to reach a goal, deciding the steps as it goes.

Example: an agent researches a new lead, checks your CRM for history, drafts personalised outreach and queues it for approval.

• Best for: research, triage, multi-step support and internal assistants
• Not ideal for: high-stakes decisions without review, or businesses with disconnected systems

5. Data and analytics automation

What it is: automation that collects data from several systems and turns it into dashboards, reports, forecasts and alerts.

Example: every Monday, sales, finance and operations data is combined into one live dashboard, and AI flags unusual results.

• Best for: management reporting, reconciliations, forecasting and performance alerts
• Not ideal for: businesses whose underlying data is inconsistent. Fix the data first.

Read more: Why business reporting fails before it reaches the tool.

6. Robotic process automation (RPA)

What it is: software robots that use applications the way a person does, clicking, typing and copying data between systems. Modern RPA adds AI for reading documents and handling exceptions.

Example: a bot copies approved orders from an old desktop system with no API into a cloud finance platform.

• Common tools: UiPath, Automation Anywhere, Power Automate Desktop
• Best for: legacy systems without APIs, and high-volume back-office work
• Not ideal for: systems whose screens change often, since bots need reconfiguring

The 6 types of AI automation compared

Type	Best for	Example	Time to first result	Maintenance
Workflow automation	Connecting cloud apps	Lead to CRM to follow-up	Days to weeks	Medium
Conversational AI & customer service	Customer questions, bookings	After-hours enquiry handling	Weeks	Medium
Document intelligence	High document volumes	Invoice matching	Weeks	Medium
AI agents	Multi-step knowledge work	Lead research and outreach	Weeks to months	Medium to high
Data and analytics automation	Reporting and forecasting	Weekly management dashboard	Weeks	Low to medium
RPA	Legacy systems without APIs	Desktop-to-cloud data transfer	1 to 6 months	High

When does your business need AI automation services?

Score each process against three signals:

1. Volume: It happens many times a day or week, across your team.
2. Variation: Inputs arrive in different formats or wording, but the output is standard.
3. Cost: Skilled people spend hours a week on it, or delays cost revenue, such as leads waiting for a reply.

Two out of three makes it a strong candidate. Three out of three makes it a priority.

Skip AI when:

• The task follows fixed rules. Moving a form into a spreadsheet doesn’t need AI.
• Nobody can explain the process in a few steps. Fix the process first.
• Mistakes would be serious and nobody can review the output.

Not sure where you stand? Take the 2-minute Automation Readiness Assessment.

DIY tools, a partner or a managed service?

You can get AI automation services in three ways:

	DIY platform	Implementation partner	Managed service
What you get	Tools your team configures	A provider designs and builds it	A provider builds, monitors and improves it
Best for	Simple, clear tasks	Complex or multi-system workflows	Several live automations
Setup time	Hours to days	Weeks	Weeks, then ongoing
Strategy	You work it out	Included	Included
When it breaks	Your team fixes it	Depends on support terms	Provider fixes it
Main risk	Automating a broken process; failures across apps that are hard to trace	Dependence on an outside team	Ongoing commitment

Choose DIY (Zapier, Make, n8n, Power Automate) if your processes are simple and someone on your team is technically confident. Choose a partner if workflows span several systems, touch customer data, or affect revenue when they break. Many businesses do both. They build simple internal automations themselves and bring in a specialist for anything customer-facing or critical to revenue.

4 AI automation trends in Australia for 2026

Australian businesses are moving from trying AI tools to building automation into how work gets done. Four trends are shaping that shift:

1. AI agents are replacing basic chatbots

Businesses are moving from chatbots that answer questions to AI agents that take action across systems. SAP and Oxford Economics found AI supports 29% of tasks in the average Australian business, and leaders expect that to reach 48% within 2 years.

But agents aren’t the answer for every task. Gartner predicts over 40% of agentic AI projects will be cancelled by the end of 2027, mostly due to rising costs and unclear business value. Use agents where a task needs judgement across several steps, and simpler workflow automation for everything else.

2. Rules and AI working together

Even large organisations run mostly on rules-based automation. Services Australia had over 600 automated processes in late 2024, and about 95% of its automations are rules-based. It’s now expanding into AI-powered tools such as document reading, smarter call routing, chatbots and large language models.

3. Trust and regulation are tightening

Australians want AI governed properly before they fully trust it. A Tech Policy Design Institute survey found 85% of Australians support government regulation of AI, and 70% would use AI more if strong rules were in place. Only 1% said they completely trust AI.

The rules are catching up:

• Privacy Act: from 10 December 2026, privacy policies must explain automated decisions that significantly affect people.
• Financial services: APRA’s April 2026 letter warned that AI governance at regulated entities isn’t keeping pace with adoption.

A government survey cited by Services Australia found the 2 biggest factors in building Australians’ trust in AI are protecting personal information (73%) and being transparent about how and where AI is used (67%).

4. Adoption is wide but shallow

Most businesses now use AI in some form. 44% of Australian SMEs reported adopting AI in February 2026. But advice to the Treasurer described uptake as widespread but shallow, with fewer than 1 in 10 businesses reporting significant adoption. Governance lags too: only 22% of Australian organisations said they were mostly or fully ready on AI governance, compared with 33% globally.

The advantage is no longer access to AI tools. It’s workflow redesign, integration and governance. See why businesses hire AI automation companies instead of just buying tools.

Why do AI automation projects fail?

Most failures come down to planning, not technology:

• Automating a broken process: Automation speeds up whatever it’s given, including the mess.
• Doing too much at once: Start with one workflow, measure it, then expand.
• No monitoring or owner: Failures go unnoticed until a customer complains.
• No route to a human: Customer-facing AI that traps people creates complaints, not savings. See what AI customer service failures have in common.

Before anything goes live, run through our AI automation safety checklist.

How to choose the right AI automation service

Choose the type of automation first, then the provider. Check any option against five criteria:

1. Process fit: The type must match the work. A workflow tool can’t automate a desktop app with no API, and enterprise RPA is overkill for connecting two cloud apps.
2. Integration depth: Your specific CRM, ERP and accounting systems should be supported, not just “thousands of integrations”.
3. Error handling: Ask for a demo with one step deliberately broken, and see how failures are caught, retried and reported.
4. Total cost of ownership: Add the build, running costs, AI usage and maintenance. A cheap tool that needs a consultant every month isn’t cheap.
5. Ownership and exit: Make sure you own the workflows, code and credentials, and can export them if you leave.

See our guide to the best AI automation companies in Australia, including 7 questions to ask before you sign.

How to calculate AI automation ROI

ROI compares what a process costs today with what it costs once automated. You need 4 numbers:

1. Hours saved per week across everyone who touches the process, minus time spent reviewing AI output.
2. Fully loaded hourly cost: base rate plus superannuation (12%), payroll tax, leave and overheads. or a quick estimate, multiply the base hourly rate by 1.25 to 1.3. If your finance team has an actual loaded labour cost, use that instead.
3. Annual saving = hours per week × loaded hourly cost × 52.
4. Annual cost: build cost plus 12 months of running costs (platform, AI usage, support).

Formulas:

• ROI = (annual saving − annual cost) ÷ annual cost × 100
• Payback period in months = build cost ÷ (monthly saving − monthly running cost)

Worked example (illustrative figures):

An accounts team spends 8 hours a week processing supplier invoices, at a loaded cost of about $70 an hour. Assume automation removes the equivalent of the full 8 hours after review time:

	Amount
Annual cost of the manual process (8 × $70 × 52)	$29,120
Example build cost	$12,000
Example running costs	$300 a month
Year-one ROI	About 87%
Payback	About 6 months
Year-two ROI on ongoing operating cost	About 700%

This counts time saved only. If automation also speeds up quotes or lead replies, add the extra revenue.

Run your own numbers: the Automation ROI Calculator takes about two minutes. For measuring results after launch, read how to measure AI ROI.

Frequently asked questions

Get your first automation built free

We’ll put up to 20 hours of real build work into your business at no cost. We’ll find the workflow costing you the most time or revenue and build the automation, so you see results before you commit to anything.

Claim your 20 free hours →

Demand is growing. Deals are getting bigger. But every new customer seems to need another hire, another spreadsheet, another manual handover. That’s the problem AI automation services solve: handling more work without costs rising at the same rate.

The right AI automation company depends on the provider’s expertise, the tools it works with, how well it knows your industry, and whether it offers strategy, implementation or both. This guide covers what AI automation services are, what they can automate, how to choose a provider, and six of the strongest options in Australia.

What are AI automation services?

AI automation services design, build and run systems that combine artificial intelligence with workflow tools to handle manual, repetitive business tasks. They include AI agents, automated workflows, document processing, chatbots and integrations between your business systems.

Traditional automation, including robotic process automation (RPA), follows fixed rules: if X happens, do Y. AI automation uses language models and machine learning to read unstructured information such as emails, PDFs and chat messages, work out what’s needed, and take the next step.

What do AI automation companies do?

Service	What it can automate
AI strategy and audits	Mapping workflows, prioritising by return, building the roadmap
AI workflow automation	Approvals, notifications, data syncing, multi-step processes
AI agent development	Agents that research, answer questions, update records and complete tasks
Customer service automation	24/7 chatbots, AI receptionists, ticket routing, qualifying questions by chat or voice, CRM updates
Document processing	Extracting data from invoices, contracts, forms and applications
Data and analytics automation	Live dashboards, scheduled reports, forecasting, alerts
System integration	Connecting CRM, ERP, accounting and e-commerce platforms
Support and optimisation	Monitoring, fixes, model updates and improvements after launch

How to choose the right AI automation company

Step by step:

1. Define the outcome: capacity, response time, cost per transaction or revenue.
2. Match the type of automation: Rule-based workflows, AI agents and predictive analytics need different skills. Pick a provider that specialises in what you need.
3. Check proof: Ask for live systems, named clients and results, ideally in your industry or on your stack.
4. Check compliance: Ask how they handle access controls, encryption, data location.
5. Check commercial terms: Look for a fixed-price first build, milestone reviews, and clear ownership of code, workflows and API credentials.
6. Start with one workflow: Prove the return, then expand.

Before signing with any AI automation company, ask these 7 questions

1. What result will this deliver, and how will we measure it?
2. Can you show us a system you’ve built that’s running now?
3. Who owns the workflows, code and API credentials?
4. Where is our data processed and stored?
5. What happens when the AI gets something wrong, and who reviews it?
6. What will it cost to run each month, including hosting, API usage, licences and support?
7. Who will we work with day to day?

How we selected these AI automation companies

We assessed each provider on 8 criteria:

1. AI and automation expertise: a track record with AI agents, machine learning, generative AI and workflow automation.
2. Industry experience: work in specific sectors, so the provider understands the processes before automating them.
3. Technology and integration: the platforms it works with and how it connects to CRM, ERP, accounting and cloud systems.
4. Security and AI governance: data protection, Privacy Act readiness, access controls and human oversight.
5. Client results and scalability: named clients, published outcomes, and systems that grow with more users and data.
6. Strategy, implementation or both: whether it helps decide what to automate, builds it, or does both.
7. Maintenance and support: monitoring, updates and improvements after launch.
8. Team: the depth of the team and who clients work with.

The 6 best AI automation companies in Australia

1. Automation Consulting

Automation Consulting is an AI and automation consultancy based in Sydney and Melbourne. It combines growth strategy with implementation: it works out where the business needs to grow, which processes are worth changing, then designs and builds the AI, automation and systems to get there.

It’s built for businesses with rising sales and deal volume. Automation Consulting helps scaling Australian businesses capture that growing demand and revenue without adding headcount or costs at the same rate. Beyond AI, it covers the systems scaling businesses outgrow and offers fractional CTO support for businesses without in-house technical leadership.

Core services:

• AI strategy and workflow audits
• AI automation and AI agents
• Process automation and systems integration
• ERP consulting, custom software and e-commerce development
• Fractional CTO

What sets it apart:

• Strategy and build from one team: The people who shape the plan deliver it, across any platform.
• A low-risk start: up to 20 hours of free build work, so your first automation is delivered before you commit to a project.

Best for: growing businesses that need both growth strategy and implementation.

2. Adaptiv

Adaptiv is a data, integration and AI consultancy serving enterprise organisations in Australia and New Zealand. It focuses only on integration, data and AI, and says it isn’t tied to any vendor. It offers advisory, implementation and managed services as a single partner across the full lifecycle.

Core services:

• System, data and application integration
• API strategy and management
• Data platforms and analytics
• AI solutions built on integrated data
• 24/7 managed support

What sets it apart:

• One of few Boomi Platinum Partners globally, with MuleSoft, Solace and Microsoft capability.
• Deep focus: Integration and data are all it does.

Best for: enterprises with complex integration, data and AI environments.

3. The Missing Link

The Missing Link is a Sydney-headquartered IT firm. Infosys acquired it for $98 million in 2025. It continues to operate under its own name, with offices in Sydney, Melbourne and the UK. It runs three divisions: Cybersecurity, IT & Cloud, and AI & Automation. It launched its robotic process automation division in 2019, building on a security practice it started in 2013.

Core services:

• Intelligent automation with UiPath and Power Automate
• Generative AI and Microsoft 365 Copilot
• Cyber security, including red and blue teams and a global security operations centre
• IT and cloud services
• Managed services

What sets it apart:

• A security-first approach to automation, backed by a mature cyber practice.
• Access to Infosys’s global resources while keeping local leadership.

Best for: organisations where security and compliance come first.

4. Arinco

Arinco is a Microsoft specialist. It works across government, financial services, healthcare, retail and utilities, covering AI, data, Azure cloud, security, modern work and digital apps. In 2025 it integrated D6 Consulting, adding business consulting and program management to its technical delivery.

Core services:

• Copilots, AI agents and AI applications on Azure
• Data platforms (Microsoft Fabric, Azure Databricks)
• Azure cloud and security
• Microsoft 365 and Copilot adoption
• “Co-Ops” managed services that keep optimising cost, security and performance

What sets it apart:

• Deep Microsoft credentials and early access to Microsoft programs and funding.
• Its “Done Right” delivery framework, which focuses on governance and security foundations before AI.

Best for: organisations committed to Microsoft 365 and Azure.

5. Mantel

Mantel is an Australian-owned technology consultancy. Its AI and data work was built through Eliiza, its former AI brand, which has been folded into Mantel. Mantel works on large, multi-discipline programs where AI depends on modern data and cloud foundations.

Core services:

• AI and machine learning solutions
• Data platforms and analytics
• Cloud migration and engineering
• Digital product design and development
• Cyber security

What sets it apart:

• Breadth, with several disciplines under one Australian-owned firm.
• Strong partner status across the major cloud and data platforms.

Best for: large organisations running programs that span AI, data and cloud.

6. Accenture

Accenture is one of the world’s largest consulting and technology firms. It has partnerships with both OpenAI and Anthropic. In Australia, it works with ASX 50 companies and federal government departments. Its August 2025 acquisition of Australian cyber security firm CyberCX added local security depth.

Core services:

• AI strategy and enterprise transformation
• Agentic AI and automation at enterprise scale
• Cloud, data and systems integration
• Cyber security, through CyberCX
• Business process outsourcing

What sets it apart:

• Global scale, with teams that can run programs across many business units and countries at once.
• Partnerships with major AI and platform vendors, including OpenAI, Anthropic and ServiceNow.

Best for: large enterprises and government agencies running enterprise-wide transformation.

Comparison table

Provider	Platforms	Typical customer	Best for
Automation Consulting	Platform-agnostic	SME to mid-market	Scaling operations
Adaptiv	Platform-agnostic; Boomi, Azure, MuleSoft, Databricks	Mid-market to enterprise	Integration/data
The Missing Link	UiPath, Microsoft	Mid-market to enterprise	Security-led automation
Arinco	Microsoft only	Mid-market to enterprise	Microsoft AI
Mantel	Google, AWS, Databricks, Snowflake	Enterprise	Large AI/data programs
Accenture	Platform-agnostic	Large enterprise/government	Enterprise transformation

Why AI automation matters for Australian businesses in 2026

Australian adoption is high. 44% of Australian SMEs reported adopting AI in February 2026. But mature use is much rarer. Deloitte Access Economics found that while two-thirds of SMBs use AI, only 5% are fully enabled to benefit from it. That means having an AI strategy built into core processes, trained staff, and centralised data.

Time savings are real, but there’s a catch

In the Australian Government’s Microsoft 365 Copilot trial, public servants saved around an hour a day on tasks like summarising and searching information. Some of that time went into checking AI output for errors. That’s why well-built automation includes review steps.

Moving up pays off

Deloitte’s modelling suggests businesses moving from basic to intermediate AI use could see profitability rise about 45%, and about 111% for those moving from intermediate to fully enabled. Tools alone don’t get you there. What’s missing is the work around the tools: redesigning workflows, connecting systems, cleaning up data, setting governance, and getting automations into production.

That’s where an AI automation company comes in. A good provider decides what’s worth automating, builds it into your existing systems, adds review steps where the AI could get things wrong, and keeps it running after launch.

Does your business need AI automation?

Signs you’re ready:

• Your team spends hours each day on data entry, scheduling or copying information between apps.
• Leads go cold because replies to enquiries take too long.
• Sales are growing, but you can’t justify hiring more people just for routine work.
• Reports take days to pull together from different systems.
• Staff answer the same customer questions repeatedly.

When to skip AI and use simple automation:

• The task follows fixed rules. Moving a form submission into a spreadsheet doesn’t need AI.
• Every job is completely different, with no repeatable pattern.
• You can’t describe the process in a few steps. Fix the process first. Automating a broken process only speeds up the mess.
• The decision is high-stakes and hard to review, and you can’t put a person in the loop.

You can also check with our Automation Readiness Assessment tool.

Industries using AI automation in Australia

Industry	Common uses	Australian example or data
Financial services	Fraud detection, compliance checks, onboarding, document review	CBA’s AI fraud detection helped cut fraud losses by over 20% in H1 FY26
Healthcare	Patient intake, scheduling, clinical admin, imaging support	Health is among the highest-adopting sectors
Retail and e-commerce	Customer service, order updates, demand forecasting, recommendations	Tech Council modelling: $3 billion to $9 billion a year by 2030
Manufacturing	Predictive maintenance, production reporting, supply chain updates	Tech Council modelling: $2 billion to $5 billion a year by 2030
Logistics and warehousing	Route planning, shipment tracking, data entry, fulfilment	Automated document and order handling
Professional services	Onboarding, document drafting, billing, knowledge search	Tech Council modelling: $5 billion to $13 billion a year by 2030
Construction	Quotes, scheduling, safety documentation, progress claims	Adoption below 30%, so early movers gain an edge
Energy and utilities	Field job scheduling, asset reporting, customer enquiries	Compliance and maintenance records
Facilities management	Work order routing, contractor scheduling, maintenance reporting	High-volume job admin
Real estate	Enquiry handling, inspection bookings, CRM follow-up	Lead response and follow-up

The CBA example shows good practice: its AI agent proposes new fraud rules, but the fraud team checks and signs them off before they go live.

How Australian businesses use AI automation services

Most start with internal efficiency. Among SME adopters, content generation and data analytics are the most common uses, each cited by 54%.

The common uses:

• Workflow automation built on n8n, Make or Zapier, with AI handling data entry and routing.
• Chatbots and voice agents answering routine questions around the clock.
• Document processing that reads invoices, PDFs and technical documents.
• Built-in AI in platforms like Xero and HubSpot for reconciliation, categorisation and lead scoring.
• Microsoft Copilot for drafting, summarising and searching internal information.

The maturity path:

1. Individual tools: Staff use AI assistants for writing and research.
2. Single workflows: One process is automated, such as lead follow-up or invoice capture.
3. Connected systems: CRM, finance and operations are linked, so work moves without manual handling.
4. AI agents: Agents take on multi-step work, with people reviewing important decisions.

Deloitte’s 5% “fully enabled” figure suggests most businesses sit at steps 1 or 2. The bigger returns come at steps 3 and 4, which is usually where a provider adds the most value.

Frequently asked questions

Get your first automation built free

We’ll put up to 20 hours of real build work into your business at no cost. We’ll find the workflow costing you the most time or revenue and build the automation, so you see results before you commit to anything.

Claim your 20 free hours →

Editor’s note, 23 September 2026: the pace hasn’t slowed since this was published. On 15 September, TypeSafe AI, founded by former OpenAI researcher Diogo Almeida, released a model called Jev that isn’t a chatbot at all. It doesn’t generate text. It returns structured decisions and confidence scores for other software to consume directly, a category TypeSafe calls a System One model. Businesses now aren’t just weighing four chat-style releases from one week. They’re deciding whether the category itself, a reasoning LLM versus a structured-decision model, is the right question for a given task before they’ve even started comparing options within it.

Model fatigue is the procurement paralysis that occurs when AI model releases outpace business evaluation cycles. Organisations stall on model selection because a newer version ships before any evaluation is complete. The solution is not a more rigorous evaluation process. It is a deployment decision made against one specific, measurable workflow.

In the first week of September 2026, Anthropic, Google, Meta, and OpenAI each released a new or updated frontier AI model. CNBC reported the result: enterprise AI buyers are experiencing what one AI insider dubbed “model fatigue.” Procurement decisions are stalling. Evaluation cycles are starting on products that change before the review is finished.

This is not a technology problem. It is a decision-making problem, and it has a practical answer.

Why the standard response to model fatigue makes it worse

The standard enterprise response to a fast-moving technology market is more rigorous evaluation. Vendor shortlists. Scoring matrices. Stakeholder review panels. These are capital procurement tools designed for decisions that take years to unwind. AI model subscriptions are not that. They are monthly costs attached to products that ship updates weekly.

Applying enterprise procurement logic to AI model selection does not reduce risk. It transfers the cost of the decision from the vendor to the business. Every week spent in evaluation is a week the current process cost stays on the books. Every comparison meeting produces a recommendation that may be outdated before it is acted on.

The evaluation is the delay. The deployment is the evaluation.

The three questions that replace the evaluation matrix

Most businesses approaching AI model selection are asking the wrong question. “Which model is best?” has no stable answer. The release cadence makes it unanswerable by design.

The right questions are narrower. They are about the specific problem in front of you, not the general state of the market.

What specific process will this run on, and what does it cost today?

A model deployed against a vague objective produces a vague result. The starting point is a specific, named process with a current baseline, the same way we scope process automation services. That might be the number of invoices processed per hour, the time taken to review a contract before sign-off, or the volume of support queries resolved without human escalation. If the process cannot be described in one sentence and measured in one number, the model selection decision is premature. Define the process first. Building your first AI agent starts with exactly this step.

What does “better” look like, and how will you measure it?

The organisations that can demonstrate AI ROI share one characteristic: they defined what better looked like before they spent anything. A metric that only exists because AI exists cannot prove that AI worked. The baseline has to predate the deployment. Write down the current number before any model is introduced. Agree on what improvement looks like in concrete terms before the first prompt is written. This is the same measurement problem that breaks business reporting before it reaches any tool.

Can you get it into production in 30 days?

Thirty days is not an arbitrary target. It is the minimum timeframe to generate production data before the next wave of model releases adds noise to the decision. If the answer is no, the blocker is not the model. It is something else: integration complexity, internal approval, data access, or process definition. Those blockers exist regardless of which model is selected. Solve them first.

How to pick a model once you can answer all three

If you have a specific process, a current baseline, and a 30-day deployment path, the model selection criterion becomes narrow. Pick the model your team can deploy against this workflow this week.

Not the model that ranked highest on a benchmark last Tuesday. Not the model a competitor is using. The one with existing API access. The one your team can configure fastest. The one that can go into production before the next release cycle changes the comparison.

Four weeks of a live workflow produces more useful information than any evaluation matrix. After four weeks, you have production data. You can measure actual performance against the baseline you set before deployment. If a better model has shipped by then, the decision to switch is a data decision. You will not have data until something is running.

This is how iteration works in practice. A specific process. A baseline. A deployed model. Four weeks of data. A decision informed by that data. The first deployment will not be optimal. It will be more useful than waiting.

What the release cadence means for Australian businesses

The four-model week in September 2026 is not an anomaly. Multiple major model updates per month across the leading providers is the current state of the industry. It is not expected to slow.

For Australian operations managers, this creates an asymmetry worth noting. Large enterprise procurement teams are the ones stalling. Smaller operators who can define a process on a Monday, deploy a model by Friday, and have four weeks of production data before the next enterprise evaluation meeting has even been scheduled are the ones who will be ahead in twelve months.

The advantage is not technical. It is structural. The window is open now.

Frequently asked questions about AI model fatigue

Ready to deploy AI on a specific process?

Automation Consulting is an Australian AI automation company, and our 20 Hours Free offer gives Australian businesses up to $3,000 of pro bono AI and automation work scoped to one specific process, in exchange for a case study. No general AI strategy. One defined problem. Real production data within 30 days.

This guide explains how to build an AI agent for your business without writing code — covering how to select the right first task, and how to build the six components that turn a chatbot into an agent that runs independently.

Why most businesses are still using AI wrong

Most businesses using AI today are using it as a chatbot. You type a question, it gives an answer, you copy that answer somewhere useful and move on. Every step requires a person in the middle.

An agent works differently. It is a loop — looking at a goal, taking a step, checking what happened, then continuing until the job is done. From there, it can reach outside itself — send an email, update a spreadsheet, pull data from your CRM — without you issuing each instruction.

As of June 2026, OpenAI’s coding agents account for 64% of all tokens consumed by its enterprise customers. That is not a chatbot metric. It means the majority of enterprise AI use has already shifted from asking questions to delegating work.

Most Australian businesses are still on the asking side. As of February 2026, only 8% of Australian SMBs report using AI broadly, with 16% describing their use as limited. (Source: NAIC AI Adoption Insights, ai.gov.au, February 2026)

Triggered byA user questionAn event, schedule, or form submissionRuns whenYou ask itAutomatically, on a defined scheduleOutputA text responseA completed task or actionMemory between sessionsNonePersistent context, rules, and proceduresTool accessNoneEmail, CRM, calendar, files via MCPScopeOne question at a timeFull workflow from trigger to finished output

Feature	Chatbot	AI Agent

Step one: pick the right first task

The task you start with determines whether your first agent succeeds or stalls. Not every repetitive task is the right starting point.

Three criteria for a good first agent task

A task qualifies if it meets all three of the following.

It happens more than once a week. Low-frequency tasks are harder to train because you see fewer examples of what correct output looks like before you automate.

It has a consistent trigger. A trigger is the event that starts the task — an email arriving, a form being submitted, a scheduled time being reached. If the task starts differently every time, the agent cannot run reliably.

It produces a predictable output. A report, a notification, a data entry row, a drafted reply. If the output changes shape depending on circumstances, the agent cannot be evaluated consistently.

Monthly invoice routing qualifies. Lead qualification from inbound enquiry forms qualifies. Weekly operations summaries qualify. “Help me think through this” does not.

The businesses we work with most commonly start with one of three workflows: inbound lead triage, internal reporting, or document processing.

Build the trigger first, not the logic

Most first agents fail because the builder starts by writing instructions for what the AI should do, before locking where the task starts and where the result lands.

Define the trigger and the destination first. What event starts the task? Where does the finished output go? Once those two things are fixed, write the instructions in between. This single rule prevents the most common first-build failure.

Test before you automate

Before setting the agent to run automatically, test it on five real historical examples. Use cases that have already happened, with known correct outputs.

Four of five correct: the agent is ready to run. Three of five correct: the prompt needs work, not a different tool. Fewer than three: the task definition is too broad — narrow it first.

This test takes less than an hour and prevents an agent from running on live work before it is reliable.

How to build the agent: six rungs

Once you have the right task, build the agent in six stages. Each stage depends on the one before it. Skipping ahead is the most common reason first builds underperform.

Rung 1: Context

Before the agent can do anything useful, it needs to know your world. Not in general terms. Specifically: who your customers are, how your operation works, what you have decided and why.

Write this down in plain text. The agent reads it every time it runs. Nothing it produces is generic because it is reading your actual business before it moves.

Context compounds over time. Every time the agent works, it can write observations back to those files. You are training it on your operation, and that training belongs to you. Anyone can access the same AI model. No one can replicate the context you have built.

This is the stage most businesses skip. It is the one that determines output quality more than any other.

Rung 2: Memory

Context is what you give the agent. Memory is what it keeps from doing the actual work.

There are three kinds. The agent remembers facts about your business and customers. It remembers rules — every correction you make is saved and never broken again. And it remembers procedures — a step-by-step method for completing a specific task, owned permanently once taught.

Together, context and memory are what separate a generic AI tool from one that works the way your business works.

Rung 3: A lane, not a task

A task is a one-off instruction. “Draft this email.” Done, gone.

A lane is ongoing ownership. “You handle the inbox. Read what comes in, sort it by priority, draft replies, and flag anything that needs a human decision. Every day, without me asking.”

The moment an agent owns a lane, you stop assigning work. The work runs itself. That is the difference between a tool you operate and a worker who operates.

Rung 4: Tools

An agent with no connection to your actual systems can only describe work, not do it. Connect it to where the work lives — your email, your calendar, your CRM, your files.

For a first build, MCP (Model Context Protocol) is the simplest approach. No code required. Most common business tools can be connected in under a minute.

Once connected, the agent stops drafting emails for you to send. It sends them directly. Rather than summarising your calendar, it reads it and acts on what it finds.

Rung 5: A schedule

An agent with context, memory, a lane, and tools is still waiting for you to trigger it. A schedule removes that dependency.

Set it to run every morning, every hour, or overnight. It wakes up on its own, completes its lane, and contacts you only when a decision requires a human. You go from operating the agent to receiving its output.

This is the stage at which the work genuinely runs without you.

Rung 6: Guardrails

An agent that runs automatically, touches your real accounts, and operates while you are not watching needs boundaries set before it is let loose.

Define three things: what it is allowed to touch, what it must never touch, and which decisions require your approval before action is taken.

Low-stakes tasks it handles without checking. High-stakes decisions — a refund above a set threshold, an email to a key client, a change to a financial record — it drafts and holds for your sign-off.

You stop being the operator. You become the approver.

What this looks like in a real Australian business

A Sydney-based mortgage broking firm was managing roughly 120 active loan applications at any given time. Their admin team was spending the majority of each day on routine client communication — chasing missing documents, sending status updates at each stage of the application, and manually updating their compliance log after every client interaction.

An agent was built to own that lane. It monitored the application pipeline, identified which stage each file was at, sent the appropriate status update to the client, flagged missing documents to the relevant broker, and updated the compliance log automatically. The agent was scoped and running within two weeks. Routine client communication, which had previously consumed the majority of two staff members’ days, was reduced to a morning review of flagged exceptions.

The same business applied the same six-rung build to a second workflow the following month.

How long does it take to build a first AI agent

A first agent built with the six-rung approach typically takes one to two weeks from task selection to reliable automated output.

The first few days involve corrections as the agent learns the business context. By the end of the second week most agents are running consistently. By the end of the first month the correction rate drops significantly and the agent begins to handle edge cases it was not explicitly trained on.

A common pattern: rough on day three, reliable by day fourteen, genuinely yours by day thirty.

Building your second and third agent

Once the first agent is running, the second build is faster. Context files already exist. Tool connections are already in place, and the guardrail framework carries over too.

Each subsequent agent inherits the shared knowledge about your business and is pointed at a new lane. A team of agents running in parallel — each owning a different workflow — is how businesses move from managing tasks to managing outcomes.

The businesses seeing the strongest results from AI are not using more sophisticated tools. They are running more tasks through structured, repeatable agent workflows.

Frequently asked questions

Start building today

Not sure which task to start with? Automation Consulting works with Australian businesses to identify, scope, and build first agent workflows. Our 20 Hours Free programme covers the full build at no cost for qualifying businesses — scoping included.

In January, Judith Butterfield had a stroke and spent 2 months in Doncaster Royal Infirmary. The stroke affected the right side of her body and left her speech fragmented.

Her GP surgery had installed an AI reception service to reduce phone queues. She tried to book an appointment 5 times and did not reach a human on any attempt.

The system asked callers not to use speakerphone. Butterfield held the phone in her left hand because her right hand could no longer operate a keypad. When the system asked her to repeat her name, it did not understand her, and the call ended. She told the BBC the experience was “very difficult and upsetting.” A receptionist could have asked her to spell it.

Butterfield, 71, registered with a different practice. Her original surgery has since decommissioned the AI system and recruited more reception staff. The watchdog Healthwatch reports similar problems from other Yorkshire patients, including one case involving a regional accent.

The same failure has now played out at a bank and an airline, with the same underlying shape.

Why do AI customer service systems fail?

AI customer service systems fail for structural reasons rather than technical ones. Two documented cases show what that looks like at scale.

Commonwealth Bank: the queue that did not shrink

In July 2025, Commonwealth Bank of Australia cut 45 customer service roles, saying its new AI voice bot had reduced call volumes by around 2,000 a week. Staff reported the opposite. The Finance Sector Union said volumes were rising, overtime was being offered to cover the load, and team leaders were being pulled onto the phones. The union took the bank to the workplace relations tribunal over its call volume claims.

On 21 August 2025, CBA reversed the redundancies and apologised, saying it “did not adequately consider all relevant business considerations” and that the roles were not redundant.

The work had not disappeared. The bot absorbed the simple calls, and customers with urgent or complicated problems kept calling. Automating the easy contacts changed the composition of the queue rather than its size.

Air Canada: the company owns what the bot says

On the day his grandmother died, Jake Moffatt asked Air Canada’s chatbot about bereavement fares. It told him he could book now and claim the reduced rate within 90 days of the ticket being issued. The airline’s actual policy, on the page the chatbot linked to, does not allow refunds for travel already taken. Moffatt booked at full fare, applied, and was refused.

British Columbia’s Civil Resolution Tribunal found Air Canada liable for negligent misrepresentation and awarded Moffatt C$812.02. The airline had argued its chatbot was a separate legal entity responsible for its own actions. The tribunal rejected that. It also rejected the argument that the correct policy was available elsewhere on the site, asking why a customer should have to check one part of a company’s website against another.

That was not a defence. Whatever your AI says is what your company said.

Deflection rate conceals the problem

Most AI customer service deployments are measured on deflection rate, which is the share of enquiries resolved without a human. Judith Butterfield’s five failed calls each counted as deflected.

Deflection rate does not separate a solved problem from an abandoned one. A deployment can report 80 percent deflection while losing its most frustrated and most vulnerable customers. CBA’s case shows the same distortion one level up: the bot’s deflection figures looked like reduced demand while the queue behind it was growing.

What to measure instead: resolution rate, which is the share of enquiries actually resolved, and escalation rate, which is the share reaching a human. Also track the proportion of conversations that end without either outcome.

What do teams miss when deploying AI in customer service?

Seven failure points account for most of the damage. All seven are design decisions rather than model limitations.

1. The callers the system was not designed for

Voice AI is usually tested on clear, standard-accent speech. Real callers have regional accents, second languages, speech affected by illness or age, background noise and poor reception.

Butterfield’s case involved two assumptions at once: that her speech would be recognised, and that she could use a keypad if it was not. Neither assumption held. The people excluded by assumptions like these are often the ones with the most urgent need.

2. No route to a human

In each of the cases above, the customer could not exit the automated conversation on the terms they needed. An AI assistant that cannot answer a question should hand over on the first failure rather than rephrase the same answer. We design that handover first in the AI automation solutions we build.

The vendor behind the GP reception system states that practices can enable routing straight through to reception on every call. That option existed at Butterfield’s surgery and was not switched on.

3. Emotion as a routing trigger

Distress, anger, urgency, legal language and bereavement appear regularly in support queues. They are also the interactions where a wrong answer costs the most. Moffatt was asking about a bereavement fare on the day his grandmother died, which is exactly the conversation that should have reached a person. Route these on detection rather than after several failed attempts.

4. Scope set too wide

AI support deployments that work handle a small set of high-volume, well-defined requests and escalate everything else with the conversation history attached. Deployments that fail attempt every request type at once and handle all of them poorly.

CBA’s experience adds a second point. Automating the simple contacts changes the composition of what remains. Plan capacity for the queue you will have after deployment, not the one you have now.

5. No memory across the conversation

Some systems treat each message as a separate event. The customer explains the situation, answers a clarifying question, and finds by the third message that the opening has been forgotten. The same happens when a customer moves from chat to phone and has to start again.

Repeating yourself is the point at which most people stop trying. Confirm that context persists across messages and across channels before going live.

6. Answers invented from a contaminated knowledge base

An AI assistant will produce an answer even when the correct one is not available to it. Air Canada’s chatbot described a bereavement policy the airline did not have.

The usual cause is the source material. Internal notes, draft pricing, superseded policies and old support threads get loaded alongside customer-facing content, and the assistant resolves the contradictions at random.

Build a separate knowledge base containing only approved customer-facing information, and check it for contradictions before launch rather than after.

7. The assistant cannot take action

Most support requests need something done rather than something explained. A refund processed. An address changed. An appointment moved. An account unlocked.

An assistant connected only to a knowledge base can describe the process and cannot complete it, so the customer is left with instructions they cannot act on. This produces the most common complaint about AI support, which is being sent a link to a help page the customer has already read.

Decide before deployment which actions the assistant can execute in your systems, and route everything else to someone who can.

Where does AI belong in customer service?

Each failure above has the same shape. A human service existed, it was removed or hidden, and AI became the only way through. A patient needed a doctor. A grieving passenger needed a fare policy. A banking customer needed a problem fixed that the bot could not fix.

Compare that with a visitor on a website at 9pm with a question about whether a product suits their room. That visitor is not in a queue and is not being denied anything. Without an assistant they leave the site, and the business never knows they were there. The alternative to AI in that case is no response at all.

The rule: use AI to add a route, never to remove one.

An example

We built an AI consultant for a major Australian flooring retailer on the add-a-route principle. It answers product and service questions, works out what the visitor needs, and recommends suitable options with clickable links and images shown in the chat. Where relevant it prompts them to book an in-store or in-home consultation, and pre-fills part of the booking form from what the conversation has already covered.

It answers from approved product and service content, holds context so the visitor is not asked the same thing twice, and follows a defined path for each common situation rather than one general instruction set. Anything it cannot resolve goes to a person who follows up directly, which was a requirement at the start of the build rather than an addition to it.

We keep tightening it against real conversations: what visitors actually ask, and where the assistant fell short.

If you want the same approach applied to your own site or support line, we can start by mapping where your customers currently get stuck.  Start with 20 hours free: real consulting work, no cost, before you commit to anything.

Summary

Placement determines the outcome in AI customer service. An AI assistant put in front of an urgent need, with the human alternative removed and success measured by how few callers reach a person, will eventually reproduce Butterfield’s five phone calls or CBA’s reversal.

An AI assistant that opens a route which was previously closed, with a person one step away, handles enquiries that would otherwise go unanswered.

Frequently asked questions

Leading companies are already seeing close to $3 back for every $1 they put into AI, according to data from McKinsey. The strongest returns aren’t coming from broad “let’s use AI everywhere” experiments. They’re coming from focused workflow automation aimed at one process at a time. Morgan Stanley‘s own tracking found the number of S&P 500 companies reporting measurable AI impact nearly doubled in a single year.

This post covers three things: what AI workflow automation actually is, what it’s already done for businesses across different industries, and what it actually costs.

What is AI workflow automation, really?

Simply explain:

Traditional automation (including most of what you’d call RPA)	AI workflow automation
follows a fixed rule. If a form field says “urgent,” route it to the urgent queue. It’s fast, it’s reliable, and it breaks the moment the input looks even slightly different from what the rule expected.	reads the input, not just the label, and decides. It can look at an unstructured email, a scanned invoice, or a customer message with no fixed format, understand what’s actually being asked, and take the appropriate next step, without someone having pre-written a rule for that exact case.

Ask where the process currently needs a person to read something and decide, rather than just tick a box. That’s the exact seam where AI-driven process automation earns its cost over a simple rule.

And no, it’s not the same as “someone on the team uses ChatGPT.” That’s real value, but it’s one person, one task, no memory between sessions, and nothing connected to your other systems. AI workflow automation is the same underlying capability wired into an actual process – triggered automatically, connected to your tools, running whether or not someone remembers to open a chat window. That gap is exactly what AI automation services are built to close.

Where AI actually fits: a framework for process automation

The single most common mistake isn’t picking the wrong AI tool. It’s picking AI for a task that never needed it, or under-building a task that genuinely does. Match the task to the category first:

If the task is…	You need…	What that looks like
The same steps, every time, no judgment calls	Basic automation (no AI needed)	Zapier, Make, or your existing platform’s built-in automation rules
Reading and judging unstructured input (emails, tickets, documents, call notes)	An AI agent	Automated lead scoring, ticket triage, document data extraction
Producing new content or messaging, not reacting to input	A generative AI workflow	Drafting first-pass reports, personalising outreach at scale, summarising long documents
Predicting what’s likely to happen next, based on historical patterns	A predictive model	Demand forecasting, churn prediction, budget forecasting
Spanning multiple systems and approval steps	A custom AI workflow build	Bespoke integration connecting your CRM, inbox, and finance tools with an agent making the calls in between
Real-time, high-stakes decisioning at volume	An advanced custom system	Purpose-built model for fraud detection, dynamic pricing, or similar

Most real workflows are hybrids, not one pure type. Invoice processing, for instance, is usually rule-based matching plus AI judgment on the exceptions that don’t match cleanly. It’s normal for one process to need two or three of the above working together.

Use cases: where AI workflow automation already pays off

A straight look at what this looks like in practice across business functions, so you can see where your own bottleneck might fit:

Business Function	What this looks like in practice	What the data shows
Customer service	From Automation Consulting’s own work: an AI consultant built for a major Australian flooring retailer answers product questions and recommends products with images and clickable links right in the chat, turning website visitors into booked quotes	10.86% conversion to quote; significant increase in leads
Finance & invoicing	Invoices are read, matched against purchase orders, and flagged automatically when something doesn’t line up	Processing time cut from 17.9 days to 3.4 days; 40–80% lower cost per invoice
Demand & inventory forecasting	Historical sales, seasonality, and market signals feed a model that predicts what stock levels will actually be needed	Cuts overstock costs by roughly 18% for mid-sized distributors
HR & recruitment	Resume screening, interview scheduling, and candidate FAQs are handled automatically, with a human still making the final call on who gets hired	Up to 50% faster time-to-hire and 75% of candidate communications automated; Nestlé has publicly reported saving roughly 8,000 admin hours a month this way
IT & internal support	Routine Level 1 tickets – password resets, access requests, standard troubleshooting – are triaged and resolved by an AI agent before they ever reach a person	Median resolution time of 4.4 hours with AI automation versus 71 hours without, measured across 50,000+ real tickets from 30+ organisations
Manufacturing & operations	Digital tooling, process redesign, and workforce retraining rolled out together across a plant’s operations	15–25% operational EBITDA improvement
Real-time fraud detection	Transactions are scored for risk in real time as they happen, instead of a fixed rule flagging anything over a dollar threshold	42% of card issuers and 26% of acquirers saved more than $5 million in fraud attempts over two years

These are seven functions where the pattern is well-documented, not the limit of where it applies. The same logic extends to any process where someone is currently reading, judging, or deciding by hand: procurement approvals, compliance checks, contract review, logistics scheduling. If you’re not sure whether your own bottleneck fits, that’s exactly the kind of thing we scope in a 20-hour free build – real work on your actual process, not a generic demo.

Where this leaves Australian businesses

The National AI Centre‘s most rigorous ongoing tracker puts SME AI adoption at 44% as of February 2026, other surveys range as low as 29% and as high as 84%, depending on how loosely “using AI” gets defined. Adoption and capability aren’t the same thing. Most of that 44% is someone using a chatbot occasionally, not a working system.

The more telling number sits inside that 44%: broad adoption, where AI is embedded across multiple parts of a business rather than one isolated task, just hit its highest level in seven months. Businesses that commit tend to expand their use rather than pull back. The real gap isn’t people trying AI and giving up. It’s the majority who haven’t started at all.

What’s actually stopping most Australian businesses from adopting AI workflow automation?

• Trust, by far the biggest one: Around 65% of non-adopting businesses cite distrust in AI decision-making or a preference to keep humans fully in control. This shows up the same way across business sizes and industries – it’s not a small-business-specific hesitation.
• Relevance – and this is the most fixable one: 54% of non-adopters say AI simply isn’t relevant to their business. The gap is stark by industry: fewer than 30% adoption in construction and agriculture, versus more than half of businesses already using AI in health, education, and services. That’s not a capability gap. It’s a lack of visible examples of what this looks like for a business like theirs – which is exactly the gap the use-case table above is meant to close.
• Not knowing where to start: 19% of SMEs say they don’t know how to apply AI to their business at all, up from the previous quarter. This group isn’t resistant, just without a clear entry point – which is a different problem to solve than trust or relevance, and usually the easiest one.
• Lack of in-house expertise: Some businesses just don’t have anyone on staff who knows how to evaluate a solution or a vendor.

Deloitte’s research on Australian AI adopters found something worth sitting with: SMEs that implement AI report productivity gains of 25–35%, notably higher than the 15–20% large enterprises report. In a smaller business, automating even one workflow lands harder – with fewer people wearing more hats, every hour saved is felt directly rather than absorbed into a large org chart.

Put together: the barrier isn’t that automation doesn’t work for smaller Australian businesses. It’s that most don’t have anyone in-house who knows where to start.

The number that makes moving now worth it: MYOB’s data shows AI-adopting SMEs are growing 2.8 times faster than the ones that aren’t. That gap is already showing up in revenue, not just survey answers.

If you want a clear-eyed read on where your own business sits, start with 20 hours free — real consulting work, no cost, before you commit to anything.

Common questions

Quick answer: Before any AI automation goes live, business owners should ask six questions: what systems does it connect to, what can it change, does it need internet access and for what, what happens if it makes a mistake overnight, is there a log of what it did, and when will its access be reviewed. Developers and vibe coders should run nine checks covering dedicated credentials, OAuth scope, network allowlisting, filesystem access, credential hygiene, blast radius, rollback capability, logging, and access review dates.

Over the past few weeks, AI security has been impossible to ignore.

Two incidents. One root cause.

OpenAI disclosed that two of its models broke out of a sandboxed testing environment, found their way to the internet, and independently identified and breached Hugging Face, carrying out more than 17,000 actions over several days. The Hugging Face CEO described it as “very weird and unprecedented.” OpenAI then found additional escapes when it investigated further.

Anthropic separately disclosed that its own model had gained unauthorised access to outside organisations in three different security evaluations conducted between April and July.

Both companies admitted the same underlying problem. Not that the AI was too capable. That the environments gave it more access than the task required, and neither company applied monitoring correctly.

Engineers made configuration mistakes. The AI did what it was built to do. Nobody was watching closely enough.

This is not a problem unique to AI research labs. Every business deploying a workflow automation makes the same decisions: what to connect it to, what it can do, and whether anyone is checking what it did. At Automation Consulting, we scope every automation we build for clients across retail, fintech, professional services, and real estate against these questions. These are the questions worth asking before your next one goes live.

If you are a business owner

Two AI security incidents made headlines this week. In both cases, the root cause was the same: the AI had access to more than the task required.

Most businesses will never face anything at that scale. But the question both incidents raise applies equally to a small business deploying a customer follow-up automation as it does to OpenAI running a security benchmark.

If you do not have a technical background, these questions are the ones to put to your tech partner before any automation goes live. You do not need to understand every answer in detail. You need to know that your partner can answer them clearly, and that the answers are in writing.

What systems does this connect to?

Every system the automation touches is a potential failure point if something goes wrong.

Ask your tech partner to list every integration by name: your CRM, email, file storage, accounting software, any external APIs. If they cannot give you a complete list, that is the first thing to fix before anything else.

What can it change, not just read?

Reading data is low risk. Writing, updating, deleting, or sending is where mistakes become expensive.

An automation that monitors your inbox is very different from one that replies to it. Ask your tech partner to separate read actions from write actions. If the automation can send emails, update records, or delete files, that list needs to be explicit. “It handles customer communications” is not sufficient. “It reads enquiry emails and creates a CRM record, it cannot send anything” is.

Does it need internet access? For what, specifically?

An automation that works entirely within your own systems has no reason to call external services. If it does need internet access, there should be a specific list of services it is permitted to call.

“It needs to reach the internet” is not an answer. “It calls the SendGrid API to send confirmation emails, and nothing else” is. If your tech partner cannot tell you exactly which external services the automation contacts, resolve that before deployment.

If it runs overnight and makes a mistake, what does it touch?

Automations often run without anyone watching. The question is not whether mistakes can happen, they can. The question is whether a mistake at 2am affects one record or ten thousand, and whether it can be reversed.

Ask: what is the worst realistic outcome of a bug in this automation? Can it be undone? If the answer is “it would update every contact in our database and we would not be able to reverse it,” that automation needs a human approval step before the irreversible action runs.

Can I see what it did?

If something goes wrong, you need to be able to look back and see exactly what the automation did, when, and to what.

There should be a log. Check how long it is kept and who can access it. If your tech partner cannot show you a record of what the automation did yesterday, that needs to change before it runs unsupervised in production.

When will its access be reviewed?

Automations outlive the problems they were built to solve. The access granted on day one may be more than is needed on day 365, because the workflow changed, the business changed, or the integration was only ever temporary.

Before sign-off, agree on a review date. Six months is a reasonable starting point. Put it in the project documentation, not just in someone’s memory.

What a good answer looks like

A tech partner who takes these questions seriously will give you specific, plain-language answers. They will be able to tell you exactly which systems are connected, exactly which actions the automation can take, and exactly what a mistake would look like in practice.

Vague answers, “it is all contained,” “that is handled on our end,” “do not worry, it is safe,” are not answers. They are reasons to ask again.

The goal is not to distrust your tech partner. It is to make sure that both of you are looking at the same thing before it goes live.

If you are building it yourself — developers and vibe coders

You have built something that works. Before it goes live, or before you hand it credentials and walk away, run through this list.

Most of these take under five minutes each. Together, they define the difference between an automation that fails cleanly and one that does real damage at 3am. This is not a guide for security engineers. It is for developers who built something fast, and for anyone building through vibe coding and AI-assisted development, who want to check it is scoped correctly before it touches production data.

Use a dedicated credential for this automation

Do not connect your automation using your personal login or a master API key. Create a service account or generate an API key specifically for this integration.

If the automation is ever compromised, or if you simply want to revoke access, you should be able to cut off that one credential without touching anything else. An automation connected under your personal account means revoking it disconnects you from everything else that account touches.

Check the permission scope before you connect

Most OAuth flows and API configurations let you restrict what an integration can actually do. Before you connect any service, check what permissions you are granting.

If your automation reads invoices, it needs read access to invoices, not admin rights to the whole account. Most developers accept the default scope without checking. The default scope is almost always broader than necessary. Check it, then reduce it.

If it needs internet access, define what it is allowed to call

An automation that calls one external API has no reason to make arbitrary outbound requests.

In n8n, Zapier, or any cloud platform, check what the workflow can actually reach. For self-hosted builds, consider an egress allowlist, a short list of specific domains it is permitted to call, with everything else blocked by default. If you cannot do that at the network level, at least document which services it is supposed to call so you have a baseline to compare against if something unexpected shows up in the logs.

For AI coding agents: restrict filesystem access to the project folder

If you are using an AI coding agent (Cursor, Claude Code, Copilot Workspace, or similar), configure it to operate only within the project directory before you start the session.

It should not have access to your home folder, your .env files, your SSH keys, or anything outside the project scope. Most tools have a setting for this. The default is often everything the current user can reach. That is not the setting you want.

Never put real credentials in a prompt

If your AI coding tool needs an API key to generate working code, use a placeholder in the prompt and inject the real value from your environment at runtime.

Prompts may be logged by the tool, by the platform, or by infrastructure you do not control. Anyone with log access can recover credentials stored in prompts. Use environment variables. Always.

Define the blast radius before you give it write access

Before any automation gets write access anywhere, ask: if this runs with a bug, what does it affect?

A single record, or all of them? One email, or ten thousand? A single file, or the entire directory? If the blast radius is large, add a human approval step before the irreversible action fires. The cost of one extra click is always lower than the cost of the cleanup.

Confirm you can roll back

For any automation that writes to a database, modifies files, or sends external communications: confirm you have a way to undo it before you deploy.

A backup is not enough on its own. You need to know which specific records were changed, when, and to what previous state. If you cannot answer that question, either add change logging before you deploy or restrict the automation to read-only until you can.

Build logging in from the start

Every production automation should write a log: what it did, when, what it changed, and whether it succeeded or failed.

In n8n this is largely automatic. In custom builds, you need to add it deliberately. Knowing what your systems are actually doing is the foundation of safe automation. Retrofitting logging after something has gone wrong is significantly harder, and you will always wish you had it. If you are building fast, logging is the one thing worth slowing down for.

Set a review date before you deploy

When you deploy, put a calendar reminder for six months out to review what the automation still has access to, and whether it still needs it.

Access accumulates. A workflow that connected to three services at launch often connects to six a year later. Permissions granted for a temporary task stay in place permanently unless someone explicitly removes them. A scheduled review is the cheapest governance mechanism available and almost nobody does it.

If someone non-technical asks whether your automation is safe, the honest answer has three parts: what it can read, what it can change, and what happens if it makes a mistake. Clear plain-language answers to all three usually means your scope is correct. If you hesitate on any of them, go back through this list before you hand it to production.

What both lists have in common

The incidents at OpenAI and Anthropic did not result from AI that was too intelligent or too autonomous. In both cases, the environments gave the AI more access than the task required, and the teams had not applied monitoring to the right scenario.

The same risks apply at any scale. The question is not whether to trust AI. It is whether your setup gives it only what it needs to do its job, and whether you would know if something went wrong.

These are the questions we ask before every automation we build for clients. They take less than an hour to work through. They are worth doing before the next one goes live.

Frequently asked questions

Claude Fable 5 returned on July 1, after the US government’s export-control directive pulled it offline for 19 days. It came back free on Pro, Max, and Team plans through July 19, and only up to 50% of your weekly usage. After that, it’s usage credits or nothing.

We covered what Fable 5 actually is when it first launched, and what the ban itself signalled for Australian businesses. This post is the practical follow-up: what can Claude Fable 5 actually do, and what’s worth building with it.

What Can Claude Fable 5 Actually Do?

Short version: it’s not a better chatbot. Claude Fable 5 is built to run for hours on one hard problem — deep coding, long documents, multi-step planning — and check its own work as it goes.

That’s not marketing language. It shows up in what people have actually shipped with it:

• Stripe used it to migrate a 50-million-line Ruby codebase in a single day — a job their own team estimated would take two months by hand.
• A game studio rebuilding HermesWorld (a live MMO) had Fable 5 find and fix six bugs in one afternoon that had accumulated over a month of work with Opus 4.8.

I'm having Claude Fable 5 redo HermesWorld 🚨

Spent the last month designing, building & prototyping HermesWorld with Opus 4.8 — a live MMO where humans and AI agents play together.

Fable 5 just found and fixed 6 bugs in one afternoon that took weeks to accumulate.

The game is… pic.twitter.com/M2LNB5fdRh

— Eric ⚡️ Building… (@outsource_) June 9, 2026

• Wharton professor Ethan Mollick gave it one shader prompt — an infinite gothic city drowned in stormy waves — then just said “make it better.” No spec, no follow-up detail. It nailed the aesthetic call on its own.

Fable: "create a visually interesting shader that can run in twigl-dot-app make it like an infinite city of neo-gothic towers partially drowned in a stormy ocean with large waves." "Make it better"

All of this is procedurally generated. https://t.co/rYai1s4yv2 pic.twitter.com/ky0q5ho643

— Ethan Mollick (@emollick) June 9, 2026

That’s the pattern worth noticing: the more open-ended and multi-step the task, the bigger the gap between Fable 5 and everything else.

Claude Fable 5 Use Cases Worth Trying

If you’re deciding what to actually run through it, these are the categories worth your usage cap:

A real audit of something you already shipped

Multiple users are pointing Claude Fable 5 at products they’ve been running for months and asking it to find what’s actually wrong. It spins up several agents, runs the full test suite, and catches bugs that Opus and GPT had already missed. In one case, it found a sign-out edge case that could leak one user’s data into another user’s account. That’s exactly the kind of quiet, expensive bug most teams don’t find until a customer does.

Fable 5 will hand you the list. Acting on it is the harder half, and that’s usually where it stalls — the findings sit in a doc because nobody owns the fix. If an audit turns up things you’d rather not sit on, that’s the work we do as an independent IT consulting engagement: review what’s actually there, then cost the fixes in the order they’ll pay you back.

A UI or UX pass with a real brief

If you want to see what Fable 5 is actually capable of, give it more to work with: your brand guidelines, a screenshot, a clear scope of what “done” looks like. That’s where the gap between a nice refresh and a genuinely sharp one shows up.

Comment
byu/No_Rip_7664 from discussion
inClaudeAI

Comment
byu/No_Rip_7664 from discussion
inClaudeAI

A plan another model executes

Fable 5’s edge is judgment, not typing speed. The highest-leverage pattern we’re seeing: have it draft the detailed plan — architecture, decisions, risks, open questions — then hand execution to Opus 4.8 or Sonnet. You get the reasoning without paying premium rates for the boilerplate.

Something that outlasts the model

Use Fable 5 to build things that keep paying off after the window closes: documented workflows, a cleaned-up prompt library, custom instructions in a Claude Project. It’s genuinely better at judging what’s worth documenting — spotting the patterns that repeat, catching edge cases a first draft misses, writing instructions clear enough for a cheaper model to follow later. Think of it as paying a senior person to write the manual once. Most people skip this one. It’s also the one with the real compounding return.

That’s also the difference between a clever prompt and a system you can rely on. Documented, running without you, still earning in twelve months — that’s what process automation actually is, and it’s the step most teams never reach because the day job wins.

What to Build With Claude Fable 5 If You Run a Business?

Translate the above into what it looks like on a Tuesday:

Marketing teams	Feed it your last quarter of campaign data, competitor positioning, and performance numbers, and ask for a single interactive dashboard you can actually review. The version that rebuilds itself every morning instead of being re-made by hand is reporting automation.
Sales teams	Hand it your call notes, CRM export, and lost-deal reasons from the last quarter and ask it to find the actual pattern in why deals stall — not a generic “improve your pitch” answer.
Operations	Point it at a workflow that’s always been “good enough” and ask it to find where it actually breaks under edge cases, not where it looks fine on a demo. What it finds is your shortlist for modernising the systems around it.
QA teams	Run the audit prompt across a whole product. It holds context long enough to catch issues that only show up when several parts interact.
Developers	Use it for the migration or refactor you’ve been putting off because it touches too many files to safely do by hand.

Automation Workflow Ideas Worth Stealing

This is the part that matters most if you’re trying to optimise workflows, break through a plateau, or solve a real bottleneck. Here are a few patterns we’ve seen from the community, translated into what they’d actually look like inside a real operation:

A session-memory skill, so nothing gets re-explained by Hans van Gent

He built /reflect — a skill that runs a three-phase review at the end of every Claude Code session, pulls out the durable facts and corrections, and writes them back into his config so the next session starts smarter instead of from zero.

=> Business translation: after every client call, audit, or campaign review, have Claude write back what changed into a shared brief — so the next person (or the next session) isn’t starting cold. Something like:

Summarise the decisions made and corrections given this session. Append anything worth treating as a standing rule to [shared doc]

You don’t need to build anything custom for this. It’s a standing instruction you type once — “at the end of every conversation, add a summary of what we decided to this document” — and Claude just does it from then on. No code, no developer required.

Overnight batch runs on your audit backlog by Christopher Duffy

He handed Fable 9 separate workstreams in a single evening — a knowledge-base audit, a CRM rebuild, and updates across dozens of his own skills — and it held all 9 without dropping the thread.

=> Business translation: most teams have a backlog of “should really get to this” audits — SEO, ad account structure, content, a competitor scan. Queue them as separate briefs and run them overnight instead of spacing them across a month of Tuesdays.

Automating the tool that has no API by Daniel

He needed to publish articles to Medium, which offers no public API. Fable 5 handled it anyway, via a Chrome extension running locally, driving the actual publish flow end to end.

=> Business translation: if a supplier portal, a legacy POS, or an old internal tool has no API, this is the workaround — Fable 5 (through Claude Code with browser tools) can watch the manual steps once and replicate them going forward. It’s the same trick behind pulling analytics out of platforms that were never built to share data.

You show it what you’d normally click through by hand, once, and it figures out how to repeat that on its own. This is more of a “get your IT person or us involved for an afternoon” task than something you’d DIY — but it’s worth knowing it’s possible before you assume a tool’s limitations are permanent.

Worth drawing the line, though. Browser automation is the right answer when there’s no API and the job is small. When the tool sits close enough to the money that a fragile workaround will eventually cost you an order, the fix isn’t a smarter script — it’s connecting the systems properly so the data moves without anyone clicking.

A standing assessment system instead of ad-hoc judgement calls by Rich Carr

He fed Fable 5 a multi-phase scope and had it hold that as the running spec, turning raw field data into scored records against a consistent rubric — with every correction becoming a standing rule rather than a one-off fix.

=> Business translation: this is a lead-scoring or supplier-scoring system that applies the same rubric every time, instead of whoever’s reviewing it that week making a slightly different call. No custom software needed — just write your rubric in plain English, hand over your raw data (a spreadsheet, form responses, call notes), and ask Claude to score every entry against it consistently. The consistency is the win, not the technology.

Support ticket root-cause mining

Point it at three to six months of support tickets and ask it to find the actual recurring cause behind your top complaint categories. Then ask it to draft the fix — a macro, a process change, a product tweak — for each one. Run it every 3-6 months and you’ve got a running record of what’s actually improving, what keeps resurfacing, and where the next bottleneck is quietly forming. Fable 5 earns its premium when you want it to run multiple passes on its own — cluster the patterns, then re-check each cluster against the raw tickets, then draft fixes — without its own categorisation drifting along the way.

Once you know the three issues generating a third of your tickets, the next move is stopping them reaching a person at all. That’s the job AI customer service does well — the repeat questions answered instantly, day or night, and everything else routed to someone who can actually help.

How to Use Claude Fable 5 Without Burning Your Whole Week

Two things worth knowing before you point it at anything important:

It burns usage fast: Anthropic itself calls it token-intensive by design, and multiple users have reported blowing through a meaningful chunk of a weekly cap in a single ambitious session. Scope the task before you start, not after.

The new safety classifiers are still over-tuned: Fable 5 automatically hands certain requests to Opus 4.8 when its filters trigger — cybersecurity, biology, chemistry-adjacent topics mostly. Anthropic says this affects under 5% of sessions; some users report it firing on ordinary technical work too. If a routine request suddenly feels different, that’s likely why — rephrase rather than argue with it.

Scoping the work before you start is most of the skill here, and it’s the same skill whether the job goes to a model or a person. If you’d rather not spend a week’s usage cap learning that the hard way, tell us what’s slowing you down — we’ll pinpoint the fastest-payback quick wins, and tell you honestly which of them need a model this expensive and which don’t.

Anthropic’s most capable model to date, Claude Fable 5 launched June 2026. Unlike previous releases, it’s designed to handle long, autonomous work without hand-holding – think multi-hour tasks, not just better chat.

Every few months, a new AI model drops and the internet goes into a frenzy. Usually it’s developers sharing things that are genuinely impressive but hard to connect to the reality of running a business or managing a team.

Right now that model is Claude Fable 5, and the hype is real. But so is the confusion.

So rather than tell you it’s the best thing ever, we want to share what we’re actually thinking about it – the opportunities, the complications, and what might be worth doing right now if you’re a manager or decision-maker who uses Claude in any part of your work.

What actually just happened?

Anthropic released two models simultaneously: Claude Fable 5 (available to everyone) and Claude Mythos 5 (restricted to select government and security partners through a program called Project Glasswing).

Here’s the thing most articles skip over: they’re the same underlying model. The only real difference is which restrictions are active. Fable 5 is Mythos 5 with safety guardrails on. Mythos 5 is for vetted institutions where some of those guardrails are lifted.

Where does Fable 5 sit in the lineup? Think of it as a new tier sitting above Opus. The Claude hierarchy now runs Haiku → Sonnet → Opus → Fable. Fable is the new ceiling for regular business users.

What does that actually mean in practice?

Less “slightly better at writing emails” and more “can handle a complex, multi-step project autonomously for hours — and check its own work along the way.” Stripe reportedly used it to complete a codebase migration in a single day that their team estimated would take two months by hand. An independent developer built and shipped an entire software library release in one day — work he estimated would normally take several days.

That’s not a marginal improvement. That’s a different category of usefulness – for the right kind of work. More on that below.

What Claude Fable 5 actually costs

This is the part that decides whether Fable 5 is worth it for your team.

Fable 5 isn’t included in every Claude plan the way Opus is. On Max plans, and on premium seats on Team and Enterprise plans, it’s a standard part of the plan – you can put up to half your weekly usage limit through Fable 5 at no extra cost. On Pro plans, and on standard Team and Enterprise seats, it isn’t included in your plan’s limits at all: it runs on pay-as-you-go usage credits you buy on top of your subscription. Through the API it’s billed at standard rates – $10 per million input tokens and $50 per million output tokens, roughly double what Opus costs.

The practical read: test before you budget. Run a narrow slice of your team’s real work through Fable 5 and see whether the output is genuinely better before you either hand over half a weekly usage limit or start buying credits. For most teams the honest answer will be that it earns its price on a handful of jobs and is overkill for the rest.

One thing worth noting on usage speed: Early users have reported Fable 5 burns through usage limits faster than previous models. This is something we’ve seen with every major Claude release – more capable models are more compute-intensive, which means they use more of your allocated usage per task. It does make sense given how much more reasoning the model does. Anthropic has signalled they’re working to improve this over time, but for now it’s worth factoring in if you’re on a plan with a weekly usage cap.

The part that might actually frustrate your team

This is something Anthropic is transparent about, but worth explaining clearly because it affects day-to-day usability.

Fable 5 doesn’t always respond as Fable 5.

Because the underlying model is exceptionally capable in areas like cybersecurity and biological research, every request runs through a layer of safety classifiers. When a request touches certain topics — cybersecurity, biology, chemistry — the system automatically routes the query to Opus 4.8 instead. You get told this is happening, but you can’t override it.

Even though Anthropic says this affects fewer than 5% of sessions on average, early user reports in the first 48 hours included some surprising examples – prompts about pulled pork shopping lists, basic biology questions, and even asking about the filters themselves apparently triggered a downgrade to Opus. That said, Anthropic designed the classifiers to be deliberately over-tuned at launch, with plans to reduce false positives over time

There’s one piece of good news here: you won’t be charged Fable prices for requests that get rerouted to Opus 4.8. So at least the fallback won’t cost you extra.

Where Fable 5 is actually worth it?

Fable 5’s edge isn’t in short, single-turn tasks. If your team is using Claude to draft emails, summarise documents, or answer quick questions, Opus 4.8 handles those perfectly well. The premium isn’t worth it for that.

Where Fable 5 is genuinely different: work that runs long, requires holding a lot of context, involves checking its own outputs, or needs to coordinate across multiple steps without hand-holding.

Anthropic describes it as built for “days-long, complex, and asynchronous tasks previous models couldn’t sustain” – running in agent harnesses, planning across stages, delegating to sub-agents, and checking its own work. That’s the real differentiator.

Here’s how that shows up across different roles:

Marketing managers and brand teams

Running a full campaign brief that requires synthesising customer research, competitive analysis, and performance data from multiple sources, then producing a structured, reviewable output in a single session. Fable 5 can carry start to finish while flagging its own uncertainties along the way.

Finance and operations leaders

Working through multi-stage scenario analysis where each step informs the next – reasoning through the implications, checking internal consistency, and producing a board-ready output. Early testing found it scored highest of any model on Hebbia’s Finance Benchmark for senior-level reasoning, with double-digit gains in document reasoning, chart and table interpretation.

Legal and compliance teams

Reviewing a stack of contracts or regulatory documents and producing a structured risk summary – reasoning about what it means and flagging inconsistencies across documents. In blind review, lawyers found its redlines matched or beat their existing model every time.

Project and operations managers

Handing off a complex brief – say, restructuring a supplier agreement or building an operational process document – and getting back a draft that’s genuinely ready to review rather than a starting point that needs significant rework. The model proactively fills in gaps rather than stopping to ask about them.

Retail and ecommerce teams

Post-campaign analysis that requires pulling together performance data, customer feedback signals, and market context then producing a clear “what worked, what didn’t, what next” synthesis. Particularly useful where the analysis needs to span multiple channels and data types in one coherent output.

Property and infrastructure teams

Tender or proposal preparation that requires synthesising project specs, compliance requirements, cost estimates, and precedent documents into a structured submission-ready document. The model’s ability to maintain coherence across a long, multi-part document is where the upgrade shows up.

The common thread: the more moving parts, the longer the task needs to run, and the more the output needs to be self-consistent — the more Fable 5’s improvements actually matter.

In most of those examples the model is the easy part. The value shows up when it’s wired into the systems the work already lives in – the CRM, the ERP, the document store – so the output lands where someone can act on it. That wiring is the workflow automation work we do every week.

The bigger shift worth watching

Something worth naming beyond just this model release.

For the first time, a frontier AI capability has been formally split into two versions – a public version with restrictions, and a restricted version for trusted institutions. Governments, approved security firms, and select research organisations have access to capabilities that are deliberately unavailable to everyone else.

This might be the right call. The arguments for it are serious and worth respecting. But it does mean AI advantage is starting to become partly a function of your relationship with the AI provider, not just your willingness to pay or your technical capability.

For most businesses today, this is background context. But it’s a pattern worth watching.

What to actually do about it?

Run your real workflows, not demo prompts. Pick the 10-20 tasks your team actually does in Claude every week and run them through Fable 5. Note what’s better, what falls back to Opus, and form a real view before committing. If picking those 10-20 tasks is itself the hard part, that’s a process-mapping exercise more than an AI one, and it’s where our process automation consulting work usually starts.

The model is genuinely impressive for the right kind of work. The rollout has some real rough edges. And there’s more to figure out about how businesses will actually use it once the dust settles.

We’re still working through that ourselves. If you’re doing the same, we’d be happy to think through it with you – we spend our days turning this kind of capability into systems that actually move revenue, and we’ll happily start with 20 hours of free work on a workflow you pick.

Common questions