No Developer Required. Except the One Nobody Mentioned.
Every vendor swears the AI tool plugs right in. Then you find out who wires it to the systems you already run.
The software shows up. You paid for it. The sales rep swore it needed no developer, that it connects to everything, that you'd be live by Friday. Three weeks later the login still opens onto an empty dashboard, because nothing you actually run is connected to it. The tool works fine. It just isn't wired to anything, and wiring it turns out to be a job.
The phrase to distrust is "integrates with." A vendor who brags that their tool integrates with 5,000 apps is telling you something specific, if you listen for it: that you will do the integrating. "Integrates with Zapier" means there's a door. It does not mean anyone walks you through it. Between that door and your real business, your booking calendar, your invoicing, your customer list that lives in three places and disagrees with itself, is a stretch of work nobody put on the quote.
I wire these systems up for a living. When I connect an automation for a small business, the AI part is usually the fastest part of the whole job. The slow part is that their leads live in a web form, their jobs live in a spreadsheet, their invoices live in QuickBooks, and their calendar lives in one guy's phone, and not one of those four things has ever spoken to any of the others. Making them talk is not prompting a robot. It's plumbing. It's API keys and webhooks and field mapping and the twelfth phone call to nail down which of the owner's three Gmail accounts the notifications should actually land in.
The demo skips all of it, because the demo runs on a clean account somebody already wired.
"No developer required" is true the same way "some assembly required" is true. Technically you don't need a developer. You need someone who can read a page with the word "webhook" on it without their eyes sliding off, who knows what OAuth is, who won't panic when a connection silently drops a field and half the records come through blank. If that person is you, congratulations, you're the developer now. If that person does not exist inside your five-person company, the tool sits in a browser tab, paid for and dark, while the monthly charge clears like clockwork.
And here's the part that keeps costing you after go-live: the wiring is not one-time. Every connection you set up is a connection that can break. The calendar app changes its login flow. QuickBooks retires the old endpoint. The form builder ships an update and the field names shift by a single character. When that happens the automation doesn't error politely and email you an apology. It just quietly stops moving data, and you find out when a customer asks why nobody ever called them back. The setup you paid a specialist to do has an expiration date, and nobody printed it on the invoice.
So before you sign anything, make the vendor answer one question in plain words. Who connects this to the tools I already run, is that included in the price or billed separately, and what happens the day one of those connections breaks? Then watch what they do. If they say "it integrates with everything," that's the tell, and the answer is you. If they say "our onboarding team handles it," ask how many hours, and whether that clock keeps running after you're live. If they say "you'll want a technical resource for that part," at least they're being honest, and now you can price the real thing, which is the software plus a human, not the software alone.
The honest version of the pitch is boring, and I'd trust it more for being boring. "This tool is good. Setting it up inside your specific mess takes somebody who knows what they're doing about a day, and it'll need a tune-up a couple times a year when the things it connects to change underneath it." Nobody says that, because it makes the sticker price look like the down payment it actually is.
Software that doesn't plug into anything isn't automation. It's a very expensive login screen. Ask who does the wiring before you find out it's you.