If you bought AI subscriptions for your team and almost nobody logs in, this article answers the question you have been quietly asking: is the problem your people, your training, or the way you installed the tool in the first place?
The Uncomfortable Thing Your Login Report Is Telling You
You paid for the seats. You ran the training. You sent the follow-up email with the link, twice. And when you pulled the usage report last week, four people had logged in since March and two of them were you on different devices.
That stings. Not because the money is enormous, but because you can see the opportunity sitting right there and you cannot get anyone to walk through the door.
Here is the direct answer. Your team is not resisting AI. They are resisting the tab. The tool you bought asked them to leave the place where their work already lives, remember a new habit under deadline pressure, and rebuild context that already existed somewhere else. That is not a motivation problem and no amount of enthusiasm from you will fix it. It is a friction problem, and friction always wins over intention in a busy week.
I want to be careful here, because this is the part where most consultants start selling fear. I am not going to do that. Your people are not lazy or behind or scared of the robots. In my experience, the same person who “will not use AI” at work has a personal ChatGPT account they use every weekend to plan meals and draft awkward emails. They already like this stuff. They just will not add a fifth window to a four-window day.
The thesis of this entire article is one sentence: AI adoption succeeds when the AI shows up inside a surface your team already touches, and it fails when it asks them to go somewhere new.
Everything below is the evidence for that claim and the process for acting on it.
Key Takeaways
- Your team’s low AI usage is almost always a friction problem, not a motivation or training problem.
- The AI products gaining real traction right now embed into existing surfaces instead of asking users to visit a new destination.
- MIT’s 2025 research found 95 percent of enterprise generative AI pilots produced no measurable profit and loss impact, and blamed workflow integration rather than model quality.
- Employees are already using AI on their own, which proves the appetite exists and the delivery method is what broke.
- You will get more adoption from moving one AI capability into an existing tool than from buying three more subscriptions.
You Bought a Destination, Not a Habit
Let me describe the pattern I see over and over, because you may recognize your own company in it.
A business owner gets excited about AI. Reasonably so. They buy team seats on a good tool. They schedule a training session, which goes well, because trainings always go well. Someone says “this is going to save me so much time.” Everyone leaves energized.
Then Monday happens.
Monday is a client escalation, a payroll question, a proposal due at four, and a supplier who did not ship. In that environment, your team member has a task in front of them. To use the AI you bought, they have to stop, open a browser tab, log in, decide what to type, paste in context from three other places, wait, read the output, copy it back, and reformat it. Each of those steps is small. Together they are a wall. The old way takes twenty minutes and requires zero new decisions. The new way might take eight minutes, but only after they get good at it, and getting good at it costs time they do not have on a Monday.
So they do it the old way. Not out of stubbornness. Out of arithmetic.
Here is the part I will admit honestly: I got this wrong for a long time. My instinct was that adoption was about persuasion. If people were not using the tool, I needed a better use case, a more compelling story, a better training. Some of that worked, briefly. Almost none of it stuck past about three weeks, because motivation is a battery and it drains.
The reframe that changed my results is this: stop trying to make people want it more, and start making it require less.
That single shift moves you from being a cheerleader to being a systems designer. It is less fun and it works much better.
Four Findings That Point the Same Direction
I do not want you to take my word for this. Look at what the research and the market are both saying.
MIT found that the failure is in the workflow, not the model. MIT’s Project NANDA published “The GenAI Divide: State of AI in Business 2025,” based on 52 executive interviews, surveys of 153 leaders, and analysis of 300 public AI deployments. The headline finding was that roughly 95 percent of enterprise generative AI pilots delivered no measurable profit and loss impact. The reason mattered more than the number. The researchers attributed the failure to a learning and integration gap, not to model quality. The models were good enough. The way they were bolted onto the business was not.
The same MIT report found people are already using AI, just not the AI you bought. The report documented that workers at over 90 percent of surveyed companies regularly used personal AI tools for work tasks, while only about 40 percent of companies had purchased official large language model subscriptions. Read that twice. The appetite is not missing. The appetite is so strong that people are routing around your procurement process to satisfy it. That is not an adoption problem. That is a delivery problem wearing an adoption costume.
A 2026 survey confirms the pattern is still running, and shows where the habit starts. PagerDuty published its Shadow AI Survey in June 2026, conducted by Wakefield Research among 1,250 office professionals at companies with at least 500 million dollars in annual revenue across the United States, United Kingdom, Australia, and Japan. Two-thirds, 66 percent, said they had used AI tools at work even though they believed it violated company policy. The finding I care about most: 89 percent of those who use AI for work say they first encountered the tool in their personal lives. People adopt AI where they already are, then drag it into work. That direction of travel is the whole lesson.
Behavioral science named this decades ago. BJ Fogg, the Stanford behavior scientist who has run a research lab there for more than twenty years, describes behavior as three things converging: Motivation, Ability, and a Prompt. He writes it as B equals MAP. The critical detail is that these multiply rather than add. If ability is near zero, meaning the behavior is hard in the moment, no amount of motivation produces the behavior. Fogg’s practical advice is to stop pumping up motivation and instead remove friction, because ability is the lever you actually control. Your AI rollout is a live experiment in that principle, and right now it is telling you the ability score is too low.
Now look at what the market is building in response.
Recent Product Hunt launches cluster around the same idea. Dune Keypad is a physical, context-aware keypad that sits next to your Mac keyboard and triggers Claude-powered workflows from a key press, and it landed at number four on its launch day in June 2026. Databox MCP lets you chat with your business dashboards from inside Claude or ChatGPT using the Model Context Protocol, which is simply an open standard that lets AI assistants pull from outside data sources. Typeahead is AI autocomplete that works across every app on a Mac rather than inside one. And on August 2, 2026, OpenAI launched “Sign in with ChatGPT” in beta with Airtable, GitLab, HubSpot, Notion, Supabase, and Vercel as launch partners.
None of those is a destination. Every one of them grafts onto a surface the user already touches.
Design for the Surface, Not the Software
Here is the framework I now use with clients. I call it surface-first implementation, and it has four parts.
One: find the surface. Before you pick a tool, name the exact place where the work currently happens. Not the department. The actual screen. Is it the inbox? The CRM record? The shared spreadsheet? The Slack channel? The phone? If you cannot name the screen, you are not ready to buy anything. The surface is the constraint that every other decision has to bend around.
Two: bring the capability to the surface. Once you know the screen, your job is to deliver the AI capability into that screen, not to relocate the person. This is where connectors, integrations, and the Model Context Protocol earn their keep. Databox MCP is the clean example: instead of teaching your team to export a dashboard, upload it, and prompt over it, you let them ask a question about their numbers inside the chat window they already have open. Same capability. No relocation.
Three: cut the decisions, not just the clicks. Friction is not only physical. It is cognitive. A blank prompt box is a decision, and decisions are expensive on a Monday. This is why I built the Perfect Prompt Framework the way I did: not to make prompts clever, but to make them repeatable, so that the person using it is executing a known pattern rather than inventing one. Save the prompt. Name it. Put it where they work. A saved prompt with a clear name removes more friction than an hour of training.
Four: measure the workflow, not the login. Stop tracking seat usage. Track whether the specific task got faster. If your quoting process took forty minutes and now takes fifteen, you have adoption whether or not anyone logged into anything. If logins are up and cycle time is flat, you have theater.
The practitioners doing serious work in this space are teaching the same thing from different angles, which is usually a sign that something is true. Rachel Woods, founder of DiviUp and The AI Exchange, focuses on AI operations and building systems that scale themselves rather than one-off prompt wins. Andy Crestodina, co-founder and CMO of Orbit Media, has been making the case that tools and workflow beat prompt cleverness. Brian Piper, co-author of the second edition of Epic Content Marketing and host of the AI for U podcast, teaches optimizing content you are already producing with data rather than generating more of it. Noelle Russell of the AI Leadership Institute teaches responsible scaling. Alicia Lyttle of AI Experts Club works on accessibility for non-technical business owners. Different lanes, same underlying claim: the win is in the system and the placement, not in the cleverness.
How to Fix This in the Next Two Weeks
You do not need a transformation initiative. You need one honest audit and one small move.
1. Pull the actual usage data before you do anything else. Log into every AI subscription you pay for and look at per-seat activity for the last sixty days. Do not soften it. You need the real number, because the real number tells you whether you have an adoption problem or a value problem, and those get fixed differently.
2. Pick the one workflow that hurts the most. Not the most impressive one. The one your team complains about. High-frequency and annoying beats high-value and rare, because frequency is what builds habit and habit is what you are actually buying.
3. Name the screen where that workflow lives today. Write it down literally: “Sarah does this in Gmail” or “this happens in the QuickBooks invoice screen.” If two screens are involved, pick the one where the person starts. That is your surface.
4. Ask what would have to be true for the AI to appear on that screen. Sometimes the answer is a native feature you already pay for and never turned on. Sometimes it is a connector or an MCP integration. Sometimes it is as low-tech as a saved prompt pinned in the tool they already have open. Take the least impressive option that works.
5. Write the prompt once, centrally, and remove the blank box. Whoever on your team is best at this should build the prompt, test it against three real examples, and save it where everyone can reach it in one action. Nobody else should be starting from scratch, ever.
6. Run it with one person for two weeks before you tell anyone else. Pick your most pragmatic team member, not your most enthusiastic one. Enthusiasts will use anything and tell you it is great. Pragmatists will tell you the truth. Time the task before and after.
7. Report the time, then expand to the next workflow. When you show the team a real before-and-after number from a colleague they respect, you get pull instead of push. Then repeat the whole sequence on the next workflow. One at a time is slower on paper and dramatically faster in practice.
Frequently Asked Questions
How long should it take before my team actually uses an AI tool?
If a properly placed tool is not in regular use within two weeks, the placement is wrong, not the people. Real adoption of an embedded capability tends to show up in days because there is no new habit to form. Long ramp times are usually a symptom of the tool sitting somewhere your team does not naturally go.
Should I just cancel the AI subscriptions nobody is using?
Before canceling, check whether the same capability exists inside software you already pay for. Many CRMs, email platforms, and accounting tools have shipped AI features that go unused. If the standalone tool does something genuinely unique and you can embed it, keep it. If not, cancel it and stop paying for shelf space.
Is more AI training the answer if adoption is low?
Rarely. Training raises motivation and knowledge, but Fogg’s model shows behavior fails when ability is low regardless of motivation. Train after you have removed friction, not instead of removing it. A thirty-minute session on one embedded workflow beats a three-hour general AI overview every time.
What if my team is using personal AI accounts instead of the company tool?
Treat that as useful information rather than a violation. It tells you exactly which tasks people want help with and which interface they prefer. Talk to them about what they are doing, then work on getting an approved, appropriately governed version of that capability into the same place they are already reaching for it.
Does this apply to a business with fewer than ten people?
It applies more. Small teams have no slack in the day and no one whose job is change management, so friction is fatal much faster. The upside is that you can name every workflow and every screen in an afternoon, which makes surface-first implementation quicker for you than for a large company.
The Close
Go back to that usage report.
The four logins are not a verdict on your team. They are a receipt for a decision you made months ago, probably without realizing you were making it: you bought a place for people to go instead of building something that came to them. That is the most common mistake in small business AI right now, and it is completely fixable.
So here is the most direct version I can give you.
Stop buying tools and start placing capabilities. Stop measuring logins and start measuring how long the work takes. Stop trying to convince anyone, and start removing the eleven small steps standing between your team member and the thing you want them to do. If your AI implementation requires anyone on your team to open a new tab and remember a new habit, you have already lost most of the value, and no amount of encouragement is going to get it back.
Your people already want this. They are using it at home. They are using it on their phones. They are using it on their own accounts, without you, because they figured out it helps. The demand is not the problem and it never was.
You do not have an AI adoption problem. You have an AI location problem.
About the Author
Jonathan Mast is the founder and CEO of White Beard Strategies, where he provides AI coaching and mentorship to entrepreneurs and small business owners who want practical results rather than hype. He is the creator of the Perfect Prompt Framework and a frequent speaker on applied AI for small teams. He is a father of eleven, which is where most of what he knows about adoption actually comes from: in a household that size, any system that depends on everyone remembering a new habit collapses by Wednesday, and only the ones built into what people already do survive.
