The Playbook · TIMELINE
How long AI automation really takes, job by job
Most of the automations a small business asks for are live in an afternoon. The ones that talk to your own systems take a month, and the difference is almost never the code. Here are honest timelines by job, what makes each one stretch, and how to plan the next few months so something useful runs every one of them.
What runs in an afternoon?
The missed-call text-back. The review request that goes out after a job is marked done. Appointment reminders the day before. These are one trigger and one message, the pattern is the same in every trade, and the tools already exist. If you give me the logins at lunch, it is running by dinner.
What can slow even these down is access. If the phone system is on a contract nobody can find, the afternoon becomes a week of waiting on a support ticket.
What takes a week?
The follow-up sequence after a quote. An intake form that lands in your customer list with the right fields. Invoice reminders that stop when the invoice is paid. These have logic in them, and the logic depends on how you actually work, so the week is mostly conversation, not building.
Why the week is mostly you
I need your words for the messages, your rules for when to stop, and a real example of the messy case. The build takes hours. Getting those three things from a busy owner takes days, and that is fine, as long as you know it going in.
What takes a month?
Anything that has to read from or write to a system of yours: inventory, a booking engine, an accounting file that only opens on one computer, a legacy database. The edges are unknown until we are inside them. I will say that before we start rather than after.
Anything with a judgement call also lives here. A bot that answers hours is a week. A system that decides which complaints need a human today needs testing on real messages before it touches a customer, and testing takes calendar time.
What stretches every timeline?
Three things. Access, meaning logins and permissions that live with a former employee or a vendor. Decisions, meaning the message copy that sits in an inbox for nine days. And the process nobody wrote down, which shows up as the exception you find on day twelve. The step-by-step play explains the exception path that catches most of these.
How do you plan the next few months?
One automation a month, boring ones first. A single workflow automation is $3,500. Care after it is on the plans page at $149, $349, or $749 a month, watched by the person who built it. Twelve months of that is a back office that mostly runs itself, and the cost play shows what each month is actually paying for.
If you want the range before we talk, the estimator on the start page prices a build in six taps, and the person reading the answer is the same one who built the playable court on the homepage. Timelines here are the same ones I give myself.
What else do owners ask?
Can an automation be live the same day?
Yes, if it is one trigger and one message and I have the logins. The missed-call text-back and the review request are the usual same-day jobs.
Why does the build wait on me?
Because the messages should sound like you, the rules should match how you work, and the exception cases only you know about. A builder who does not wait on those ships something generic that you switch off in a month.
How long before it pays for itself?
Run the busywork calculator on the free tools page. It prices the hours the job costs you today. Most afternoon automations pay back inside the first month against that number, and the month-long ones are the ones you sanity-check before starting.
Your move. Call or text (847) 387-0244, or price your build in six taps and I call you with the exact number.
← All plays · Free tools: cost calculator, busywork calculator & site audit · Price my build
Your move