8 min Read

Choosing an AI Automation Provider: Expertise Over Influencers

How to tell a partner who has shipped production systems from one who has watched a lot of demos.

Nikhil Sharma
Choosing an AI Automation Provider: Expertise Over Influencers - Digital Solutions Ninja blog

Key takeaways

  • Ask what they have run in production for a year, not what they have built, because the gap between those two is where every real problem lives
  • A provider who cannot name a project they talked a client out of is selling, not advising
  • Demos are trivial to make impressive and tell you almost nothing about whether something survives a Tuesday
  • The integration and the failure handling are the work, so a proposal that is mostly about the model is a proposal to hand you a prototype

There is a lot of money moving into AI automation right now and very little agreement about what competence looks like. That combination reliably produces a market where confidence is cheap and results are not.

Here is how I would evaluate someone, including me.

Ask what has been running, not what has been built

Building an impressive AI demo is genuinely easy now. That is not a criticism of anyone, it is a statement about how good the tooling has become. A capable person can produce something that looks like magic in a weekend.

What remains hard is the same thing that has always been hard: something that runs for a year, handles the inputs nobody anticipated, degrades sensibly when a dependency fails, and does not require its author to be awake.

So the question is not what have you built. It is what have you had running in production for over a year, and what broke. The second half matters more than the first. Anyone who says nothing broke either has not run anything long enough or is not being straight with you.

Ask what they talked someone out of

A provider who has never advised a client not to build something is not advising. They are selling, and everything they tell you should be read in that light.

Good technical partners refuse work regularly, because a meaningful share of what gets requested is either solved by an existing product, better fixed as a process problem, or not yet worth the money. Someone who can tell you a specific story about that has judgment they are willing to apply against their own revenue.

Watch where the proposal spends its words

Read any proposal you receive and count what it is actually about.

If most of it concerns models, capabilities and what the AI can do, you are being sold a prototype. The model is the commodity layer. It is the part that will be better and cheaper in six months regardless of who you hire.

The work is everywhere else: what systems it has to reach, what happens when they are down, who reviews what, how errors surface, what the audit trail looks like, what it does when it does not know. A proposal that treats those as implementation detail has not thought about them, and you will meet all of them anyway.

The demo problem

Demos are run on chosen inputs by the person who built the thing. Every failure mode has been avoided by construction.

If you are being shown one, ask to type your own input. Ask what happens with a badly formatted request, an ambiguous one, or one in a second language. Ask what it does when the system it writes to is unavailable. The response to those questions is far more informative than the demo itself, because it tells you whether the person has thought past the happy path.

Price signals

Genuinely senior work in this market runs somewhere around $100 to $250 per hour. That is a wide band and it reflects real variation in scope and seniority.

Substantially below that, somebody is either junior, subcontracting to people you will never meet, or pricing to win the work and intending to make it back on change requests. Any of those can be fine if you know which it is. The problem is when the price implies a level of attention that the delivery cannot match.

Substantially above it, ask what you are getting for the premium. Sometimes the answer is good, such as deep domain knowledge or regulatory experience. Sometimes it is an account manager.

Certainty is the red flag

The clearest signal I know is a confident price given before anyone has scoped anything.

It feels like competence. It is usually the opposite: either a guess dressed up, or a template being sold regardless of whether it fits. In both cases the number is fiction and the reconciliation happens later, as change requests, at your expense.

The honest version is slower and less satisfying to hear. It sounds like: I do not know yet, here is what I would need to look at to find out, here is what that costs, and the plan is yours whether or not I build it. That is what an MVP Roadmap is, and you should expect something equivalent from anyone competent.

The short version

Hire the person who tells you what they do not know, has run something long enough to have scars, and can point at work they refused. That filter removes most of the market and almost all of the risk.

FAQ

Quick answers to the most common questions about this topic.

Ask what they have had running in production for over a year, and what broke in that time. Anyone can build a demo. The interesting information is in what happened at month eight, because that is when the edge cases, the model changes and the integration drift show up.

Often the reverse. Most of these projects are integration and workflow problems with a model in the middle. Someone who has spent a decade making systems talk to each other and has learned the AI part is usually a safer bet than someone whose entire career started with language models.

Expect $100 to $250 per hour for genuinely senior work in this market, and treat anything far below that as a signal to look harder at who is actually doing the work. On fixed scope, the honest path to a number is a paid scoping engagement rather than a quote from a description.

Ask who specifically will do the work and what happens if they leave. A large firm where you never meet the builders and a solo operator with no continuity plan are different versions of the same risk. What you want is named accountability plus a documented handover.

Certainty before scoping. If someone gives you a confident price and timeline from a conversation, they are either guessing or they have a template they intend to sell you regardless of fit. Both cost you more than the scoping would have.

Nikhil Sharma

Written by

Nikhil Sharma

Founder, DigiBenders

Twelve years shipping software, five of them leading a studio in New Brunswick. I build the software and run the marketing around it, which is an unusual combination and the reason most of my work arrives by referral. One person accountable, and everything ends up in your name.

You read the thinking

Now tell me what you are actually building.

If this was useful, the call usually is too. You describe the problem, I tell you what it takes and whether I am the right person for it.

Thirty minutes, no pitch

Honest read, including when the answer is no

Replies within one business day

Book a strategy call30 min

Keep reading

More from the same desk.

What you walk away with

One instrument. You own it.

Nothing held hostage, nothing locked to a platform you cannot leave.

The codebase

Yours, in your repository

The infrastructure

Your accounts, your billing

The accounts

Registrar, analytics, ads

The documentation

Written for the next person