What AI Should Never Do in Your Business

In rebuilding operating processes, I've had to clarify who owns the work as it moves between departments. I bring that same discipline to AI: preparing something and having authority to approve it are different responsibilities.

For a small business owner, that distinction matters whenever a document, payment instruction, or customer message is ready to leave the business. The decision isn't just whether to use AI assistance. It's who has authority to commit the company, and whether that person has actually reviewed the work.

My boundary is straightforward: I use AI to assist work, not to replace accountable human judgment in legal obligations, financial commitments, or consequential customer conversations.

Legal obligations need more than readable language

I wouldn't treat an AI-assisted draft as legal clearance. My responsibility is to understand the business purpose, identify the obligations under consideration, and bring material legal questions to qualified counsel.

I can organize information and prepare questions with AI assistance. I wouldn't use that assistance as a substitute for professional review when a decision affects contracts, employment obligations, privacy requirements, or other legal responsibilities.

The approval has to mean something. Before accepting language, I'd want the responsible person to understand what the business is agreeing to, what it must do afterward, and which questions remain unresolved. A document that reads smoothly doesn't establish any of those things.

I'd also set boundaries on the information used during preparation. Permission to work on a document isn't automatically permission to put every detail into an AI tool. I would establish what information may be used, in which approved tools, and under what restrictions before the work begins.

Financial authority stays with a person

I separate financial preparation from financial authority. I may organize costs, compare assumptions, or develop a working analysis with AI assistance. I still own the analysis and the decision about what the numbers mean.

I wouldn't make an AI-assisted output the sole basis for releasing money, changing payment details, accepting a financial obligation, or making a material tax decision. Those actions need an authorized person and the appropriate checks. Where accounting or tax judgment is material, I'd involve a qualified professional.

For me, financial review starts with the source information. I want to know where a figure came from, which assumptions sit behind it, and whether anything important is missing. Reviewing only the finished summary leaves too much outside the review.

I'd put the approval boundary into the process itself. The person preparing the work should know which actions require authorization, who can give it, and where that authorization is recorded. A general instruction to “check everything” isn't a usable approval process.

Customer relationships aren't just writing tasks

I distinguish routine communication from a message that changes the relationship. A sensitive complaint, a disputed obligation, or a promise about what the business will do next deserves a person who understands the situation and has authority to respond.

I may prepare wording with AI assistance. I wouldn't let that preparation become an unreviewed apology, concession, commitment, or statement of company policy.

My review would go beyond tone and grammar. I'd check whether the message reflects what actually happened, whether the commitment is authorized, and whether the business can carry it out. Polished wording isn't enough if the substance hasn't been settled.

I'd also preserve a clear route to a person. When a customer needs judgment or an exception, I want a named employee responsible for the next step, rather than another message that leaves the issue unresolved.

Write the limits before making exceptions

I would make these boundaries part of the operating instructions, not leave them as an owner's unwritten expectations. For each sensitive task, I'd specify what assistance is allowed, what information is restricted, who reviews the work, and what cannot proceed without approval.

I'd define a stop point as well. Missing information, conflicting instructions, or uncertainty about authority should send the work to a responsible person. I wouldn't make completing the task more important than resolving the uncertainty.

I don't see these limits as an argument against AI. They're how I keep assistance separate from authority. My standard is that a named person understands and accepts the business consequence before a consequential action proceeds. If that responsibility isn't clear, I wouldn't approve the process.