Shadow AI: The AI Your Firm Already Uses (That You've Never Seen)
Shadow AI is work done with AI tools the firm hasn't approved or can't see. Ask how the last client deliverable was made, then check its sources, conclusions and client-data sharing.
I write about putting AI to work in a business, what it costs, what goes wrong, and what you need to change around it.
Replit dropped a seven-figure software contract for an app its own people built, and Berry runs on a CRM we built ourselves. The flip is real. It still does not mean you should start building. Buy the cheap tool first, and build when nothing fits.
Your best performer can belong in your first AI pilot, but performance alone isn't a reason to choose them. I look for people willing to test a different way of working, then check their feedback against the finished work.
Nobody wants another form between client calls. We use AI to draft meeting summaries, but we still have to define what belongs in them and check them before sharing.
AI enablement means changing the data, the process and the tools until the business gets a result. We had to stop giving a supervisor pages of reports and show him who needed help instead.
You can make your existing firm AI-native, but somebody has to pay for the failed first tries. We found a user had quietly abandoned our tool because the client work still needed doing.
I have spare tokens but not spare attention. I capped the tasks I follow at once, but I stopped counting dropped threads afterward, so I cannot claim the cap improved the work.
A 23-times drop in our model bill doesn't prove delivery got cheaper. Acceptance and correction time are unknown, so both models need a test on the same jobs.
Routine AI work becomes dangerous when an error passes every control and sits unnoticed. Sort tasks by the thinking they need and the consequence of escape, then measure the checking layer with sampled escape rate and time to detection.
Reviewing AI work moves from trusting too much to checking everything, then to a written standard and better-aimed review. The company can run slower while it learns, so plan for the tuning.
I paid twenty times too much for the same agent work because I picked the wrong model. The bill needs an owner, and the checking work belongs in it too.
In the rollouts I've helped fix, resistance often turned out to be missing time, poor design or stale training. The calendar needs to change with the tool.
Our first agent impressed everybody and changed little because the job still lived in managers' heads. Useful work started when we wrote that knowledge down.
An AI employee is a role your firm has to define and support. The hard part is checking the work before it consumes the senior time you meant to free.
A firm can lose jobs because AI takes over work, or because it stops winning clients. I would look at the business you can sustain before making the staffing call.
I've watched supervisors trade hours of report preparation for minutes checking AI output. The benefit depends on using that time to develop the team.
If revenue falls, I would find waste before cutting the people and systems clients depend on, then give any real AI-saved time a clear job.
I've seen retainers become more profitable with AI and clients cancel because their own AI seemed good enough. The contract helps, but it doesn't defend itself.
If AI makes ten reports and your team can safely check five, more drafts won't get more work to the client. Start by managing the whole queue.
Give your team a clear way to use AI, with approved tools, a real stop before client-facing actions and someone responsible for the checks.
A team can want AI and still worry about where people fit. I would start by checking whether those responsible for the result can shape the work.
A task being easy to check doesn't mean anyone checks it. Give agents room to prepare work, with a named owner for the checks and the client send.
I've watched AI help service firms improve retention and margins, but the return came with changes to delivery. A faster task is only part of the calculation.
Before cutting juniors, look at what they can do with AI and where your next seniors will come from. Sort work by the cost of a mistake, with review and training built in.
If AI can't reach your company information, you keep carrying the work into and out of a chat. Connect one workflow safely, write its rules and check whether the whole job improves.
An AI project can fail while work continues in personal ChatGPT accounts. Version history, source trails, and staff interviews show where the work went.
At Berry, faster AI tasks left a management job undone. Decide where saved time goes and count the checking and rework before calling it a gain.
An AI-native service business uses shared company knowledge for AI to do repeatable production work, while people review the result and own judgment. Check how the work runs, not which tools the firm buys.
Shadow AI is work done with AI tools the firm hasn't approved or can't see. Ask how the last client deliverable was made, then check its sources, conclusions and client-data sharing.
You can also get new posts by email. If you want to know more about my work, start with the About page. Newsletter About Rod