AI consultant, AI software firm, or do it yourself? How to choose

There are three ways to get AI into a business — hire someone to advise, hire someone to build, or do it in-house with off-the-shelf tools. Each is the right answer for some problems and an expensive mistake for others. Here's an honest comparison.

Share

There are three ways to bring AI into a business: do it yourself with off-the-shelf tools, hire an AI consultant to tell you what to do, or hire an AI software firm to build it. Do it yourself when a product already does the job. Hire advice when you don't yet know which problems are worth solving. Hire a builder when the work needs custom integration with your own systems. Plenty of businesses need all three at different stages, and the expensive mistakes come from using one where another was needed.

We should say up front that we're not neutral. Abrams & Luchanski advises, and Nexos, our technology division, builds. So this piece tries hard to describe the cases where you don't need us at all.

Should you hire an AI consultant?

Hire one when the question is "what should we do, and in what order?" and nobody inside the business owns it. Don't hire one when a product already does the job, or when the only reason to act is a fear of being left behind.

Signs it's worth paying for:

  • You have a dozen possible uses for AI and no way to rank them.
  • Leadership disagrees about where to start.
  • You need a policy for which data can go into which tools before anyone picks one.
  • You're about to spend real money and want someone independent to check the plan.

Signs it's a waste of money:

  • A product already exists for the task, and the job is setting it up, not deciding.
  • There's no named workflow, only a general sense that the business should "do something with AI".
  • Nobody will own the result. A plan with no owner inside the business doesn't get carried out.
  • Every answer ends at the adviser's own product. Then you're paying for a sales process.

What does each option actually give you?

The labels get used loosely, so here is what each one usually means in practice.

Do it yourself (DIY). You buy AI products off the shelf, such as a company AI assistant, AI features inside the software you already use, or a no-code automation tool, and your own people set them up and drive adoption. You pay in subscriptions and staff time.

AI consultant. Someone reviews your business and tells you where AI fits: a strategy, a roadmap, a vendor shortlist, a policy. The deliverable is usually a document or a set of recommendations. Building it is left to you or to someone else.

AI software firm. Someone designs, builds and integrates a system for you: a custom agent, an automation across your tools, a private model connected to your documents. The deliverable is working software. Its quality depends on whether they understood the problem before they started building.

How do they compare?

Do it yourselfAI consultantAI software firm
Best forCommon tasks a product already handlesDeciding what to do and in what orderWorkflows that need custom integration
What you getTools and your own team's learningRecommendations, roadmap, policyWorking, integrated software
Upfront costLowest: subscriptions plus staff timeModerate: advisory feesHighest: a scoped project
Speed to first resultFastest for simple tasksSlow to reach a working result, since advice isn't a systemWeeks per scoped project
Who owns the outcomeYouYou, since the consultant owns only the adviceShared: they own the build, you own adoption
Main riskTool sprawl, no integration, stalled adoptionA good report that never gets builtBuilding the wrong thing well
Knowledge left behindHigh, because your team learned itDepends on the handoffDepends on documentation and ownership terms

No column wins across the board, which is the point. The right choice depends on what the specific problem needs.

When should you do it yourself?

Before paying anyone, check whether you can do it yourself. DIY is the right call when:

  • A product already does the job. Drafting, summarising, meeting notes, searching your own files, first-pass research: mature products handle these, and many already sit inside software you pay for. Buying means someone else maintains it.
  • The data doesn't need custom plumbing. If the task lives inside one tool, there's nothing to integrate.
  • Someone owns adoption. The usual way DIY fails isn't the tool. It's that nobody is responsible for training people, writing the usage guidelines and checking whether anyone uses it.

The warning sign is tool sprawl: five AI subscriptions, none connected to each other, each used by two people, and data copied between them by hand. At that point you've recreated the problem you were trying to solve. We call it the copy-paste tax.

When is a consultant worth paying for?

Advice earns its fee when the question is "what should we do?" rather than "how do we build this?" The signs that it's worth paying for are listed above.

The main risk with pure advisory work is a good report that never gets built. A roadmap is only worth something if it's specific enough to act on: named workflows, what "done" means for each, rough cost and effort, and the order to do them in. If a consultant's output doesn't say which workflow to fix first and how you'll know it worked, it's a presentation, not a plan.

Also ask whether the advice is tied to the adviser's own products. A recommendation that always ends at the adviser's own platform is sales material, not independent advice.

Can you just ask ChatGPT instead of hiring a consultant?

For part of the job, yes. In our view an AI assistant is good for learning the vocabulary, understanding what kinds of tools exist and drafting the questions you'd put to an adviser. It's a cheap way to walk into that conversation prepared.

It can't do the part you'd be paying a consultant for. It can't see your workflows, your data or your systems, so its advice is only as good as your description of them. It isn't accountable if the recommendation turns out wrong. And it tends to accept the problem as you framed it, when the most useful thing an adviser does is often to tell you you've framed it wrong. If the question involves what data you can put into which tool, that's a decision in its own right; we compare the options in Private LLM vs. ChatGPT Business or Enterprise.

Use an assistant to prepare for the decision, not to make it.

What does an AI consultant cost, and how is it priced?

Advisory work is usually priced in one of three shapes:

  • A day or hourly rate. Flexible, but the total is open-ended, and nothing in the pricing pushes the work toward a conclusion.
  • A fixed-scope project. A set price for a defined deliverable, such as an assessment of named workflows or a roadmap. You know the cost before you start.
  • A retainer. A monthly fee for ongoing access. Useful once you know what you need help with; risky as a first step, because it can run on without producing anything you can act on.

Whatever the shape, ask for two things: a fixed price on a small first scope, so you can judge the work before committing to more, and a written deliverable you keep, so the plan is yours even if you never hire them again.

For our own figures, the free audit is a 30-minute call plus a written report, builds are scoped per project from $4,900, and ongoing support is optional.

When do you need a software firm?

You need someone who builds when the answer to "does a product already do this?" is no. Usually that's because:

  • The workflow runs across several of your systems (inbox, CRM, accounting, scheduling) and has to read from and write to each of them.
  • The task needs judgment on unstructured input, such as reading an email to work out what's being asked, and then acting on it in your tools.
  • It needs approval steps, audit trails, or rules about what the AI may do on its own.
  • Your data can't leave your control, so the model has to run privately.

The main risk here is building the wrong thing well: a technically good system aimed at a workflow that didn't need it, or one that a $40-a-month product would have handled. The defence is to scope before building. We cover that sorting in Buy, build, or automate.

Why do the categories blur?

In practice most useful engagements need both advice and implementation. The advice is only as good as its understanding of what can be built, and the build is only as good as its understanding of the business. That's why many firms, including us, now do both.

How to vet an AI consultant or AI firm before you pay

Whether you hire an adviser, a builder, or one team for both, check:

Our own model follows that shape. Every engagement can start with a free AI readiness audit, and its written report is yours to keep with no obligation to build with us. Our figures are in the pricing section above and on our pricing page. We describe how the audit runs, step by step, in The AI-readiness audit, step by step.

A quick way to decide

Take one problem at a time, not "our AI strategy", and ask:

  1. Does a product already solve this? If yes, do it yourself: buy it, set it up, own adoption.
  2. Do we know this is the right problem to solve first? If not, get advice before spending on a build.
  3. Does it need our systems connected, judgment on messy inputs, or private data handling? If yes, you need a builder, ideally one who scoped it with you first.

Many businesses end up using all three: DIY for the common tasks, advice to set priorities, and a build for the one or two workflows that justify it. The mistake is using one option for everything.

Not sure which one your problem needs? A free audit will tell you, even if the answer is to buy a product.

Request a free AI readiness audit from Nexos →

You can also see what the firm does or get in touch directly.

Common questions

Should I hire an AI consultant?

Hire one when the question is what to do and in what order, and nobody inside the business owns that question. Don't hire one when a product already does the job, or when the only reason is a fear of being left behind.

Should a small business hire an AI consultant or build AI itself?

If the need is a common task an off-the-shelf tool already handles, such as drafting, summarising or meeting notes, do it yourself and train the team. If you don't yet know which workflows are worth changing, get advice first. If the workflow needs custom integration with your systems or approval steps, you need someone who can build as well as advise.

What is the difference between an AI consultant and an AI software firm?

A consultant typically delivers recommendations — a strategy, a roadmap, a vendor shortlist — and leaves implementation to you or someone else. A software firm builds and integrates the system. Some firms do both; the thing to check is whether the people advising you are accountable for whether the recommendation actually works once built.

When is doing AI yourself the right choice?

When the tools you need already exist as products, your data doesn't need custom plumbing, and someone on the team has the time and interest to own adoption. Many first wins, such as a company-wide AI assistant with good usage guidelines, need no outside help at all.

Share

See what this looks like in your business.

Bring us the problem. We start with a conversation about how the work runs today, and come back with what we would change and what it would take to do it.

Discuss a project

New pieces, in your inbox

Occasional notes on operations, decisions, systems and AI — from the work. No spam, unsubscribe anytime.