Where should a small business start with AI?
The short answer: To start using AI in a small business, pick one boring, frequent task where a person can check the output, such as drafting replies to common questions or summarizing call notes. Score a few candidates on value, effort and risk, set rules for what data may go into which tool, and run the first task for about a month. Leave anything customer-facing or involving money for later.
Say a few people on your team already use an AI assistant. You can tell, because some of their emails got smoother around spring. Somebody in sales has probably pasted a customer list into a public tool to “tidy it up”. Nobody told you, and nobody did it to cause trouble. Meanwhile a vendor emails you every morning with a plan to change your entire business.
You don’t need a strategy deck. You need to choose one thing, and to decide what never goes into the tools. Both take less time than the vendor’s demo.
How do you start using AI in a small business?
Start with the work, not the tool. Write down the tasks your team repeats every week that involve reading or writing, then pick one. The right tool is usually obvious once the task is clear, and it’s often one you already pay for.
Good first tasks share four traits:
- Frequent. It happens daily or weekly, so you’ll see results fast.
- Text-based. Reading, writing, sorting, summarizing and extracting are jobs you can check at a glance.
- Low-risk. If the output is wrong, the damage is small and caught before it leaves the building.
- Easy to check. You already know what a good answer looks like, so a person can review it in seconds.
Typical candidates: drafting first replies to common customer questions, summarizing meetings or calls, sorting incoming requests into categories, pulling fields out of emails or forms, and writing first drafts of routine documents. None of that is exciting. That’s the point. It’s the work nobody wants to do, and the cost of a mistake is a corrected draft.
How do you choose between candidates?
Score each one on value, effort and risk, then compare the totals. It takes twenty minutes with the person who does the task today, and it stops the loudest idea from winning by default.
Use a simple scale. For each candidate give a 1, 2 or 3 on three questions:
- Value: how much time or irritation does this remove? 3 is a lot.
- Effort: how hard is it to set up and check? 3 means easy.
- Risk: how bad is a wrong answer? 3 means low risk.
Here is an illustrative example. These scores are made up to show the method, not measured in any real business.
| Candidate task | Value | Effort | Risk | Total |
|---|---|---|---|---|
| Draft first replies to common customer questions | 3 | 2 | 2 | 7 |
| Summarize call or meeting notes | 2 | 3 | 3 | 8 |
| Sort incoming requests by type | 2 | 3 | 3 | 8 |
| Pull key fields out of emailed orders | 3 | 2 | 2 | 7 |
| Decide which invoices to pay | 2 | 1 | 1 | 4 |
Two rules keep the table honest. First, a 1 on risk is a veto, whatever the total says. Second, ties go to the task where checking is fastest. In the example, you’d start with call summaries or sorting requests and leave the invoice decision alone for a good while.
What data rules should you set on day one?
Write down what can be shared, with which tool, before anyone starts. The National Cybersecurity Alliance’s guidance for small businesses puts it this way: define in writing what information can and cannot be shared with outside platforms, and assume that anything entered into a public AI tool may be stored or processed by a third party.
A first set of rules fits on half a page:
- Name the approved tools. Anything else needs a yes from one named person. The Cyber Readiness Institute suggests starting with an inventory of what staff already use, approved or not.
- Write the never list. Customer personal details, financial records, passwords, and confidential documents stay out of public tools.
- Prefer business plans over consumer ones. The National Cybersecurity Alliance notes that business versions often include stronger contractual data protections. Read the terms for your plan, because they differ.
- Treat what you paste as shared. The Cyber Readiness Institute’s wording is that anything entered into a public tool should be treated as public disclosure.
- A person reviews anything that leaves the building. The Small Business Administration’s guidance also says a person should assess customer messages and outreach before they go out.
The Cyber Readiness Institute also makes a point worth keeping: governance, not prohibition, is the key. A blanket ban mostly pushes use underground. Rules people can follow work better. Our post on a two-page AI policy goes into the wording.
How do you run the first task?
Run it as a small experiment with an end date. Four steps are enough.
- Time it today. Ask the person doing the task how long it takes and how often. That’s your baseline, and without it you can’t tell whether the AI helped.
- Run it for four weeks with a person checking everything. Keep a note of every output they had to fix.
- Decide a stop condition up front. For example: if more than a set share of outputs need rewriting, pause and rethink. Choose the number before you start, not afterward.
- Compare, then decide. Did it save time after checking? Did anything slip through? Keep it, change it, or drop it.
The checking is the work at first. Once the fixes dry up, you can relax the review a little, and only then try something harder.
What should you not do?
Skip these, in roughly this order of how often they happen:
- Don’t start with something customer-facing and automatic. A bot that replies to customers on its own is a second or third project.
- Don’t buy a tool before you’ve chosen a task. You’ll end up shopping for a use.
- Don’t paste customer lists into a public tool to tidy them up. It’s an easy leak, and it needs no malice.
- Don’t promise your board a number. Until you’ve timed it in your own business, any figure is a guess, including ours.
- Don’t wait for perfect data. Tidy only what the first task reads. If the assistant answers from your policy documents, those documents need to be current. Your whole file server can wait.
- Don’t treat the output as the final word. The Small Business Administration says to have another person review what these tools produce.
If you run Salesforce, the same logic applies to agents: pick a narrow job first. Our post on choosing your first Agentforce use case covers that, and Agentforce data readiness covers what the records need.
What to do Monday:
– List ten tasks your team repeats weekly, then mark the ones that involve reading or writing.
– Score your top five on value, effort and risk, with the person who does the work.
– Ask your team which AI tools they use now, and promise no blame for honest answers.
– Write the never list: five things that don’t go into a public tool.
Where we come in
We do AI consulting for companies of roughly 10 to 500 people, on any stack, with Salesforce not required. The usual starting point is a half-day AI Opportunity Workshop that scores your candidates by value, effort and risk, and ends with a written short list. We’re not a reseller and take no commission from AI vendors. See AI consulting for how it runs and what we won’t do.
Questions people ask
Do we need to clean up our data before using AI?
Only the data the first task touches. An assistant that answers questions from your policies needs current, well-organized policies. It doesn’t need your whole file server sorted out. Pick the task first, then tidy what it reads, and expand the cleanup only when the next task needs more.
Is it safe to put customer data into AI tools?
It depends on the tool, the plan and the data. Treat anything entered into a public tool as shared. Business plans often have stronger data protections than consumer ones, but terms differ, so read yours. Keep customer personal details, financial records and passwords out until someone has checked the terms.
How long should a first AI project run?
About a month is enough to learn something real. Time the task before you start, check every output with a person, and set your stop condition in advance. That’s our rule of thumb, not a standard. A shorter run teaches you little. A longer one drifts.
Sources
- National Cybersecurity Alliance: AI best practices for small businesses: written rules for shared data, business plans over consumer ones, human review.
- Cyber Readiness Institute: Using generative AI at work: August 12, 2026 guidance on tool inventories, public disclosure and governance over bans.
- U.S. Small Business Administration: AI for small business: start small, avoid sensitive data, have a person review outputs.