For owners who would rather buy a role than a feature list

AI Workers on a Monthly Fee: The Menu, the Scope and the Limits

Most AI is sold as capability: it can read email, it can answer calls, it can update a spreadsheet. That is useless to a business owner, because capability is not a job. A worker is a job. It has a name, a written scope, a set of systems it touches, a list of things it will never do, and a person who is accountable for its output. That is what this page prices.

Every worker below is named after the task, never after a profession. There is no AI Bookkeeper here and there never will be, because that title invites a customer to assume a standard of care the software cannot hold, and because the moment the work crosses into BAS services for a fee it needs a registered agent, not software. Intake, Quote Chaser, Debtor Follow-Up, After-Hours Switchboard, Booking Desk and Reporting Clerk are all tasks, and each of them has a one page scope you sign before anything is built.

Book a Worker Scoping Call (03) 9003 0111

Realistic ROI

1 page

Is the right length for a worker scope

What it does, what it never does, what it connects to, who it escalates to and how you switch it off. If it needs ten pages, the worker is doing two jobs.

2 to 6 weeks

From signed scope to a worker in production

The build is rarely the long pole. Access to the systems it needs and agreement on the escalation rules usually are.

One monthly fee

Per worker, set after scoping

Not per seat, not per action, not per minute of thinking time. You should be able to forecast the line item twelve months out.

2 to 3 workers

Is a sensible first year, not six

Each worker changes a real process and someone has to absorb that change. Buying the whole menu at once is how programmes stall.

Why a Named Worker Beats a Feature List

Four reasons buying a role works better than buying an automation platform, and one reason it can still go wrong.

A written scope is the product

The thing you are actually buying is a document that says exactly what the worker does, in what order, using which systems, and what it hands to a human instead of attempting. Without it you are buying a demo and a hope. With it, you can hold us to a standard, your team knows what to expect on Monday morning, and a disagreement six months in gets settled by reading a page rather than by relitigating what was said on a call. If a supplier will not write the scope down before you pay, that tells you something.

Name the task, never the profession

We will not sell you an AI Bookkeeper, an AI Solicitor or an AI Nurse. Some of those titles are regulated outright: a nurse is registered with AHPRA, a solicitor is admitted to practise. Others become regulated the moment the work crosses a line, which is the more interesting case. A general bookkeeper in Australia needs no licence at all, but providing BAS services for a fee requires a registered agent, and no software qualifies. Either way the title invites a customer or a regulator to assume a standard of care that is not there. Debtor Follow-Up is honest: it chases a list of overdue invoices using words you approved. It does not decide whether a debt is disputed, whether to write it off, or whether a payment plan is reasonable. That distinction is the whole point.

A human stays accountable for money and law

Any action with a financial or legal consequence needs a named person who owns it. Workers can draft the invoice, prepare the reminder, assemble the report, prepare the refund and queue the escalation. A person releases the payment, signs the document, approves the credit and answers the complaint. This is not timidity, it is how you keep the audit trail defensible and how you keep your insurer, your accountant and your board comfortable with what you have deployed.

Roles compose, platforms sprawl

The failure mode of general automation platforms is that after a year nobody can say what is running, why, or who owns the broken bit. Named workers resist that because each one is a bounded thing with an owner and a scope. When you add the fourth worker you are adding a fourth named role to an org chart, not another forty steps to an unlabelled flow. That is also what makes it easy to cancel one worker without destabilising the rest, which is a test worth applying before you sign anything.

The Worker Menu

Six named workers. Each entry states what it does, what it never does, and what it has to be connected to before it is worth anything.

Qualified enquiry in your system

Intake

Takes every inbound enquiry from web forms, email and messaging, works out what the person actually wants, asks the two or three questions your team always has to ask anyway, and writes a complete, structured record into your CRM or job system. Never does: quote a price, promise a date, or accept work outside your service area. Connects to: your website forms, a shared inbox, and the CRM or job management system that already holds your customers. Without that last connection it just makes tidier email, which is not worth a monthly fee.

Follow-ups sent, replies routed

Quote Chaser

Watches quotes that have been sent and not answered, follows them up on a schedule you set, in wording you approved, and stops the moment a human replies or the job is marked won or lost. Never does: discount, renegotiate, change a scope, or chase a customer who has asked to be left alone. Connects to: wherever quotes actually live, which for most Australian trades and service businesses is a job management system rather than a CRM. This is usually the highest return worker on the menu, because most businesses already write good quotes and simply stop chasing them after the second attempt.

Reminders sent, exceptions escalated

Debtor Follow-Up

Works the aged receivables list, sends the polite reminder, the firmer one and the final notice on your ladder, records every contact against the invoice, and hands anything unusual straight to a person. Never does: threaten legal action, agree a payment plan, apply a credit, decide a debt is disputed, or contact a customer flagged as in hardship. Connects to: your accounting system, and ideally your inbox so replies are seen. Australian debt collection is regulated and reputation sensitive, so the escalation rules on this worker matter more than the automation does.

Calls answered, urgent ones passed on

After-Hours Switchboard

Answers the phone when the office is closed, identifies the caller and the reason, deals with the routine ones, and gets genuine emergencies to a human immediately by the path you nominate. Never does: give clinical, legal or safety advice, take payment card details, or decide that something is not an emergency when the caller says it is. Connects to: your phone number, your on-call roster and your job or booking system. It should always tell callers plainly that they are speaking to an automated assistant, and it should hand over the moment someone asks for a person.

Appointments made, changed, confirmed

Booking Desk

Takes booking requests across phone, web and messaging, offers only genuinely available times, books them, sends the confirmation, handles reschedules and cancellations and works the reminder sequence. Never does: double book, override a clinician or tradesperson blocking out time, waive a cancellation fee, or book a service the customer is not eligible for. Connects to: the real calendar or practice system, live, not a copy. A booking worker on stale availability is worse than no booking worker, because it creates confident wrong answers.

The same numbers, same time, every week

Reporting Clerk

Pulls the handful of numbers you actually run the business on from the systems that hold them, assembles the same report on the same schedule, flags what moved and by how much, and sends it to the people who need it. Never does: interpret the numbers as advice, change a figure it cannot reconcile, or quietly drop a data source that stopped responding. Connects to: your accounting system, your job or CRM system and whatever else holds a number on the list. Its most valuable behaviour is telling you when a source is missing rather than publishing a report that looks complete and is not.

What Actually Changes, Worker by Worker

Task	Traditional	Named worker	Notes
A web enquiry arrives at 9pm	Sits in an inbox until morning	Intake qualifies it and creates the record	Speed to first response is the single most measurable thing in inbound sales. Overnight enquiries are where it is usually lost.
Quote sent, no reply	Chased once, then forgotten	Quote Chaser works the full sequence	Most businesses have a written follow-up cadence and do not run it. Consistency is the gain, not cleverness.
Invoice 45 days overdue	Chased when cash gets tight	Debtor Follow-Up chases on schedule	Regular, unemotional and early beats sporadic and heated. The escalation rules keep it inside the regulated lines.
Phone rings after 6pm	Voicemail, or the owner answers at dinner	After-Hours Switchboard triages	The value is not answering everything, it is correctly identifying the one call in twenty that must wake somebody.
Customer wants to reschedule	Phone tag across two days	Booking Desk moves it in one exchange	Reschedules are more admin work than new bookings in most service businesses, and they are the easier win.
Monday numbers	Someone rebuilds a spreadsheet	Reporting Clerk sends the same pack	The consistency is what makes trends visible. Hand-built reports quietly change definition month to month.
Something goes wrong	Nobody is sure which automation did it	One named worker, one named owner	This is the real argument for roles over platforms. Ownership survives staff turnover.
You want to stop	Untangling a year of interconnected flows	Cancel that worker, the rest keep running	Ask any supplier what switching off looks like before you switch anything on.

Where a Monthly AI Worker Goes Wrong

The scope is vague, so the worker expands

A worker described as "handles customer enquiries" will drift into quoting, promising dates and making commitments, because that is what enquiries turn into. Every scope needs an explicit never list, and the never list should be the part you argue about hardest during scoping. If a supplier is relaxed about the never list, they have not thought about what happens the first time the worker is confidently wrong in front of a customer.

Nobody owns the worker internally

A worker without a named internal owner degrades within a quarter. Someone has to read the escalation queue, notice that the wording is out of date after a price change, and say when a rule is no longer right. That person needs perhaps thirty minutes a week, but they need to exist and to know it is their job. Programmes that fail almost never fail technically, they fail because the owner left and nobody inherited the role.

It is connected to a copy rather than the live system

A booking worker on a synced copy of the calendar, or a debtor worker on a nightly export of the ledger, will eventually act on stale data and do it with complete confidence. That is worse than not acting at all, because the customer receives a specific wrong answer. Insist on live reads for anything that makes a commitment, and if live access genuinely is not possible, narrow the worker to drafting rather than acting.

Money or legal actions were quietly automated

The line to hold is that a human approves anything that moves money, creates a legal obligation or makes a representation about safety, health or compliance. It is tempting to cross it once volumes rise, because the approvals feel like a bottleneck. Do not. The approval step is the reason your audit trail is defensible and the reason a mistake is a correction rather than an incident. Keep the queue small by narrowing what the worker attempts, not by removing the approval.

Buying six workers in the first month

Each worker changes a real process, and change has to be absorbed by real people who also have their normal jobs. Two workers, run properly for a quarter, teach you more about what to buy next than six workers half-configured. The natural sequence for most Australian small and mid sized businesses is one revenue worker and one admin worker first, then a decision at the end of the quarter based on what actually happened rather than what was projected.

The monthly fee has no ceiling on volume

Read what the fee covers. A worker priced per action, per minute or per interaction will surprise you the month you have a busy period, which is exactly the month you cannot afford a surprise. Ask what happens at double the volume, at ten times the volume, and what the practical cap is. A fixed monthly fee with a stated fair use band is honest. A fixed fee with no stated band is either generous or under-thought, and it is worth finding out which.

How Yes AI Supplies Workers

Scope written and signed before we build

One page per worker: the task, the never list, the systems, the escalation path, the owner and the off switch. You sign it before anything is built, and we hold ourselves to it. If we cannot describe the worker in a page, we tell you it is two workers or that it is not ready to be one.

Built, hosted and monitored by us

The workers run on a managed cloud environment we operate and watch, with logging on every action taken, alerting when a connection stops responding, and a monthly note on what the worker actually did. You do not run infrastructure and you do not keep a script alive on somebody’s desktop.

A human owner named on both sides

Every worker has an owner in your business and an owner in ours. The escalation queue goes to a person, not to a folder. When wording, pricing or process changes, there is a defined route to update the worker rather than a slow drift into being wrong.

Honest advice on which workers not to buy

If your quote volume is six a month, a Quote Chaser is a novelty and we will say so. If your debtors ledger is short and your customers are people you drink with, a Debtor Follow-Up worker may cost you more in relationship than it recovers. We would rather sell you one worker that earns its fee than four that make a nice diagram.

From Menu to a Worker in Production

Five steps. Most of the effort sits in the first two, which is the correct place for it.

Pick the tasks, not the tools

We walk your week and find the repeated, rule-shaped tasks that a named worker can hold. You end up with a shortlist ranked by the money or the hours attached, and an honest note against any that are not worth automating.

Write and sign the scope

One page per worker: what it does, what it never does, which systems it touches, who it escalates to, who owns it and how you turn it off. Nothing is built until you have read the never list and agreed with it.

Connect the systems properly

Live access to the calendar, ledger, job system or CRM the worker needs, with permissions scoped to only what the task requires. Where live access is not possible we narrow the worker to drafting rather than pretending the copy is current.

Run it shadowed for two weeks

The worker prepares its output and a person reviews everything before it goes out. You see exactly how it behaves on your real traffic, including the awkward cases, and we tune the wording and the escalation thresholds before anyone external is affected.

Release, monitor, then consider the next one

The worker goes live within its scope, monitoring and logging are on, and you get a monthly note of what it did and what it escalated. The decision about a second worker is made at the end of the quarter on evidence.

FAQ

What does an AI worker actually cost per month in Australia?

The honest answer is that it depends on how many systems the worker has to touch and how much judgement sits in its escalation rules, and that we set the monthly fee after a scoping conversation rather than from a rate card. What we can tell you is the shape: one fixed monthly fee per worker, covering the hosting, the monitoring, the wording updates and the human on our side who owns it, with a stated fair use band so a busy month does not become a surprise invoice. Where a piece of design work is needed first, that sits on our consulting ladder at $1,000 for a basic scope, $3,000 for a standard one and $10,000 for a strategic engagement across multiple functions. Book a call and you will leave it with a number rather than a range.

Why will you not sell an AI Bookkeeper or an AI Solicitor?

Partly because some of those titles are regulated outright. A nurse is registered with AHPRA and a solicitor is admitted to practise, so borrowing the title implies professional judgement, insurance and duties to third parties that software holds none of. Bookkeeper is the one worth being precise about: a general bookkeeper in Australia needs no registration, but the moment the work becomes BAS services provided for a fee it requires a registered BAS agent, and software cannot be one. Either way, naming a worker after a profession invites a customer, a court or a regulator to assume a standard of care that is not present, and it quietly transfers risk to you as the buyer. Naming it after the task is both more honest and more useful: Debtor Follow-Up tells you precisely what happens, which is that overdue invoices get chased in wording you approved. It also makes the never list obvious, because everyone can see the gap between chasing an invoice and deciding whether a debt is disputed.

What happens when the worker gets something wrong?

It will, occasionally, in the same way a new staff member does. The design questions are how fast you find out and how contained the damage is. Every worker logs what it did, escalates anything outside its scope to a named person rather than guessing, and holds back from any action that moves money or creates a legal obligation. During the first two weeks it runs shadowed, meaning a human reviews everything before it goes out, so the first errors happen where nobody external sees them. After go live you get an escalation queue and a monthly note, and the fix for a recurring mistake is a scope change we make, not a bill you receive.

Can a worker be turned off, and what breaks if we do?

Yes, and this is worth testing before you buy. Each worker is a bounded thing with its own connections and its own scope, so cancelling one does not destabilise the others. What you lose is the task getting done, which means the process it was covering has to go back to a person, so the practical answer is to give a fortnight’s notice so the handover is planned rather than abrupt. We will also hand back the written scope, the wording and the escalation rules, because those describe your process and belong to you regardless of who runs the automation.

Do we need to replace our existing systems first?

Almost never. Workers are designed to sit on top of the job management, accounting, calendar and CRM systems you already run, and a worker that requires you to replatform first is a project pretending to be a subscription. What does matter is that the system holding the truth can be read live and, where the worker needs to write, written to with properly scoped permissions. Older on premise systems can usually still be reached, though sometimes only through a file or database level connection, and occasionally the honest answer is that a particular worker should draft rather than act until that connection exists.

How many workers should we start with?

Two, in most cases, and not more than three. Each worker changes a real process that real people are involved in, and that change has to be absorbed alongside everybody’s normal job. A sensible first pair is one worker attached to revenue, usually Intake or Quote Chaser, and one attached to admin load, usually Booking Desk or Reporting Clerk. Run them for a quarter, look at what actually happened rather than what was projected, and decide the next one from evidence. Buying the whole menu at once is the most common way these programmes stall, and it is an expensive way to learn a cheap lesson.

When is buying an AI worker the wrong decision?

When the volume is not there, when the process is not stable, or when the relationship matters more than the efficiency. If you send six quotes a month, a Quote Chaser is a toy. If your intake questions change every fortnight because the business is still finding its shape, you will spend more on scope changes than the worker saves. If your debtors are long-standing customers you know personally, an automated reminder sequence can cost you goodwill worth more than the days it shaves off collections. And if the honest requirement is a person who can think, judge and be accountable, hire the person. We will tell you that on the call rather than after the invoice.

Buy a Role, Not a Feature List

Book a call. We will walk your week, tell you which two workers are worth having and which ones are not, and write the scope before anybody builds anything. Call (03) 9003 0111 if you would rather talk it through first.