Do I Need AI in My Business? A Decision Guide for Owners

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Do I Need AI in My Business? A Decision Guide for Owners.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Do I Need AI in My Business? A Decision Guide for Owners.

Not necessarily. You need AI if your staff each spend more than about five hours a week on repeatable writing, reading or data entry, if slow replies are costing you work, or if you can't hire fast enough to meet demand. If none of those is true, one approved business chat tool and a short usage policy are enough for now.

"Need" is doing a lot of work in that question. Few small businesses will fail next year for lack of AI; plenty will waste money buying it for the wrong reasons. The ten-question score further down gives you a defensible answer in about ten minutes, and the 30-day test at the end settles it with your own numbers rather than someone's sales pitch.

Follow me on Instagram@sagnikteaches

Three situations where the answer is yes

1. Repeatable text or data work above a threshold. The thresholds I'd use are about five hours per person per week, or 20 hours across the team, on the same kind of task: drafting similar emails and letters, summarising documents, keying figures from PDFs into systems, or answering the same customer questions. Below that level there are still gains, but they're small enough to pick up casually with a chat assistant; they don't justify a project.

Connect on LinkedInSagnik Bhattacharya

2. Speed decides who wins the work. If prospects contact three firms and pick the first sensible reply, or clients judge you on turnaround, faster drafting changes revenue, not just workload. Look at last month's new enquiries: if your typical first reply took longer than half a working day, and you know you've lost work to quicker firms, you have a speed problem AI can help with.

Subscribe on YouTube@codingliquids

In a kitchen-fitting firm, for instance, that check might turn up something like this (illustrative figures): 31 enquiries last month, first replies ranging from 40 minutes to three days, and a median of about 20 working hours, because quotes wait until the owner is off site in the evening. Nine enquiries went quiet, and when the owner rang round, four said they'd gone with someone who got back sooner. That pattern is a genuine yes-signal. If the lost jobs had mentioned price or fitting dates instead, faster drafting wouldn't have won them back.

3. Demand exceeds capacity and hiring is slow. If you're turning work away or the team is on regular overtime, AI that takes over admin can add capacity before you recruit, and it's worth checking before you advertise a role. Deciding between AI and a new hire walks through that comparison.

The check is to list what the new hire would actually do. An illustrative dog-grooming salon planning a 15-hour-a-week admin role wrote it out: about six hours answering booking messages, four sending appointment reminders and chasing no-shows, three on stock orders and two on social posts. The reminders didn't need AI at all; the booking software could send them automatically once someone switched the feature on. AI-drafted replies trimmed the message time to about three and a half hours, and first drafts of posts halved that job. That freed roughly eight hours, leaving a seven-hour role. The salon still hired, but for half the hours it had planned.

When waiting is the sensible answer

  • Most of the work is physical, face to face or on site, and admin is under a couple of hours a week per person.
  • Volume is tiny. A business with a handful of clients and a few emails a day gains little from automation.
  • The process itself is a mess. If three people do the same task three different ways, AI will copy the confusion faster. Why automating a broken process backfires explains what to fix first.
  • A system change is due soon. If you're replacing your practice or CRM software in the next few months, wait and see what AI the new system includes.
  • The work is high-stakes judgement at low volume, where every AI output would need full expert review anyway, so the saving mostly disappears.

Reasons that feel like need but aren't

Some pressures push owners into buying AI without any of the three situations above being true. Each deserves a pause.

A vendor demo. Demos use clean data and a task chosen to look impressive. Ask to see the product run on one of your own documents, with your own messy formatting, before you conclude anything. Consider an illustrative dental laboratory shown a tool that read typed prescription PDFs flawlessly. The lab's real prescriptions arrive as scanned forms with handwritten tooth numbers and shade notes. On ten of those, the same tool misread a tooth number on three and a shade on two, which in a lab means remaking a crown. The demo had answered a question the lab never asked.

A competitor's announcement. "Now powered by AI" on a rival's website tells you about their marketing, not their margins. What matters is whether your customers have started choosing them for speed or price, and you can usually find that out by asking the last three clients you lost.

That call needs only two questions: "What made you go with them?" and "Is there anything we could have done differently?" Answers such as "they sent a price the same afternoon" or "they replied on a Sunday" point to speed, which AI can help with. Answers such as "they were cheaper", "they could start sooner" or "we already knew them" point somewhere else entirely, and no amount of AI drafting will win those jobs back.

A client asking "do you use AI?" That's usually a question about confidentiality and disclosure, not a request for you to use more of it. Answer it honestly, and see whether to tell customers you use AI for how to phrase it.

A plan to cut headcount quickly. AI rarely removes a whole role in a small firm in the first year; it removes tasks spread across several people. If the business case only works when someone leaves, test the task savings first and let the staffing question follow the evidence.

The minimum you need even if the answer is "not yet"

Deciding you don't need AI as a project isn't the same as your business not using it. Staff at most firms are already trying free chat tools, often on personal accounts, sometimes with client material. So even at a score of zero, put two things in place: a one-page rule on what must never go into an AI tool, and one approved option on a business account so people have somewhere safe to go. Microsoft 365 business plans come with Copilot Chat and Google Workspace business plans with Gemini, so this often costs nothing extra. The rule can be very light; a single page is plenty for a small team.

Filled in for a small estate agency, the page might read like this (illustrative wording to adapt, not legal advice):

AI USE RULE, version 1, [date]
Approved tool: Copilot Chat, signed in with your work account only.
Never paste in: ID documents, bank details, mortgage offers, offers on
  a property before they're accepted, or anything a client has
  marked confidential.
Fine to use it for: first drafts of property descriptions from your
  own viewing notes, tidying an email, summarising a survey you have
  already read yourself.
Always: read every word before it goes out. Check room sizes, prices
  and dates against the file, never against the AI's version.
Not sure? Ask [named person] before you paste.

Notice what it leaves out: no list of banned websites, no sign-off form, no training course. At a score near zero the job is to give people a safe default, and three short rules do that.

Score your business in ten questions

Questions 1 to 6 measure need. Questions 7 to 10 measure whether you're ready to act on it. Score each 0, 1 or 2 and add them up.

#Question012
1Hours per person per week drafting emails, letters or reportsUnder 22 to 5Over 5
2Hours per person per week keying data from documents or emails into systemsUnder 22 to 5Over 5
3How often the same customer questions arriveRarelyWeeklyDaily
4Typical time to first reply on a new enquiryUnder 2 hoursSame dayNext day or later
5Turning work away or running regular overtimeNoSometimesOften
6Difficulty recruiting for admin or junior rolesNoneSomeSerious
7Main processes written down step by stepNoneSomeMost
8Core softwareOld desktopMixedCloud, with integrations
9Clients asking about AI or expecting faster turnaroundNeverOccasionallyOften
10Someone who can give it two hours a weekNoMaybeYes
  • 0 to 7: wait. Put the minimum in place and score again in six months.
  • 8 to 13: test. Run the 30-day test below on one task.
  • 14 to 20: act. Pick two workflows and budget for them properly.

Watch the split as well as the total. A high need score (questions 1 to 6) with a low readiness score (7 to 10) means the case is real but the groundwork isn't there: write down the process and find an owner before buying anything.

Here's how that split shows up in practice. Picture a 12-person landscaping company (illustrative) scoring itself honestly. Question 1 gets a 1 (quotes and client emails take the office manager about four hours a week), question 2 a 2 (she keys supplier invoices and paper timesheets for well over five), question 3 a 2 (daily "when are you coming?" calls), question 4 a 1, question 5 a 2 because spring and summer run on overtime, and question 6 a 1. That's 9 out of 12 on need. Readiness is thin: 0 for written processes, 1 for software (cloud accounting, but jobs still live in a paper diary), 0 for clients asking, and 1 for someone with time. The total of 11 says "test", but the 9-and-2 split says the test should wait three or four weeks while the office manager writes down how invoices and timesheets actually move through the office. Run the trial before that and you measure her improvising, not the tool.

Three owners, three different answers (illustrative)

A nine-person bookkeeping firm scores 15. Staff spend hours coding receipts, chasing clients for missing records and answering the same "where's my return?" emails. The answer is yes, but the first step isn't a new subscription. Its accounting software probably has AI already. QuickBooks Online and Xero both now build it in, QuickBooks through a set of AI agents and Xero through its JAX assistant, and both aim at exactly this work: coding transactions and reconciling bank feeds. Switch those features on and measure them before adding a chat assistant for client chasers.

A six-person insurance broker scores 11. Renewal letters and comparing old and new policy wordings take most of the admin time, but much of the day is on the phone and the broker's management system is old. The answer is to test one task, the renewal comparison, in a business chat assistant for a month. How brokers use AI to compare policy wordings shows the workflow worth trying.

A three-lawyer firm doing contested cases scores 6. The work is bespoke, volumes are low and every document is checked line by line. The answer is not yet, as a project. An approved business chat tool for summarising long bundles and first drafts of routine letters is sensible, with a hard rule that every citation is checked at the source. What AI still gets wrong explains why that rule matters in legal work especially.

What the smallest sensible start costs

List prices in USD, as of September 2026. Business chat assistants: ChatGPT Business Standard is $25 per user a month, or $20 billed annually, and Claude Team Standard is priced the same way. Microsoft 365 Copilot Business is $21 per user a month on annual billing, with a promotional $18 through 31 December 2026. If a task needs connecting two apps, Zapier starts at $19.99 a month billed annually and Make from about $9 a month.

So a six-person trial on business chat seats costs roughly $120 to $150 a month, plus the time of whoever runs it. Plan for about two hours a week of that person's time for the first two months. What AI costs a small business in 2026 breaks down the larger options.

A 30-day test that settles the question

  1. Pick two tasks linked to your highest-scoring questions, each done at least weekly by at least two people.
  2. Week 1: log them as they are now. How many times each task was done and how long it took. No AI yet.
  3. Weeks 2 to 4: do them with the approved tool. Log the time again, including the time spent checking and fixing the output.
  4. Compare and decide. Keep going if the saving is at least an hour per person per week after checking time, with no rise in errors. Stop if it's under 30 minutes, or if errors went up. In between, try a better prompt or a different task for one more month.
TASK LOG (one row per time the task is done)
Date | Person | Task | Minutes taken | AI used? (Y/N) |
Minutes spent checking/fixing | Any error found later? (Y/N) | Note

A few rows from a four-person travel agency's log (illustrative) show why the checking column matters:

Date  | Person  | Task                  | Mins | AI? | Check/fix | Error later? | Note
03/09 | Agent A | Itinerary cover email | 22   | N   | 0         | N            | baseline week
04/09 | Agent B | Itinerary cover email | 18   | N   | 0         | N            | baseline week
16/09 | Agent A | Itinerary cover email | 7    | Y   | 5         | N            | fixed a transfer time
17/09 | Agent B | Itinerary cover email | 6    | Y   | 4         | Y            | said "all taxes
      |         |                       |      |     |           |              | included"; they weren't

The headline looks great: 20 minutes down to about 6. Add the checking back in and it's roughly 11 minutes, a saving of 9 minutes a time. At about 12 itinerary emails a week across four people, that's under half an hour per person per week, and one wrong claim reached a customer. By the rule above, this task stops. The agency tries its other task, supplier enquiry emails, for the next month instead.

Plenty of tests land in the middle band, and the checking column usually says why. In an illustrative print shop, AI-drafted replies to artwork queries saved about 40 minutes per person per week, short of the hour. Nearly all the fixing time went on one thing: the drafts didn't know the shop's standard bleed, paper weights and file formats, so staff typed them into every reply. Adding a six-line spec list to the saved prompt for a second month took the saving to about 70 minutes, and the task cleared the bar. Had the fixes been scattered, with no single cause, a second month would have been wasted.

The test is deliberately small. It won't tell you everything AI could do for your business, but it answers the question you asked with evidence from your own week. If the numbers come back strong, you need AI, and you know where to start. If they don't, you've spent a month and about $150 finding out, which is cheaper than a year of seats nobody opens.

Other questions owners ask at this stage

Will I fall behind competitors if I wait?

Only if AI changes what your customers experience, such as reply speed, turnaround or price. Check what faster competitors are doing and whether you've lost work to them recently. If clients aren't noticing any difference yet, waiting six months with a policy and one approved tool in place costs little, and the products will be more mature when you start.

Is AI worth it for a one-person business?

Often yes, but as a personal assistant rather than a project. A single paid chat assistant at about $20 a month can cut time on proposals, emails and admin for one person without any setup. The ten-question score still applies: if you spend under two hours a week on writing and admin, the free tiers are enough.

Do I need someone technical on the team?

Not for chat assistants or the AI built into software you already use. You need someone organised who can spare a couple of hours a week, keep the prompts and rules tidy, and notice when output quality slips. Technical help matters later, when you connect AI to other systems or build automations that run without anyone watching.

Further reads

Sources: ChatGPT Business, Claude Team, Microsoft 365 Copilot Business, Zapier and Make pricing pages; Xero JAX and QuickBooks Online AI agent product pages.

Not sure which side of the line you're on?

On a 1:1 call we'll go through where your team's hours actually go, test that against your tools and data, and decide together whether to act now, trial one task, or wait.

Book a 1:1 call with me