Skip to content
Sheet 17 · How We CompareCentennial, CO
How We Compare · October 2026

Who can actually run AI for your business?

There are six common ways to put AI to work in a small business. Here's what the research says about how these projects go, and what each option actually gives you.

What The Research Says

Most AI projects stall. Who builds it matters.

How often AI projects succeed

MIT studied hundreds of company AI projects. In-house builds succeeded about a third as often as projects bought from specialists.

How often AI-written code failed security checks

Veracode tested more than 100 AI models on 80 coding tasks. Bigger models did no better.

What an in-house hire costs

Median U.S. software developer pay is $135,980. Benefits make up about 30% of what employers spend on pay, which adds roughly $58,277.

97%

Of organizations whose AI was breached, 97% had no proper access controls on it.

40%+

Gartner expects over 40% of AI agent projects to be canceled by 2027, citing cost, unclear value, and weak risk controls.

Six Ways To Do It

What each option actually gives you.

Swipe to see all six.

BrewTech + Swirls

BrewTech runs it; Swirls powers it

  • Yes
    Works with your tools
    BrewTech already manages your systems; Swirls connects to hundreds of apps
  • Yes
    Ties your tools together
    One system across your apps, built in Swirls
  • Yes
    Asks before it acts
    Important actions wait for your approval
  • Yes
    You own it
    Written down plainly in Swirls and yours to keep
  • Yes
    Maintained for you
    BrewTech monitors and maintains it

Built-in IT software AI

AI inside tools like Syncro, HaloPSA, SuperOps

  • Partly
    Works with your tools
    Only sees data inside that one product
  • No
    Ties your tools together
    Can't reach your other apps
  • Yes
    Asks before it acts
    Good approval controls
  • No
    You own it
    Lives inside the vendor's product
  • Partly
    Maintained for you
    The vendor maintains the software, not your setup

DIY AI assistants

ChatGPT, Claude and similar, set up yourself

  • Partly
    Works with your tools
    Connects to many apps, one person at a time
  • Partly
    Ties your tools together
    Links apps inside a single chat
  • Partly
    Asks before it acts
    Asks before acting, inside the chat
  • No
    You own it
    Chats and prompts, not a system
  • No
    Maintained for you
    You maintain it yourself

AI consultants

One-off custom builds

  • Partly
    Works with your tools
    Has to be given access first
  • Yes
    Ties your tools together
    Custom builds can link apps
  • Partly
    Asks before it acts
    Depends on who you hire
  • Yes
    You own it
    You usually get the code
  • No
    Maintained for you
    Often gone after the project

Automation apps

Zapier, n8n and similar

  • Yes
    Works with your tools
    Thousands of app connections
  • Yes
    Ties your tools together
    Linking apps is what they do best
  • No
    Asks before it acts
    Few built-in approval steps
  • Partly
    You own it
    Yours, but setups get hard to follow
  • No
    Maintained for you
    You set up and fix it yourself

In-house AI hire

An employee building systems with AI chatbots

  • Partly
    Works with your tools
    Has access, but connecting systems is learned on the job
  • Partly
    Ties your tools together
    Possible, but often fragile, chatbot-written code
  • No
    Asks before it acts
    Approvals and audit trails are rarely built in
  • Partly
    You own it
    Yours, but it lives in one person's head
  • Partly
    Maintained for you
    Stops when that person is out or leaves

Yes, Partly, and No are our assessment of each option as it's usually delivered today.

What About Hiring Someone?

Same story as in-house IT. Higher stakes.

Plenty of businesses hand AI to one employee and a chatbot. The chatbot will happily write the code. It won't tell you what it missed about your data, your security, or what breaks six months from now.

One in-house hire
  • About $194,000 a year in salary and benefits for one person learning on the job
  • Data, security, and compliance figured out as they go
  • Chatbot-written code that nobody else reviews
  • No backup when they're out sick, on vacation, or gone
  • When they leave, the know-how leaves with them
BrewTech + Swirls
  • A team that builds and runs these systems every day
  • Security and data handling are part of the build from day one
  • Every system is written down plainly in Swirls and reviewed
  • Monitored and maintained, by people who already know your IT
  • You own what we build, whoever is on your payroll

Your in-house people still matter. They know the business best. We work with them, so they spend their time on the work, not on keeping the systems running.

See what it would look like for your business.

Bring one process that eats your team's time. We'll tell you honestly which of these options fits it best, even if it isn't us.

Charts and figures come from published research. The Yes, Partly, and No ratings are BrewTech's assessment, based on public product information and our own client projects. BrewTech builds and runs every system on Swirls. Think we got something wrong? Tell us.