Our team will be out of office on Friday, May 1, 2026. We’ll be back and ready to assist you starting Monday, May 4th.

Why Doesn’t My Team Use The AI We Pay For?

Contents

Because it does not know anything about your business, and your team figured that out faster than you did. Here is the question this article answers: what do you actually have to build before AI output is good enough that people choose to use it?


The Hook

A builder on Reddit did something yesterday that nobody selling AI software wants done. He went and asked a group of sysadmins what their companies actually use AI for after the rollout is finished, and then he published the answers without cleaning them up.

"A more expensive Google web search."

"Execs use it and ask us to use it. No one uses it."

"One guy said out of 300 users maybe 5 use it."

Five out of three hundred. Somebody paid for three hundred seats.

If you bought AI for your team this year and the usage is thinner than you expected, here is the direct answer: your team is not resistant and they are not behind. They tried it, got an answer that could have come from anywhere, and correctly decided it was not worth the trouble. The tool does not know your prices. It does not know your policies. It does not know who your customer is or what you have already tried that failed. It is a very articulate stranger, and nobody wants advice from a very articulate stranger about their own business.

The fix is not a better model. The fix is giving the model your business in writing. That is an afternoon of work, and it is the entire difference between an expensive search box and something your team opens on purpose.

Key Takeaways

  • AI adoption usually fails on context and provenance, not on model quality or employee willingness.
  • MIT's NANDA research found roughly 95 percent of enterprise generative AI pilots produced no measurable financial impact, and attributed the failures to integration rather than to the models.
  • The two requests that deployers hear most and cannot deliver are an AI that knows the company's own material, and an answer that shows where it came from.
  • You can close most of that gap yourself with four plain-language files and one standing instruction.
  • Adoption spreads from one person who got a real win on one recurring task, never from a company-wide announcement.

The Problem

Here is the part that stings. You did the responsible thing. You picked a reputable tool, you bought licenses, you probably ran a training session, and you told the team it was available. Then you waited for the productivity.

What you got instead was a handful of enthusiasts, a long tail of people who logged in once, and a quiet suspicion that your team is just not very adaptable.

I have been on the wrong side of this. I built a seven-figure agency and lost it, and one of the honest reasons was that I kept buying capability and skipping implementation. New tool, new platform, new system, same assumption: that if I put the thing in front of people, the value would follow. It never once did. The tool was never the missing piece. The missing piece was always the specific, boring, unglamorous work of making the tool know what we knew.

The research says this is not a me problem. MIT's NANDA initiative looked at 150 leader interviews, a survey of 350 employees and 300 public AI deployments, and concluded that roughly 95 percent of enterprise generative AI pilots produced no measurable profit-and-loss impact. That figure is from 2025 and it gets misquoted constantly, so be precise about what it measures: it is pilots without measurable financial return, not employees refusing to use software. The report's own explanation is the useful part. It blamed integration and a learning gap. Not model quality.

Recon Analytics found something that makes the same point from a different direction. When workers have both Microsoft Copilot and ChatGPT available to them, Copilot adoption falls to 18 percent while ChatGPT takes 76 percent. That is a vendor-adjacent survey and I would hold the exact numbers loosely. But the shape is not controversial: given a choice, people go to the tool that gives them a usable answer, and nothing about the underlying model explains that gap.

But what if the problem is not that your team needs convincing? What if they already told you the answer and you heard it as resistance?

The Evidence

Go back to that sysadmin thread, because the useful part is not the complaints. It is the list of things clients keep asking for that the person deploying the software cannot deliver. He wrote down three.

Knowing the company's own material, not just the documents somebody indexed.

Showing where an answer came from before an employee sends it to a client.

Controlling who is allowed to ask what.

Read those again and notice that not one of them is about intelligence. All three are about context, provenance and permission. A separate post in r/artificial made the same argument more bluntly, pushing back on the idea that an AI "knows" a company just because somebody handed it access to the document folder. Access is not knowledge. A filing cabinet in the room does not mean you understand the business.

Now watch the market agree in public, because this is the part that convinced me the diagnosis is right.

Today on Product Hunt, Hexis Cloud launched at number seven with a one-line pitch: one company brain for all your AI agents. On the same board at number two, Google's EmbeddingGemma 2, an open lightweight multimodal embedding model, which in plain language is the raw material for making your own files findable by a model. At number five, Manifold MCP, selling data for your agent. Four days earlier, Anthropic put Claude inside Google Docs, Sheets and Slides in public beta, which is a bet that the valuable thing is proximity to your actual documents.

Every one of those products is the same wager: the scarce resource is no longer intelligence, it is your context.

And here is the detail that should settle it for you. Anthropic shipped Claude Haiku 5.5 on Oct 7, positioned explicitly for high-volume, cost-sensitive work. OpenAI shipped GPT-6 Sol and Luna into ChatGPT the same day. Capability went up again last week, and it did not fix a single one of those three requests. It cannot. No model release will ever tell your team what your refund policy is.

What Actually Changes It

So here is the system, and I am going to be specific because vague advice is how this problem survives.

You are building four files. Not a platform, not a knowledge base project, not a vector database. Four plain text or markdown files that any AI tool can read, which you or one person on your team can maintain in minutes a week.

File one is what you sell. Every offer, the exact price, what is included, what is not. Not "starting at." Not a range. The actual number. This is the single highest-value file you will write, because pricing is the thing AI gets wrong most often and the thing that costs you most when it is wrong. A made-up price in a client email is a refund conversation.

File two is who you serve and what they have already tried. Your customer, in their language, including the solutions that failed them before they found you. This is what separates an answer that lands from an answer that reads like a brochure.

File three is your policies and boundaries. What you do. What you decline. Your service area, hours, response time, refund terms. And the section almost nobody writes: what you are not. The worst AI output is rarely inaccurate. It is overcommitted. An AI that does not know what you refuse will cheerfully promise it.

File four is your voice. How you write, the words you never use, the formatting rules you hold to. I can fix a wrong fact in a minute. A wrong voice takes an hour, which means it does not get fixed, which means the output does not get used.

Then you add one standing instruction, and this is the part that converts skeptics. Every answer must say which file it came from, and must say "not in our files" rather than guessing. Remember the sysadmin complaint. It was never that the answers were wrong. It was that nobody could tell. Provenance is what makes an answer forwardable, and forwardable is the whole difference between a curiosity and a tool.

That is it. That is the implementation layer everybody skips, and it is why five people out of three hundred use the software.

Practical Steps

1. Ask your team before you fix anything. Five questions, under twenty words each, not a survey and not a performance review. The one that matters: when was the last time you tried and gave up, and what happened? You are looking for the specific moment the tool lost them, because that moment is your test case later.

2. Block two hours and write the four files. Dictate them if writing is slow. Have the AI interview you and draft them, then correct every number by hand. Do not aim for elegance. Aim for complete and exact. A file with your real prices in it beats a beautiful document with a range.

3. Write the "what we do not do" section deliberately. Separate pass, own section. List the work you decline, the customers you are a bad fit for, the things people ask for that you do not offer, and the promises you never make. Include the alternative you suggest when you decline. This section prevents more damage than the other three combined.

4. Add the citation rule and the refusal rule. One paragraph, pasted at the top of any AI chat your team starts. Every answer names its source file. Any gap gets "not in our files" instead of a plausible guess. Test it by asking something you deliberately left out and confirming it says it does not know.

5. Pick one recurring task and make the AI excellent at only that. Not the whole company. One task, done weekly, by somebody who can recognize a bad output instantly, where being wrong means a redo rather than a customer problem. Write the instruction set, define what good looks like so the user can judge it, and hand it to one person.

6. Run the test that already failed. Take the three questions the AI answered badly before you did any of this. Ask them again with the files loaded. If the answers are right now, show your team the before and the after. Trust comes back from a visible improvement, never from an announcement.

7. Measure in weeks and set a stop rule. Three numbers a week for four weeks, plus one question to the team. Decide in advance what result tells you to abandon this task and pick a different one. If you do not set the stop rule now, you will interpret any outcome as encouraging.

Here is a prompt to start step two with, built on the Perfect Prompt Framework 2.0.

[The Job] Interview me and build a plain-language context file about my business that any AI can read before it writes or answers anything. This is for: every AI tool my team uses. It matters because: right now the AI knows nothing about us and gives generic answers nobody trusts.

[The Background] Here is what you need to know: my business is [WHAT YOU DO], my customer is [WHO YOU SERVE], my prices are [EXACT PRICES], and the questions we answer most are [TOP THREE QUESTIONS]. Do not use: marketing language, or any claim I have not given you.

[The Deliverable] Return: a markdown file under 1,200 words with sections for what we sell, who we serve, our exact prices, our policies, and how we talk. Must include: the real numbers I gave you. Optimize for: accuracy.

[The Questions] Ask me any questions you have.

Frequently Asked Questions

How long does it actually take to write business context files?

Two to three hours for a first version if you dictate and let AI draft while you correct the facts. The pricing file is the slowest because every number has to be exact. Plan on a second pass a week later once you have seen where the gaps show up in real use.

Do I need special software to give AI my business context?

No. Plain markdown or text files that you paste in, or upload to a project or custom instructions area, work for most small businesses. Buy a context platform only when you are running several agents that all need the same material and the material changes weekly.

Why does my AI give generic answers even when I upload documents?

Access is not organization. A long unstructured document gets summarized, and summaries lose the exact numbers. Restructure so each fact sits on its own line under a clear heading, and keep the whole file short enough to be read rather than condensed.

Is low AI adoption on my team a training problem?

Usually not. Training teaches people how to prompt a tool that still does not know your business, so the output stays generic and the training does not stick. Fix the context first, then one short session on one real task will do more than a full training day did.

What is the first file I should write?

Pricing, with exact figures and the conditions that change them. It is the highest-frequency question, the most expensive thing to get wrong in front of a customer, and the fastest way to prove to a skeptical team member that the tool now knows something real.

The Close

Five people out of three hundred. That is what a rollout looks like when you buy the capability and skip the implementation.

I want to be careful here, because it would be easy to read this as a story about other people's companies. It is not. It is the exact mistake I made for years, with marketing software, with CRMs, with every system I ever bought believing the thing itself would create the result. It never did. The result always came from the unglamorous week where I sat down and wrote out what we actually knew so the system could use it.

Your team is not behind. Your team is accurate. They tried something that did not know your business and they stopped using it, which is the correct response to a tool that wastes their time.

So give it your business. In writing. Four files and an afternoon.

The AI does not need to be smarter. It needs to know what you know.


About the author. Jonathan Mast is the founder of White Beard Strategies, where he teaches non-technical business owners how to use AI to amplify the skill and experience they already have. He runs a 500,000-member entrepreneur community, the AI Insiders membership at $247 per month, and live training programs including Express AI Training at $10 live or $20 for the replay. He is the creator of the Perfect Prompt Framework and a frequent speaker on practical AI implementation. He has built a business, lost it, and rebuilt it, which is most of why he writes about implementation instead of capability.

About the Author