Owners do not buy Claude, n8n or Zapier. Puru sorts what they actually pay for into four buckets: hours back, lower costs, more revenue, and an edge a rival can't easily copy. The request rarely arrives in those words. "Can you automate our customer service?" usually means staff answer the same questions all day (time). "We need better lead tracking" usually means leads are slipping away (revenue). Part of the work is translating the ask into the bucket, because an owner values plugging a customer leak far above saving an hour on a report.
The demand is real and mostly unmet. A Goldman Sachs 10,000 Small Businesses Voices survey of 1,256 owners was published March 17, 2026. It found 76% already use AI. Just 14% say it is fully built into their core operations. The software is already in the building. What is missing is someone who turns occasional use into a business that runs on it.
Puru splits people working in AI into three groups. Tourists collect tools and know each feature the day it ships, but have shipped nothing of value. Builders get something working for themselves, an inbox sorter or a report writer, that nobody pays for. Operators have put a system inside a real business that pays for the result and keeps running when they are not in the room.
His quick test: look at your last seven days. Count the hours spent learning or building, then count the messages you sent to business owners. If the second number is near zero, you are a tourist or a builder, however good your builds are. The five steps below are how you move to the third group.
He also ranks the work in five levels: running the tool, connecting systems, designing the fix, finding the real problem, and changing how the business runs. The tools are swallowing the bottom levels fast. The top two, finding the real leak and changing the operation around it, are where the money is moving.
Here's the reality. I've built, scaled, and sold three companies, generated over $85 million in the last seven years in my own companies. None of them won because of a tool. They won because someone understood exactly where the business leaked money and fixed that first. Puru's data points the same way.
| Evidence | Source |
|---|---|
| 76% of small businesses use AI; 14% have it fully built into core operations | Goldman Sachs 10,000 Small Businesses Voices, 1,256 owners, Mar 17, 2026 |
| Of about 360 owner requests to his agency, the top asks were follow-ups (152), weekly reports (127), inbox and phones (92) and client onboarding (91) | Nick Puru, Reprise's own inquiry data, as stated in the video |
| 68 of 192 teams on his growth plan form ticked "not sure yet, show me where AI helps most" | Same |
These are Puru's steps, in his order. He is clear that the order matters: each one sets up the next.
Choose one industry you can actually get a meeting in, such as property managers, accounting firms or clinics, and commit to it. Without prior experience, learning one industry properly can take a year or two: who answers the phone, how quotes are built, where jobs stall. That knowledge compounds, and nobody can copy it from a tutorial. Switching niches every month resets it to zero.
Walk in with a number, not a pitch. Good candidates are visible from the outside: whether anyone answers the phone after hours, or how long a quote takes to come back. Puru's favorite is the contact form test. Fill in the business's inquiry form like an ordinary customer and start a timer. If the reply takes five hours, you have found the problem, and the exact time is your opening line. A buyer who is shown their own leak listens differently from one who is offered a chatbot.
The answer to the problem rarely lives in the model, since every business can rent the same one. It lives in what the business knows: how it prices work, whose calls get returned first, how the owner handles an upset client. In most small firms that sits in two or three heads. Get it out with roughly one conversation per department head. Put everything in one folder of plain files: a rules file for how the work is done, a skill for each repeated task, and the list of apps the agent is allowed to touch. Puru keeps a CLAUDE.md and an AGENTS.md side by side saying the same thing, so any agent can work from the same folder.
Pick a daily task that touches money or time. Record the number before you start and again after go-live. Define success as a pass mark rather than a promise; his proposals state that the system must "sort at least 90% of a test set of emails correctly." Keep the first phase small enough that a nervous owner can say yes. In one of his examples, an owner worried about a 35-million-record database got a first phase that ran on a test copy for $7,000 instead of $22,000.
Now take the proven fix to the next firm of the same type and price it on what it changes, not on your hours. Hourly pricing punishes you for getting faster. Price against the cost the fix removes or the capacity it frees, and add a monthly retainer for keeping it running (he cites $500 to $1,500 monthly, sometimes more). We walk through both pricing methods with the full arithmetic in our post on value based pricing for AI automation. After five or ten repeats, the build that took weeks takes days, because you have seen the same patterns already.
A stranger will not hand you their whole business. Puru's tactics for lowering the risk on their side:
He is also honest about failure. One clinic agent started double booking appointments because a setting skipped the availability check. The fix was a real check before every booking plus a switch letting staff take over any chat. Learn the tool well enough to judge its work and see why it is wrong; that is the level of technical skill this path needs.
Here is how a new operator might run the five steps in one quarter.
rules.md (how new patients are greeted and booked), skills/ (insurance questions, reschedules) and connections.md (the booking calendar, the inbox, nothing else).Run a business rather than want to start one? We do these five steps on your side. We measure where leads and hours leak, write down how your team actually works, build one fix and report the before and after numbers. You approve the pass mark before anything is built and see the result before you commit to more, so you aren't paying for a build nobody uses. Why now: most of your competitors are still in the "we use it sometimes" stage.
| What you get | Where |
|---|---|
| A measured leak, a documented workflow, one fix with before and after numbers | AI automation |
One free, MIT-licensed skill for Claude, Codex and Grok comes with this guide: Operator Kit (checks whether your week is a tourist's, a builder's or an operator's; sorts owner requests into time, cost, revenue and edge; runs the contact form response time test and writes each opening line; prices a fix by cost and by capacity, plus the retainer; scores a build against its pass mark; and checks the business folder before you build). Download the skill (free zip)
No, but you need to understand the tool well enough to judge its output and spot why it went wrong. Puru is not a developer.
You fill in a business's website inquiry form as a normal customer would and time how long a reply takes. A slow reply is a measured problem you can bring to the first conversation.
Puru puts it at a year or two without prior experience. Staying in one niche is what makes that time count.
He advises against it. Price on the cost the fix removes or the capacity it frees, plus a monthly retainer for upkeep.
Whichever one lets you build and check your first fix. The step that matters is understanding one business, because the tools will keep changing.
Book a call and we'll find the one leak in your business that is worth fixing first.
Book a Search Strategy Call