The Internal Ops Assistant: Stop Being Your Team's Search Engine

Count the interruptions tomorrow. Not the real problems. The questions.

"What do we charge for that?" "Are we in that zip code?" "What's the warranty on the parts?" "Do we need a deposit?" "Who do I call if the truck breaks down?" "Where's the W-9?"

You've answered every one of these before. You've probably answered several of them this month. In a ten-person business, the owner is a search engine with a pulse, and it eats an hour or two of your day in fragments so small you never notice them go.

This is the single easiest thing to fix with AI, and almost nobody does it, because it isn't sexy and there's no revenue line with its name on it. Fix it anyway. It buys you back the most expensive hour in the company: yours.

What an internal ops assistant actually is

Strip the jargon. It's a chat your team can talk to that has read every document you'd otherwise have to explain, and answers in plain English with a link to where it got the answer.

That's the whole thing. Two parts:

A pile of documents that represent how your business works.
A way to ask questions of that pile and get a cited answer.

Part two is a solved problem now. There are a dozen ways to stand it up, several of which are cheap and none of which require you to write code. Part one is the actual project, and it's the part everyone skips.

The documents are the work

Here's the uncomfortable truth. The reason you're your team's search engine isn't that you lack software. It's that the answers live in your head and nowhere else.

The assistant is only as good as what you feed it. So the build is really an excuse to finally write down the things you've been meaning to write down for four years.

Start with these. Nothing fancy, plain documents:

Pricing and what's included. Every service, the price or the range, what's in it, what costs extra, when you discount and when you don't.
Service area. Cities, zips, how far is too far, what you charge for the far ones.
Policies. Deposits, cancellations, warranty, payment terms, what to do about a refund request.
The "who do I call" list. Supplier contacts, the backup plumber, the guy who fixes the truck, the accountant.
How to handle the ten hardest customer situations. The angry review. The customer who wants the price matched. The one who won't pay. Write down what you'd actually say.
Onboarding. What a new hire needs to know in their first week.

Each of these is thirty minutes of writing. Most of it you can dictate into your phone while you drive and clean up later. Do one a day for two weeks and you have a company handbook, which you needed regardless of whether you ever build the assistant.

That handbook is the asset. The AI is just the interface to it.

Rules that make it work

Answers must cite the source. Every response tells the person which document it came from. This does two things. It lets someone verify a high-stakes answer. And it lets you find the document that's out of date when the answer is wrong.

Wrong answers must be reportable in one click. Give your team a way to flag a bad answer. Read the flags weekly. Every flag is either a document that's missing, a document that's wrong, or a question you never realized people had. All three are gold.

It says "I don't know." This is worth insisting on. An assistant that invents a plausible price is worse than no assistant, because it will be wrong confidently and someone will quote it to a customer. Make it clear that when the documents don't cover something, the answer is "that's not written down, ask Chad." Then write it down.

High-stakes questions get a human. Anything involving a legal commitment, a discount over a threshold, or a safety issue: the assistant answers with what's written and tells them to confirm with a person. Not because AI can't handle it, because that's the boundary where a mistake is expensive and nobody's checking.

What changes

The first week, nobody uses it. Expect that. People ask you because asking you works.

So don't launch it and hope. Do this instead: for two weeks, every time someone asks you a question that's in the assistant, answer it with "ask the assistant, and tell me if it gets it wrong." Feels petty. Works in about ten days.

Then the shape of your day changes. The questions you get are the ones nobody has an answer to, which are the ones that actually need you. Your new hire ramps in half the time because they can ask the dumb questions at 9pm without feeling stupid. Your office manager stops holding six pieces of tribal knowledge that would leave with her.

That last one is the real prize. In most small businesses, one or two people are load-bearing in a way nobody's admitted. They know the thing. If they quit, or take a two-week vacation, or get sick, things break in ways nobody can diagnose. Writing it down de-risks the business. The assistant is what makes writing it down feel worth doing.

What it won't do

It won't know anything that's happening right now. It doesn't know who's on the schedule Thursday or whether that part came in, unless you wire it into the systems that know, which is a bigger project and usually not the one to start with.

It won't replace training. A new tech still needs to ride along. The assistant handles recall, not skill.

It won't fix a business where the policies genuinely don't exist. If your pricing is "whatever I feel like that day," an assistant can't help, and honestly neither can any other system. Decide the policy first. That's a management problem wearing a technology costume.

Start smaller than you think

Don't try to document the whole business. Pick the five questions you get most often. Write those five answers. Load them. Tell three people. See what happens.

If your team uses it, add more. If they don't, find out why before you write another word, because you've learned something more valuable than any document: they'd rather interrupt you, and there's a reason.

The whole first version is a weekend, and most of that weekend is you talking into your phone about how your own business works. Which, either way, is time well spent.

If you want the ops assistant built and wired into the documents and tools you already have, that's one of the systems I put in. Or tell me the five questions you're sick of answering and we'll start there.