The honest answer is not the impressive thing you saw in a demo video. This article answers the question every owner eventually asks out loud: out of everything AI could do, which single process should I hand over first, and how do I keep it working after the model changes underneath me?
Suggested SEO meta title tag: What to Automate First With AI (Small Business Guide)
The Demo You Envy Is Not the One Making Money
Somebody in r/VibeCoding asked a question this week that I have not been able to shake.
"Why are 90% of showcased projects here slop?"
Eighty-five upvotes. One hundred forty-six comments. An entire community of builders standing in a circle, admitting out loud that most of what they show each other is impressive for eleven seconds and useless on Tuesday.
Here is the direct answer to the question in the headline. Automate the unglamorous recurring process you run every single week, the one with a clear start, a clear finish, and a clear definition of "done." Not the flashiest thing AI can do. The most repetitive thing you do. That is where the measurable return lives, and the research backs it hard.
I spent years believing the opposite. I chased the shiny build. I have a graveyard of half-finished automations that were technically remarkable and commercially worthless.
Meanwhile, one subreddit over from all that slop, somebody posted a workflow that classifies incoming contracts and tracks renewal dates through n8n, Google Drive, and Google Sheets. No fireworks. Nobody is putting that on a highlight reel.
That person is going to make money.
On Product Hunt the same day, the top AI launches were Lightfield, an AI-native CRM built for sales teams tired of manual data entry, and Tines, a governed environment for running agents without sprawl. Data entry nobody wants to do. Guardrails nobody wants to build. That is what is winning.
Candidly, this is very good news for you. You do not need to out-build a twenty-three-year-old with a GPU cluster. You need to look honestly at your own calendar and find the two hours you burn every week on something with a name, a pattern, and no strategic value whatsoever.
That is the thesis: the demo economy is losing to the boring automation economy, and the boring automation economy is one you can actually compete in.
Key Takeaways
- The best first automation is the process you already run on a repeating schedule, not the most technically impressive thing AI can do.
- Research consistently shows AI delivers the largest measured gains on narrow, well-defined, repetitive tasks and the smallest gains on open-ended judgment work.
- Most AI initiatives fail on approach and workflow integration, not on model quality, which means small businesses are not at the disadvantage they assume.
- An automation without a checkpoint is a liability, because model behavior demonstrably changes over time even when your prompt does not.
- You should measure one number before you automate and the same number after, or you have built a hobby instead of a system.
The Problem: Everyone Is Optimizing for the Wrong Audience
Here is the thing about AI demos. They are built to impress other builders, not to serve customers.
I know this because I did it. I built things because they were hard, and I showed them to people who understood why they were hard. It felt like progress. It was applause.
The trap is subtle and it catches smart people. A demo rewards novelty. A business rewards repetition. Those pull in opposite directions, and nobody tells you until you have spent four months on something nobody asked for.
Small business owners get caught in a second version of the same trap. You watch a founder on LinkedIn show an agent that "runs their entire company," and you conclude that AI is either magic you cannot access or nonsense you should ignore. Both conclusions are wrong, and both cost you money.
The real difficulty is not technical. It is selection.
Picking what to automate first is hard because the obvious candidates are the wrong ones. The thing that annoys you most usually requires the most judgment. The thing that takes the longest usually varies the most. The thing your competitor is bragging about is usually the thing they built for the bragging.
There is a third problem, quieter and more expensive. Even when you pick the right process and build it well, it can stop working. Not break. Stop working. The model gets updated, the outputs drift, and three weeks later you notice your categorization has been wrong the whole time.
Somebody in r/PromptEngineering asked exactly that this week: "How do you catch a prompt that quietly got worse after a model update?" That is not a beginner question. That is somebody who has already been burned.
Michael Hyatt spent a live training this week teaching seven ways AI systems break, hosted by Molly Mahoney. Seven. That is a curriculum, not a warning label.
So the challenge is two challenges stacked. Choose correctly. Then build the thing that tells you when your correct choice stopped being correct.
The Evidence: Narrow and Repetitive Beats Broad and Impressive
I do not want you to take my word for any of this. Here are five findings, all named, all checkable.
1. Most enterprise AI pilots produce nothing measurable. MIT's Project NANDA published "The GenAI Divide: State of AI in Business," based on 52 executive interviews, surveys of 153 leaders, and analysis of 300 public AI deployments. Roughly 95 percent of enterprise generative AI pilots delivered no measurable impact on profit and loss. The report is explicit that this gap was not driven by model quality or regulation. It was driven by approach. Generic tools that demo beautifully turned out to be brittle inside real workflows.
Read that again, because it is the most encouraging sentence in this article. The companies failing have more money than you. They are failing on selection and integration, which are exactly the two things a small operator can do better.
2. When the task is narrow, the gains are enormous. Erik Brynjolfsson, Danielle Li, and Lindsey Raymond studied 5,179 customer support agents in a field experiment published as NBER Working Paper 31161, "Generative AI at Work." Agents with an AI assistant resolved 14 percent more issues per hour on average. Novice and lower-skilled agents improved by 34 percent. Highly experienced agents barely moved.
The pattern matters more than the number. The largest gains landed on a repetitive, well-defined task performed by people who had not yet memorized the pattern.
3. The same pattern shows up in a randomized controlled trial. GitHub ran a controlled experiment where developers built an HTTP server. The group using Copilot finished 55.8 percent faster, averaging 71 minutes against 161 minutes for the control group. Bounded task. Clear finish line. Enormous gain.
4. Push past the boundary and the gains invert. Boston Consulting Group and Harvard's Digital Data Design Institute studied 758 BCG consultants in the research now known as the "jagged frontier" study. Consultants using AI completed 12.2 percent more tasks, 25.1 percent faster, with meaningfully higher quality scores. But on tasks outside AI's capability, those same consultants were 19 percentage points more likely to produce an incorrect answer than colleagues working without it.
Inside the frontier, AI makes you faster. Outside it, AI makes you confidently wrong.
5. Your automation will drift, and this is documented. Lingjiao Chen, Matei Zaharia, and James Zou at Stanford and UC Berkeley published "How Is ChatGPT's Behavior Changing Over Time?" comparing March and June 2023 versions of the same models. On identifying prime versus composite numbers, GPT-4 scored 84 percent in March and 51 percent in June. Same service. Same prompt. Different behavior.
Two more numbers worth holding. McKinsey's State of AI global survey found 88 percent of organizations now use AI in at least one business function, while only 39 percent report any enterprise-level impact on earnings. And Gartner, after polling more than 3,400 organizations, predicts over 40 percent of agentic AI projects will be canceled by the end of 2027, citing escalating costs, unclear business value, and inadequate risk controls.
Adoption is nearly universal. Value is not. The difference is what you chose and whether you checked on it.
The Solution: The Boring Loop
Here is what changed for me.
I stopped asking "what impressive thing could AI do for my business" and started asking "what do I do every week that a competent assistant could do if I wrote down exactly how I do it."
That second question is boring. It is also the entire job.
Andrew Ng published his AI Engineering Skills Map this month in The Batch, built from more than 10,000 job postings plus structured interviews with hiring managers and recruiters. Four skills made the list: building and deploying AI applications, software engineering fundamentals, using coding agents, and shaping the build.
Prompting is not on it.
Look at what those four describe. Deploying, not prototyping. Fundamentals, not tricks. Orchestrating agents, not talking to a chatbot. Shaping a build, which is judgment applied to a system you do not fully control. Every one is execution. Not one is ideation. Ng, working from ten thousand real job postings, landed exactly where that guy with the n8n contract pipeline landed on his own.
Credit where it belongs. That framing sharpened for me reading Ng's letter, and Dan Shipper of Every has been circling the same idea with his argument to stop doing tasks and start tending loops.
Tending loops. That is the phrase.
So here is the framework I use, and I call it the Boring Loop because I want you to remember what it is not.
A process qualifies for your first automation if it passes four tests. It repeats on a schedule you can name. It has a defined output you could show someone and get a yes or no on. It has low variance, meaning the inputs look mostly the same every time. And it costs you real hours you can count.
If a process fails any one of those, it is not your first automation. It might be your fourth.
My own proof case is unglamorous to the point of being embarrassing. Every week I review what the major AI companies shipped, what the top threads in a dozen subreddits said, what a set of specific influencers published, and what launched on Product Hunt. It used to eat most of a morning. It repeats weekly, produces a defined artifact, barely varies in structure, and cost me hours I could count.
It now runs as a chained process with a human review step I do not skip, and I get a briefing instead of a morning of tabs.
Nothing about it would make a good demo video. It is the highest return thing I built all year.
The tools are ordinary and that is the point. n8n or Make for chaining steps. Google Drive and Google Sheets as the backbone almost every small business already has. Claude or ChatGPT for classification and drafting inside a step. Tines if you reach the stage where governance stops being optional.
And one non-negotiable addition: the checkpoint.
Practical Steps: Build One Loop This Week
-
Track your week before you automate anything. For five business days, write down every task you repeat, how long it took, and whether the output was the same shape every time. Do it in a plain Google Sheet. You cannot select correctly from memory, because memory over-weights the tasks that annoyed you and under-weights the ones that quietly consumed your morning.
-
Score every candidate against the four tests. Scheduled, defined output, low variance, countable hours. Give each one a yes or no. Take the process with four yeses and the highest hour count. If nothing scores four, take the highest scorer and narrow the scope until it does.
-
Write the process down as a human would run it, step by step. Before you touch a tool, document the actual sequence including the judgment calls you make without noticing. This is the step everyone skips and it is the step that determines whether the automation works. If you cannot write it down, you cannot automate it.
-
Have AI turn your notes into a build plan. Paste your written process into Claude or ChatGPT with this prompt:
[The Job]
Turn my written description of a recurring business process into a step-by-step automation plan.
This is for: [YOUR ROLE] at a [SIZE] [INDUSTRY] business with no technical staff.
It matters because: this process currently costs me [NUMBER] hours every [WEEK/MONTH] and I need those hours back.[The Background]
Here is what you need to know: my full written process is pasted below. The tools I already pay for are [LIST YOUR TOOLS]. The person who will run and monitor this is [WHO]. The output has to be accurate enough that [WHO CONSUMES IT] can act on it without rechecking.
Do not use: tools I do not already have, anything requiring custom code, or any step I cannot verify with my own eyes in under five minutes.[The Deliverable]
Return: a numbered build plan of no more than 10 steps, plus a short table listing every step, the tool it uses, and the specific way that step could silently fail.
Must include: one clearly marked human review checkpoint, and a plain-language description of what "correct output" looks like.
Optimize for: reliability over cleverness.[The Questions]
Ask me any questions you have. -
Build the smallest version and run it beside the manual process. For two weeks, let the automation run and keep doing the task yourself. Compare outputs. This feels wasteful and it is the cheapest insurance you will ever buy, because it surfaces failure modes while the stakes are zero.
-
Install the drift checkpoint. Keep five to ten real historical inputs where you already know the correct answer. Once a month, and every time you hear a model was updated, run those inputs through again and compare. That is your entire early warning system, and it takes about ten minutes.
-
Write down the before and after number. Hours per week before. Hours per week after. If you cannot state both, you did not automate a process, you adopted a tool. Only when that number is real do you move to the second loop.
Frequently Asked Questions
What is the best first process for a small business to automate with AI?
The one you repeat on a schedule with a consistent output and low variance. For most small businesses that is lead intake and routing, invoice follow-up, meeting notes to CRM entry, contract and renewal tracking, or weekly reporting. Pick based on hours you can count, not on how interesting the task is.
How do I know if a task is too complex to automate?
Check the variance. If the inputs look different every time, or if you make a judgment call that depends on context outside the document in front of you, it is too complex for a first build. The BCG and Harvard research found that pushing AI past its capability boundary made users significantly more likely to be wrong.
How much does it cost to automate one business process?
Usually far less than owners expect, because the backbone is tools you already pay for. A typical first loop runs on your existing Google Workspace, a workflow tool like n8n or Make, and one AI subscription. The larger cost is your time documenting the process correctly before you build anything.
How often should I check an AI automation that is already working?
Monthly at minimum, and immediately after any model update. Stanford and Berkeley researchers documented GPT-4 accuracy on one task dropping from 84 percent to 51 percent between two versions of the same service. Keep a small set of test inputs with known correct answers and rerun them on that schedule.
Should I use AI agents or simple automation for my first project?
Start with simple, deterministic automation and add AI only inside the steps that genuinely require language understanding. Gartner, polling over 3,400 organizations, predicts more than 40 percent of agentic AI projects will be canceled by the end of 2027 on cost and unclear value. Complexity is a cost, not a feature.
The Close: Nobody Is Going to Applaud This
Go back to that r/VibeCoding thread for a second. One hundred forty-six people, arguing about why the impressive stuff is slop.
They are all looking at each other. That is the mistake.
Here is what I want you to hear, as plainly as I know how. The thing that will actually change your business is sitting in your calendar right now, and it is so unremarkable you have never once considered it worth attention. It is the report you rebuild every Monday. The renewals you track in your head until one slips. The intake email you rewrite forty times a month with three words changed.
Nobody will be impressed when you automate it. There is no post in it. No launch. No applause.
And it will pay you every week for years.
I have learned most things the expensive way, including some seasons I would not choose again, and the most useful lesson from all of it is this: the work that compounds is almost never the work that gets noticed. It is the work you do on schedule when nobody is watching, and check on after everybody has moved to the next shiny thing.
So do the unglamorous thing. Write down one process this week. Score it against the four tests. Build the smallest version. Put a checkpoint on it so it keeps working after the model shifts under you, because it will.
The demo economy is loud and it is losing. The boring automation economy is quiet and it is paying.
Go get quiet and get paid.
Want the build sessions, not the highlight reel? Our Express AI Training is $10 live or $20 for the replay, and it is two focused hours. The Challenge AI Training is $97 live or $147 for the replay across three days. If you want ongoing help choosing and building these loops with people doing the same work, AI Insiders is $247 per month. Come build something boring with us.
About the Author
Jonathan Mast is the founder of White Beard Strategies, where he teaches entrepreneurs, coaches, and consultants how to use AI in ways that survive contact with a real business. He leads a Facebook community of more than 500,000 members, runs the AI Insiders membership, and speaks regularly on practical AI adoption for small business owners. He is open about the parts of his story that were not a highlight reel, including prison and bankruptcy, because he thinks people learn more from the recovery than the resume. He genuinely enjoys building automations nobody will ever see, and considers a Monday morning that runs itself the closest thing to a standing ovation he needs.
