A question is showing up across Massachusetts small businesses, from professional services and family manufacturers to dental practices and landscaping companies with an office manager and four crews.
Do we need to hire an AI person?
For most small businesses, that question arrives too early. AI features are already appearing inside scheduling software, bookkeeping platforms, customer service tools, and email systems. Owners see the change and reasonably assume they need technical expertise to keep up.
You may eventually need outside help. But before you post a job, look at the people already on your payroll.
I spent more than twenty years implementing clinical technology across more than 270 healthcare facilities before I began training workforces on AI. Healthcare is not small business, but one adoption pattern repeated for two decades. The implementations that struggled were the ones that routed around experienced staff. The ones that worked put the technology in the hands of people who understood the work well enough to know when something was wrong.
That lesson matters even more with AI.
The AI tools arriving inside small business software are not asking anyone to write code. They draft the customer email. They summarize the intake form. They flag the invoice. They prepare the proposal.
Learning to click the button is not the difficult part. Knowing when the output is wrong is.
That requires judgment about your customers, your pricing, your procedures, your risk, and your reputation. Your employees who have been doing the work for years already hold much of it. You can hire AI expertise. What you cannot hire quickly is years of knowledge about how your business actually works.
So before asking who you should hire for AI, ask a better question. Who already understands this business well enough to know when AI gets it wrong?
Do not default to whoever is most comfortable with technology. Comfort tells you someone will try a new tool quickly. It does not tell you they will recognize a convincing but incorrect answer.
Look for three signals instead.
None of these are technical. In most small businesses this person sits in operations, administration, finance, or a customer facing role. They are frequently one of your most experienced employees.
Most AI training starts with prompting. How do I ask for what I want.
Start somewhere else. Start with verification.
Before employees learn to get better answers, they need to know how to evaluate the answers they receive. What does this tool actually have access to. What does it not know. What should never be entered into it. What would a plausible but wrong answer look like in our business. Which outputs require human review, and who is responsible for it.
A team that prompts well but verifies poorly will produce wrong work faster than before. That is not a productivity gain. That is a liability with better formatting.
Verification also forces a conversation most owners have not had. When AI generated work goes wrong in front of a customer, the question is not what the software did. It is who was responsible for checking it. If your team cannot answer that, you do not have an AI policy. You have an exposure.
The typical order looks like this.
Reverse the middle two. Train your people, agree on what requires human review, then expand use.
The policy does not need to start as a thirty page document. In the sessions I run, teams draft a workable one page workplace AI use policy in a single sitting, because the people writing it are the people doing the work. They know which tasks carry risk, where customer information lives, and which shortcuts would embarrass the company.
You do not need to turn your company into AI experts by Monday.
Choose one experienced employee who understands the work. Choose one repetitive, relatively low risk workflow. Train that person to use AI on it, verify the output, document what works, and identify what still requires human judgment. Once it runs consistently, expand from there.
That gives you something more useful than scattered experimentation. It builds internal capability shaped around how your business actually operates.
One condition, though. Retraining does not mean quietly adding “AI expert” to someone’s existing workload. If you are asking an employee to become your internal AI lead, give them training, time, authority, and a defined scope. AI adoption should remove unnecessary work, not create another invisible job for your best person.
The Commonwealth Corporation’s Workforce Training Fund Express Program allows eligible Massachusetts employers with 100 or fewer employees to apply for reimbursement of approved workforce training.
Three details worth knowing before you plan around it.
Whichever provider you choose, it is worth ten minutes to review the approved training directory and confirm current program requirements before you assume workforce development is an expense your business absorbs alone.
AI will keep arriving in your business. It will show up in the next software update, in the platform your vendor adopts, in the tool your competitor starts using.
You may not control when it arrives. You do control whether it lands on a workforce prepared to use it well.
The most valuable person in your business may still be the employee who looks at a perfectly polished answer and says that something about this is not right. Give that person the training, time, and authority to help your team use AI responsibly.
Before you post a job for an AI specialist, look around your own payroll.
Human First. AI Second. Always.
This is a contributed blog post written by Jennifer Ngure, MSHI, PMP, RN, NI-BC, founder of Imara Health AI Consulting LLC, a Massachusetts based firm focused on AI workforce readiness, responsible adoption, governance, and training. Are you interested in submitting a blog post? Fill out our contact form.
Enter your name and email address for our State of Small Business in Massachusetts 2026 report to find out. You'll also receive weekly emails from us!
Leave a Reply