Skip to content

AI software or a managed service: who will do the work?

By Howling CRM Automation & AI Directory · Published · Updated

How to decide between AI software your team operates and a provider who implements or runs it, with a sample acceptance checklist.

The real question is ownership

Most AI buying decisions are framed as a choice between products. In practice the bigger choice is who will do the work: your own staff using a tool, or an outside provider who builds and possibly runs it for you. Both can work. They fail in different ways, so it helps to decide deliberately.

Software you operate is usually cheaper to start and gives you direct control, but someone on your team has to learn it, configure it, notice when it breaks and fix it. A consultant or managed service takes that burden off your staff, but you then depend on their availability, their documentation and the terms of your agreement.

Process ownership

Before comparing any vendor, write down the process you want to change: what triggers it, each step, who does it today and what a correct result looks like. If nobody can write that down, the first job is process design, not tool selection, and that is often where an implementer earns their fee.

Then name one person inside your business who owns the process after launch. That person does not need to be technical, but they must be able to say whether the result is right.

Maintenance is the hidden cost

Connected systems change. A field gets renamed, a password expires, a connected app updates its permissions, or an AI model behaves differently. Each of these can quietly stop a workflow. Ask every option the same questions:

  • Who receives an alert when a run fails, and within what time?
  • Who is allowed to change the configuration, and is there a record of changes?
  • What does maintenance cost per month, in money or in staff hours?

Integration work

The connection between systems is usually where projects slow down. Check that every system involved actually allows the access needed, on the plan you pay for. List each account the solution will connect to and what it will be allowed to read or change. Prefer connections made with accounts your business owns, so access can be removed without asking anyone.

What a real handoff looks like

If a provider builds something for you, the handoff should leave you able to keep it running or move it elsewhere. A real handoff includes:

  • Administrator access to every account, in your business's name.
  • Written documentation of what each workflow does and why.
  • A walkthrough with the person who will own the process.
  • A list of known limitations and things that will need periodic attention.

For an ongoing managed service, ask what you would receive if you ended the service: data exports, configurations, phone numbers, and how long the transition takes.

Verifying outputs

AI output can be fluent and wrong. Decide in advance how results will be checked: a person reviewing a sample each week, automatic checks that compare outputs against known values, or approval steps before anything reaches a customer. Whatever you choose, keep the checking with someone inside your business, not only with the provider who built the system. Frameworks such as the NIST AI Risk Management Framework describe this kind of ongoing measurement in more depth.

Sample acceptance checklist

Use or adapt this list before you approve a launch or a final invoice:

  • The process is written down, with a named internal owner.
  • The solution ran on at least 20 real cases and results were reviewed by that owner.
  • Failure alerts go to a named person, and a test failure was received.
  • Every connected account is owned by our business, with access listed.
  • We can remove the provider's access ourselves within one day.
  • Documentation is delivered and understood by the internal owner.
  • Monthly costs (subscriptions, usage, service fees) are written down.
  • We know what we keep, and how, if the service or tool is discontinued.

A simple way to choose

If you have a staff member with time and interest, and the process is simple, start with software and a small trial. If the process crosses several systems, matters to customers, or nobody has time to own it, a scoped engagement with a consultant or managed service is often the safer start, provided the handoff and exit terms above are in writing. In either case, judge the provider on evidence from your own process rather than on marketing claims.

Public sources

General information only, not legal, medical or compliance advice. Spotted an error? Request a correction.

Related listings