Do I Need an AI Consultant? 8 Signs It's Time to Get Help

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Do I Need an AI Consultant? 8 Signs It's Time to Get Help.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Do I Need an AI Consultant? 8 Signs It's Time to Get Help.

You probably don't need an AI consultant to get staff using ChatGPT, Claude, Copilot or Gemini well: a business plan, a one-page policy and a two-week trial will do it. Help starts to pay once AI must connect to customer data or other systems, a pilot has stalled, or you're about to commit several thousand dollars.

The eight signs below each come with a test you can run this week. If two or more apply, that's the point where a few hours of outside help is worth pricing; if none apply, put the money into seats and staff time instead. The signs that you don't need a consultant yet matter just as much, so they're here too.

Follow me on Instagram@sagnikteaches

What you can do alone before paying anyone

The first stage of AI adoption is mostly organisation. An owner who spends a few hours a week for a month can usually get here without outside help:

Connect on LinkedInSagnik Bhattacharya
  1. Move everyone onto company accounts on one business plan (an afternoon). This puts your data under business terms and lets you remove access when someone leaves.
  2. Write a one-page usage policy (one to two hours): which kinds of information may go into the tool, and which outputs a person must check before they leave the building.
  3. Pick three repetitive tasks and time them (a week of noting it down). Quotes, client emails and meeting notes are common choices.
  4. Run a two-week trial on those tasks with the AI included in your office suite, or a few paid seats.
  5. Compare the timings and the quality. Did it save time on real work, and would you have sent the output?
  6. Keep what worked and save the prompts that produced it in a shared document.

Step 5 is where most owners go vague, so write the comparison down. Here is an illustrative two-week log from the front desk of a three-optometrist opticians:

Subscribe on YouTube@codingliquids
TaskTimes doneMinutes each, beforeMinutes each, with AISent without major edits?
Replies to frame and lens enquiries466241 of 46
Recall letters for overdue eye tests3 batches4515All three, after checking the dates
Notes from the monthly staff meeting14010Yes, one wrong name fixed

The sum: enquiries saved 46 × 4 minutes, about three hours, recalls another 1.5 hours and the meeting 30 minutes, so roughly five hours in a fortnight, or ten a month, for two seats. That clears the cost of the seats several times over, and none of it needed outside help. The five enquiry replies that did need rewriting all quoted a lens price, which tells you the next thing to fix: add the current price list to the project the assistant works from, rather than paying anyone.

The fuller version is in the first seven steps for getting started with AI. If that process works, you may never need a consultant for chat assistants. The signs below are about what comes after.

Eight signs it's time to get help

1. AI would need to read or write records in your other systems

The test: the job you want to automate touches two or more apps (say, your inbox, your CRM and your accounts package), or it would send something to a customer without a person checking it first.

A chat window fails loudly: you see the bad answer. A connected automation can fail quietly, filing the wrong enquiries or sending the wrong template for weeks before anyone notices. Connecting systems also raises questions a chat tool never does: which account the automation runs under, what it's allowed to change, and who gets alerted when it breaks. What help looks like: someone who designs the flow, sets the permissions, builds in error alerts and hands it over with instructions.

How a quiet failure shows up, in an illustrative landscaping firm: an automation reads each web-form enquiry, adds it to the CRM and emails a matching price guide based on the "Project type" field. Someone tidies the form and renames that field to "What do you need?". The automation can no longer find a project type, falls back to its first template, and sends the patio price guide to every enquiry for three weeks, including 40 people asking about hedges and lawns. Nobody notices until a customer replies, puzzled. A built-in check ("if the project type is blank, stop and email the office") would have caught it on the first enquiry.

2. You're paying for seats that nobody uses

The test: 60 days after buying, fewer than half the paid seats are used in a typical week. Check the usage report in your plan's admin console.

Low use rarely means the tool is bad. More often, nobody has shown each role where AI fits its own tasks, so people tried it twice on something unsuitable and gave up. What help looks like: a task-by-task map for each role, a handful of tested prompts per role, and cancelling the seats that still aren't earning their place.

Put a price on it. Twelve Microsoft 365 Copilot Business seats on annual billing cost $21 each, $252 a month. If the Copilot usage report in the Microsoft 365 admin centre shows five active users over the last 28 days, seven seats are idle: $147 a month, or $1,764 a year. A role map for the office manager in that business might read "supplier emails: draft replies in Outlook; month-end: summarise the aged-debt spreadsheet in Excel; meetings: Teams recap for the weekly ops call". Three specific jobs per role, each with a saved prompt, is usually what turns a trial seat into a used one.

3. A pilot has stalled for more than six weeks

The test: it worked in the demo, it half-works on real work, and nobody has made a go or no-go decision in six weeks.

Stalled pilots usually have one of a few causes: no success measure agreed at the start, messy input data, or no owner with time to fix the edge cases. Why AI pilots stall, and how to get them live goes through each. What help looks like: an outside review that ends with a decision (fix, narrow the scope, or stop) rather than more tinkering.

Most of the rescue is rewriting the pilot's definition. Here is a before and after for an illustrative joinery workshop:

BEFORE
"Try AI on our quotes and see how it goes."

AFTER
Scope:     AI drafts every kitchen and wardrobe quote under
           $15,000 from the site-visit notes. Staircases stay
           manual.
Success:   20 quotes checked; each needs under 10 minutes of
           editing; zero pricing errors.
Owner:     the workshop manager, 2 hours a week.
Decision:  go / narrow / stop at the review on week 4.

The "before" version can never fail, so it never finishes. The "after" version gives a date on which someone has to say yes or no.

4. You have a long list of ideas and no order

The test: you or your team have listed more than ten things AI could do, and none of them has hours saved, cost or risk written next to it.

A long list without numbers leads to starting with the most exciting idea rather than the most valuable one. What help looks like: scoring each idea on hours saved per month, how often the task happens, what goes wrong if the AI gets it wrong, and how hard it is to build, then choosing one to do first.

Here is what four ideas from an illustrative wedding venue's list look like once they have numbers against them:

IdeaHours a monthHow oftenIf AI gets it wrongEffort to set up
First reply to enquiry emails, with availability and package prices18DailyMedium: a wrong date or price, caught if a person approves each replyLow
Weekly social posts from event photos5WeeklyLowLow
Allergen summaries for the catering menu2MonthlyHigh: a guest's safetyLow
Automatic seating-plan builder3Per eventLowHigh

The seating planner was the idea everyone liked most. The enquiry replies win by a distance: most hours, lowest effort, and a risk a human approval step handles. Allergens stay manual, however easy they'd be to automate.

5. You're about to sign something you can't judge

The test: you're looking at a quote, proposal or annual contract worth more than a few thousand dollars, or two quotes for what sounds like the same job differ by more than double, and you can't say why.

Price differences that large often mean the quotes describe different jobs: one includes testing, error handling and training; the other doesn't. How to evaluate an AI implementation proposal gives you a checklist to run first. What help looks like: an independent read of the proposals by someone who isn't the one selling the build.

Consider an illustrative craft-supplies wholesaler with two quotes to automate purchase orders from supplier emails. Quote A is $3,500 for "set-up of the AI purchase-order workflow". Quote B is $9,000 and lists two weeks of running alongside the manual process, an alert when a supplier email can't be read, a written guide, a handover session and 30 days of fixes. They sound like one job but aren't. The useful question to put to the cheaper firm is "Which of the items in the other quote are included in yours, and what would the rest cost?" Sometimes the answer closes most of the gap; sometimes it shows the cheaper quote stops the day the workflow first runs.

6. Staff are already using AI on their own accounts

The test: ask the team anonymously: "Have you used an AI tool for work in the last month, and on which account?" If personal accounts come back, and any of them involved client or staff information, the sign applies.

This is common and it isn't a disciplinary matter; it means people found the tools useful before the business provided safe ones. What to do about shadow AI covers the conversation. What help looks like: choosing the approved tool quickly, setting it up with the right settings, and writing a policy people will actually follow.

A typical result, for illustration, from an eleven-person bookkeeping firm: seven people used AI for work in the past month, five on free personal accounts, and two had pasted client material in, one of them a payroll export with names and salaries, to "tidy up the columns". The model-training setting on that account was still on. Nobody had done anything malicious, but the firm now had client data on an account it didn't control and couldn't delete. The fix took a week: two business-plan seats for the heaviest users, a rule that client files go only into the business account, and a two-line note to the rest of the team about switching off training on any personal account they keep for their own use.

7. AI would influence decisions about people

The test: the AI would screen job applicants, affect credit or payment terms for individuals, set prices for specific customers, or handle health information.

These are the uses where bias and errors do real harm; how AI bias shows up in hiring, pricing and credit explains the mechanisms. If you sell to customers in the EU, the EU AI Act also applies: transparency duties for chatbots remain in force, and the high-risk obligations that cover some hiring and credit-scoring uses have been deferred to 2 December 2027 for stand-alone systems. What help looks like: someone to design human checks into the process, plus a solicitor for the legal questions. A consultant is not a substitute for legal advice.

How bias sneaks in without anyone intending it: an illustrative 15-person garden centre pastes 80 applications for a shop-floor supervisor into a chat assistant with the prompt "rank these by suitability". The top ten all have unbroken employment histories. Two strong candidates with gaps for childcare and caring for a parent sit near the bottom, and nothing in the job needed an unbroken history. The redesigned process asks the AI only to summarise each application against five written criteria, has a person make every shortlisting decision, and has a second person read a sample of the rejected pile.

8. You're the bottleneck

The test: you're the only person who understands the tools, and you can't find three to four hours a week for the next two months to drive the work.

AI projects in small firms often stall when the one person pushing them gets busy. What help looks like: someone to run the first project alongside a named person in your team, so that person owns it when the outside help leaves.

Picture an illustrative family bakery with two shops and a wholesale round supplying a dozen cafés. The owner starts at 4am, and the plan to have AI turn the cafés' WhatsApp and email orders into a daily bake sheet has sat half-built since spring. The owner still has the know-how; what's missing is time. The shape that works is a named person (here, the shop manager who already takes the orders) given two protected hours a week, with the outside help building alongside them rather than instead of them. When the help leaves, the person who takes the orders also knows how the bake sheet is made.

Signs you don't need a consultant yet

Paying for help too early wastes money as surely as paying too late. Hold off if:

  • The process isn't written down, and three people do it three different ways. Agree how the task should be done first; automating a muddle makes the muddle faster.
  • The task takes less than two hours a week in total. The saving won't cover design and build time. A better prompt or template will do. Run the sum for an illustrative florist who spends 90 minutes a week chasing unpaid invoices: even if automation removed all of it, at $30 an hour that's $45 a week. A $1,500 build takes 33 weeks to pay back before any fixes or subscription costs, while three saved reminder emails and a Friday calendar slot get most of the saving for nothing.
  • Nobody inside will own it after launch. Someone can build it for you; they can't care about it on a busy Tuesday six months later.
  • You want AI done to the business without anyone changing how they work. Every useful AI change alters someone's daily routine. If that's off the table, the project will stall whatever it costs.
  • The real need is something else. Laptops, accounts and security are IT support. New custom software is a developer. Contracts and compliance are a solicitor. Whether AI belongs with your IT support company or a consultant helps you tell which you need.

Score yourself: a decision rule

Count the signs from the eight above that clearly apply, then find your row.

Signs that applyWhat I'd do
0 or 1Do it yourself with the six steps above. Revisit this list in three months.
2 or 3Get a single session or short review to rank your options and choose the first job, then do most of the work yourself.
4 or more, or sign 1 with customer dataScope a project with someone who will build, test and hand over. Insist on a fixed scope and written acceptance criteria (what "working" means, and how it will be measured).
Sign 7, at any scoreAdd a solicitor or data-protection adviser before anything goes live.

If you land in the middle row and would rather work it through with someone, that's what my AI implementation consultation is for: finding the jobs where AI pays off, working out how to automate them or add AI to the tools you already use, and leaving you with something your team can run.

How the rule plays out in three businesses

These are illustrations, not client stories.

Say a sole-trader interior designer uses ChatGPT Plus to draft client emails, proposals and supplier queries. None of the eight signs apply; at a stretch, sign 4, because there's a list of ideas. Score: 0 or 1. The right move is to check the model-training setting on the account, keep client identifiers out of prompts, save the five prompts that work best, and spend nothing on outside help.

Say an eight-person physiotherapy clinic wants AI to answer booking enquiries out of hours and draft summaries of treatment notes. Sign 1 applies (the inbox and the booking system), sign 7 applies (health information), and sign 8 applies because the practice owner is fully booked with patients. Score: 3, but sign 1 with patient data puts it in the project row, and sign 7 adds an adviser. The clinic needs someone to build and test the enquiry flow, plus data-protection advice before any patient information goes near an AI tool. A sensible order is booking enquiries first, notes later, once the adviser has signed off.

Say a 25-person courier and logistics firm bought Copilot seats in the spring. Half are idle (sign 2), an automation that turns emailed delivery requests into bookings "almost works" after two months (sign 3), there's a whiteboard of ideas with no numbers (sign 4), and two firms have quoted for the next phase at very different prices (sign 5). Score: 4. Before signing either quote, the business needs an independent view of what each one includes, then a scoped project with a named internal owner.

If you do get help, make sure you come away with these

Whoever you hire, and whatever it costs, the engagement should leave you with:

  1. A ranked list of jobs, with estimated hours saved, and the first one chosen and justified.
  2. A fixed scope with acceptance criteria, so you both know when the work is done.
  3. Everything built in your own accounts, not the consultant's, so it keeps running if the relationship ends.
  4. Documentation and a handover session attended by the person in your team who will own it.
  5. A clear statement of any commissions or referral fees on the tools recommended to you.

Test item 4 before the final invoice is paid. In the week after the outside help steps back, ask your internal owner to make one real change unaided: add a new service to the enquiry-reply template, change who gets the error alert, or pause the automation over a public holiday and restart it. If they can do it from the written guide in under half an hour, the handover worked. If they have to message the consultant, the guide is missing a step, and adding it should be part of the job you've already paid for. In an illustrative accountancy practice, that test showed the guide never said which login owned the automation, so only the consultant could open it; one paragraph and a change of account owner fixed it.

Bring your own homework too: the task timings from your trial, a list of the software you already pay for, and three real examples of the work you want help with. An adviser who has those in front of them can give you specific answers in the first hour instead of general ones.

Further reads

Two or more of these signs sound familiar?

On a 1:1 call we'll go through the signs that apply to you, pick the one job where AI would pay off first, and decide whether you can do it yourself or need something built.

Book a 1:1 call with me