Start with the work that repeats
In short
Hand AI first the work that comes back every day in your customers' own words and follows rules you can write down, where a person can still take the cases that need judgment.
For many small businesses that work is the phone: the same questions about opening times and bookings, asked again every day, often while everyone is busy with a customer. The questions people type into a website at night are the same kind of work, and so is paperwork that arrives the same way each time, such as supplier invoices or order forms.
A job makes a poor first choice when a mistake would be costly and nobody would see it, such as anything that moves money, or when the answer needs a license, such as medical or legal advice. Those stay with people. We do not offer a BAA today, so no AI job of ours is built where patients' health details would reach it.
Start with one job, give it a few weeks of real work, and read what it did before you add the next. Each job is priced on its own, so the second one can wait until the first one runs the way you want.
The order we would build the nine jobs in
In short
The phone and the website chat come first, then the paperwork, then the jobs that wait on more groundwork: a texting registration, recorded calls, records in one place, or consent records and a lawyer-settled script for the calls you place.
The receptionist and the website chat wait on no texting registration. The receptionist needs a number to answer and written rules for each kind of call, and the chat answers from the pages already on your site; as with every job, your lawyer reviews their wording and settings before launch. Paperwork comes next, starting with one kind of document read into one system, and a person still sends every reply.
Follow-up texts wait on your texting registration, and call review needs calls your phone system already records with consent. The team assistant needs your records in one system and a playbook written down, and the night shift needs the systems it works through and a list of jobs you approve.
Calls placed to your customers come late, because they need the most in place: a record that each person agreed to the calls, and a script your lawyer has settled before the first live call. AI on your software comes last, when a tool you already pay for lets other programs in, or as part of a custom app.
| What it needs before it starts | How the written plan prices it | |
|---|---|---|
| AI receptionist | A phone number and your rules for each kind of call | A setup price, then receptionist care each month |
| AI website chat | The pages already on your website | A build price, then a care plan each month |
| AI paperwork and inbox | One kind of document and the system it goes into | A build price, then the ops retainer each month |
| AI follow-up by text and email | A texting number registered in your name, and its approval | A build price, then the ops retainer each month |
| AI call review | Calls your phone system already records with consent, and a checklist you approve | A build price, then the ops retainer each month |
| AI team assistant | Your records in one system and a playbook written down | A build price, then the ops retainer each month |
| Night shift and morning brief | The systems it works through and a list of jobs you approve | A build price, then the ops retainer each month |
| AI outbound calls | Contacts marked as opted in, and a script your lawyer has settled | A build price, then receptionist care each month |
| AI on your software | A tool that lets other programs in, confirmed in the written plan | Part of a custom app's build price, then the app support retainer |
Swipe sideways to see every column
A worked example (hypothetical)
In short
A print shop that misses calls while it runs jobs could start with the receptionist and the website chat, and leave texts for later, once its texting registration is approved.
Picture a print shop in Van Nuys with three people at the counter. Customers call to ask whether a job is ready or what a run of flyers costs, often while the press is running. At night the same questions about file formats come in through the website, and orders arrive by email with the artwork attached.
The shop could start with the receptionist, which runs on monthly care after its setup, to answer the calls the counter cannot reach and email the shop a summary after each one. The website chat, which runs on a care plan after launch, could answer the file questions from the shop's own pages.
Order emails could go to the paperwork job once the counter is sure what it wants read into its order system, and texts saying a job is ready would wait for the shop's texting registration. Each step would be priced on its own in the written plan.
What this means for a small business
In short
Start with the one job that takes the most of your day and follows rules you can write down, and add the next once it runs the way you want.
Before you choose, note a week of the work you are thinking of handing over: how many calls or messages came in, what each one wanted and who handled it. That list shows which job repeats most and which ones need a person every time.
Our AI plan puts that order in writing for your business: the jobs worth building first at your one location and what to ask your lawyer, as a map of where AI fits the whole business. Its fee comes off the price of the build it recommends, as long as you sign for that build within 60 days of the plan's delivery.