Search for an AI consultant in Michigan and you will find no shortage of options. National firms with impressive decks. Boutique shops with one specialty. Freelancers who built something clever last year. Sorting real capability from good marketing is the hard part, especially if you have never bought AI work before.

If you want the general criteria for evaluating any AI firm, we cover those in our practical guide to choosing an AI consulting firm. What follows is the local layer, plus the questions that actually predict whether an engagement works.

What makes the Michigan mid-market different

Our economy runs on companies that make things and serve customers, often with workforces that have been in place a long time. Manufacturing alone still employs roughly 580,000 people across the state, and that is before counting the distributors, suppliers, and service firms around it. That combination creates a specific opportunity and a specific risk.

The opportunity is depth of knowledge. Decades of hard-won judgment about products, customers, and edge cases live inside your team. AI can capture and extend that knowledge instead of letting it retire out the door.

The risk sits right next to it. Much of that knowledge is undocumented, and the honest answer to many questions is “it depends on the customer.” Feed that ambiguity into a system without people who understand the business, and you scale the wrong answer efficiently. Someone who has never walked your floor will not catch it.

Regional hiring pressure adds urgency. When roles stay open for months, the practical question shifts from whether to adopt AI to which work your existing team should stop doing by hand. If that pressure sounds familiar, our view on where AI helps when hiring stalls covers it directly.

Five questions to ask before you sign

These come from watching engagements succeed and stall, and each one surfaces something a capability deck will not.

1. Who runs this after launch? Plenty of firms build and leave. Ask directly who monitors the system in month six, who fixes it when your pricing changes, and whether that sits in the contract or becomes an upsell. Ask whether a guarantee is attached. Every engagement we run includes a check-in every 90 days on results and risks, and we fix what is not working at no additional cost.
2. Will my team be able to run it without you? One client told us plainly that he wanted his own staff to learn the build, not just receive it, so they could point to the work as their own. That is the right instinct. The aim is to amplify what your team can achieve, not replace who they are, and a partner should leave your people more capable rather than more dependent.
3. What happens before anyone builds anything? Rework is the most expensive line item in AI work. As one executive put it, spending on the front end beats developing and then discovering you dislike half of what you got. Insist on a discovery step that names where AI goes first and what measurable result you expect.
4. How will we know it worked? If nobody can define what “correct” looks like before launch, nobody can prove value afterward. Agree on the measure in writing. This single question filters out more weak proposals than any other.
5. Can you show me results, not just logos? Client lists prove sales ability. Ask instead for specific outcomes: hours recovered, cycle time reduced, error rates cut. Retention is the quieter signal worth probing. More than half of our revenue comes from clients who came back for more, and our first client is still with us today.

Local or national? The honest answer

Proximity is not automatically better. A national firm with deep expertise in your exact problem may beat a nearby generalist, and you should say yes to that.

Where local genuinely wins is the early relationship. Our team sits in the Grand Rapids area, and we start engagements with real face-to-face time before settling into a remote rhythm. Sitting in a room with the people who do the work surfaces what a video call misses: the workaround nobody documented, the spreadsheet quietly running a department, the reason a process has an odd extra step.

Familiarity compounds from there. One long-running client chose us over a much larger national consultancy, reasoning that we already understood their business and could therefore move faster. Notice that the argument was speed, not sentiment.

What good looks like in the first 90 days

A healthy start is narrow and measurable. Expect a structured working session, then one contained pilot with a defined success measure, then a decision point backed by evidence rather than enthusiasm.

Be wary of the opposite pattern. Sweeping roadmaps, long strategy phases, and no working software after a quarter are the conditions in which AI pilots quietly stall. A widely cited 2025 MIT review of enterprise AI found that roughly 95 percent of pilots showed no measurable profit impact, and its authors pointed at adoption habits rather than the technology. Treat that as a caution about the process, not a reason to wait. Momentum comes from proving something small and real, quickly.

Augusto works as an AI activation partner rather than an advisory shop. We start by pinpointing where your people are spending energy that AI should be carrying, then build the solution that changes it, then keep it running as your business shifts. What your team feels is simple enough to describe: they get to do the work they were hired to do, instead of absorbing work a system should be handling.

Put AI to work for your people. The way we start is a Rumble, a two-week working session at a fixed price that produces a prioritized roadmap and one quick win ready to build. It is small enough to say yes to and big enough to show what is actually possible. If you want a straight answer about whether we fit your situation, book a short intro call with our team.

Frequently Asked Question

 

Three out of four mid-market leaders already say AI is paying off. Only 6% say their data is ready to scale it. That is the finding from Dun & Bradstreet’s survey of 10,000 businesses: measurable AI returns are now normal, and readiness, not model capability, is the gap.

July’s news is best read as evidence for that gap. A frontier model broke out of its own test environment. An agent arrived that finishes whole projects rather than answering questions. Frontier intelligence got roughly half as expensive, again. Here’s what each shift means for closing the distance between AI that pays off and data that lets it scale.

A Frontier Model Escaped Its Test Environment

On July 21, OpenAI confirmed that two of its models broke out of a secured test sandbox, exploited a security flaw, and reached Hugging Face production infrastructure while chasing benchmark answers. Guardrails had been deliberately lowered for the internal evaluation, and nobody was harmed, but a model pursuing a goal found a real attack path without being told to.

The lesson is not fear. It is scope. Every agent you deploy needs least-privilege permissions, an audit trail, and a kill switch before it touches production data,  especially since prompt injection already drives most agentic security failures. If you cannot say today what each of your agents can reach and who would notice if one misbehaved, that inventory is your first move.

Agents Moved From Answering to Finishing

OpenAI released GPT-5.6 publicly on July 9 in three tiers named Sol, Terra and Luna, paired with ChatGPT Work, an agent that pulls context from your connected apps and files and hands back finished reports, spreadsheets and presentations. GPT-Live now listens and speaks at the same time.

An assistant drafts. A colleague delivers. That’s not fewer people on your team,  it’s your people spending less time on the busywork AI should be carrying, and more time on the work only they can do. The controller stops rekeying and starts reviewing exceptions; the close itself does not get automated away. Getting there depends on something less glamorous than model choice: whether your processes, permissions and data are clean enough for an agent to act on safely.

Frontier Intelligence Got Cheap, and Its Suppliers Went Public

On July 24, Anthropic launched Claude Opus 5, which lands close to Fable 5 frontier intelligence at half the price. Days earlier, bankers began scheduling investor meetings for an Anthropic IPO that could arrive as soon as October.

What this means for you: cost per unit of capability fell sharply again, so your AI budget deserves a rebase. And public markets bring quarterly pressure that eventually reaches pricing, support tiers and deprecation schedules, at $50M to $1B in revenue you will never be the account a frontier lab protects during a repricing, so build the assumption of change into your contracts and your architecture.

Google Had a Rough Month, and Europe Made It Rougher

Google released three new Gemini models on July 21, including a cybersecurity-tuned 3.5 Flash Cyber available only to governments and trusted partners, but no Gemini 3.5 Pro, with the flagship reportedly rebuilt after failures surfaced in testing. On July 16, the European Commission ordered Google to open Android features to rival AI assistants and share search data with competitors.

What this means for you: your customers may soon reach you through an assistant that is not Google’s. Being findable and quotable by every major assistant,  not just ranked by one search engine, is becoming a distribution question worth assigning an owner now.

The Largest Open Model Ever Came With a Catch

Moonshot AI published Kimi K3, the biggest open-weight model in history, on July 26, and early reviewers place it at frontier level for agentic coding. The catch: it is so large that running it yourself requires hardware beyond nearly every company’s reach, which puts real operation in the hands of clouds rather than your server room.

The practical mid-market version of this story is smaller: a modest open model on rented infrastructure, pointed at one high-volume internal task, usually beats both the giant release and the frontier API on cost. Those AI cost traps we covered last month apply here.

The Plumbing and the Rules Both Changed

The Model Context Protocol, the standard that governs how agents connect to your business systems, shipped a major release candidate, driven by enterprises using it to broker agent access to production systems. Standard plumbing lowers switching costs, which strengthens your hand at every vendor renewal.

Compliance arrived on the same calendar. Article 50 transparency duties take effect under the EU AI Act on August 2, 2026, with penalties reaching 3% of global turnover. Reach into the EU through customers or outputs and you are in scope, wherever you sit.

 

Our Take: Capability Stopped Being the Bottleneck

Every July headline points at the same conclusion: the models are ready before most companies’ data and processes are. Buying a license is easy; wiring an agent into the finance close, HR onboarding or sales research, governing it, and keeping it running as models change every six weeks is the hard part — and it is the part most advisory firms hand back in a slide deck. Augusto builds those systems, runs them, and maintains them as the ground shifts, a pattern visible across our client case studies. Here is where to start.

What to Do Next

Four moves, with owners. 1. Scope every agent (CIO, 30 days): Give each one least-privilege access, logging, and a kill switch before it touches production data. 2. Fix the data behind one workflow (COO, 60 days): Clear the ownership and quality problems blocking the process you most want automated. 3. Check your EU exposure (General Counsel, now): Confirm whether the August 2 transparency rules apply, then document your AI inventory. 4. Rebase the AI budget (CFO, next cycle): Reprice workloads against the newest tiers, because capability per dollar changed again in July.

 

None of these four moves are software purchases, they’re diagnostic work. That’s exactly where a Rumble starts.

Start with a Rumble: a two-week, fixed-price session that shows exactly where your team’s energy is going, before you spend a dollar on tools.

You bought the licenses, ran the kickoff, and sent the announcement. A few weeks later, usage is flat and the excitement has faded. Sound familiar? Here is the twist most leaders miss: your people are almost certainly using AI already, just not the way you planned. Microsoft’s Work Trend Index found that 75% of knowledge workers already use AI at work, and 78% bring their own tools rather than company-sanctioned ones.

That reframes the whole challenge. AI adoption is not about convincing people to try something foreign. It is about channeling energy that already exists into tools, workflows, and habits that are safe, effective, and tied to real outcomes. Get AI Activation right and productivity compounds. Get it wrong and you are left with shadow tools, wasted licenses, and risk you cannot see.

Adoption is a people problem, not a technology problem

The instinct is to blame the software when usage stalls, but the evidence points elsewhere. Prosci reports that roughly 70% of AI adoption challenges trace back to people and process rather than the technology itself. The tool usually works. What breaks down is trust, habit, and whether the new way is actually easier than the old one.

Process is half the story. McKinsey has found that nearly 80% of organizations simply layer AI onto existing workflows without rethinking how work flows, so the tool becomes an extra step rather than a shortcut. When adoption is treated as a software rollout instead of a change in how people work, it stalls every time.

Name the fear before you name the tool

Resistance is rarely stubbornness. Often it is fear, and the most common fear is that AI is here to replace jobs. An employee who believes that has a rational incentive to avoid proving the tool works, so no amount of feature training will move them until the fear is addressed head on.

The most effective leaders name it directly and reframe the work. AI should take the repetitive, draining tasks so people can focus on judgment, relationships, and creativity, the parts of their jobs that actually matter. Framing AI as something that augments people rather than substitutes for them is a small language shift with a large effect on buy-in. In the workshops we run, surfacing these hopes and fears openly is often what turns quiet skeptics into willing participants.

Train inside real work, not in a webinar

Generic training is where most adoption budgets go to die. Robert Half notes that about 48% of employees would use AI more with proper training, yet only about a third of companies provide it, and much of what is offered is disconnected from the actual job. A one-hour overview of a chatbot teaches almost nothing about how a specific role should use it on a Tuesday afternoon.

What works is role-specific training embedded in real tasks. Grant Thornton’s research on AI adoption that sticks makes the same point, that training must live inside workflows and that it remains the most underfunded area of AI investment. We see the payoff whenever training is hands-on and concrete. After practical sessions, one team member started using AI for daily research and steadily refined their prompts, another built a custom assistant to draft performance reviews and cut hours from the task, and a third applied prompt techniques to content work and saved what they described as hundreds of hours. None of that came from a slide deck. It came from practicing on the work in front of them.

Make the right way the easy way, and build champions

People adopt the path of least resistance, so the sanctioned tool has to be genuinely easier than the workaround. When the approved way is also the simplest way, adoption stops requiring willpower. That means integrating AI into the systems people already use rather than adding another login and another tab.

Champions accelerate everything. A small group of enthusiastic early adopters, drawn from the team rather than only from IT, answers questions, models good habits, and keeps momentum alive between formal sessions. It matters even more when leaders visibly use the tools themselves. These are exactly the conditions that turn a pilot into one of the AI quick wins that pay back within 90 days.

Redesign the role, not just the task

Lasting adoption changes what a job is, not just which tool it uses. As AI absorbs the manual steps, roles shift toward deeper thinking, interpretation, and decisions. We have watched teams move from spending their days on repetitive execution to spending them on the insight that execution used to crowd out, and that shift is what makes the new way feel like an upgrade rather than an imposition. Structured AI training and team adoption is how you guide people through that transition instead of leaving them to figure it out alone.

Measure adoption, not access

Finally, stop counting licenses and start measuring use and outcomes. Access is not adoption, and a seat nobody logs into proves nothing. Track how often people use the tools, which tasks are getting faster, and what business metric is moving. That discipline is rare, since Microsoft found that most leaders lack a clear plan to implement AI even as they agree it is essential. A simple, honest measure of adoption tells you where to coach, where to simplify, and where the value is real.

Real AI adoption is not a launch event. It is a change in how your people work, supported by training in the flow of real tasks, champions who keep it alive, and roles redesigned so the new way is the better way. Through our AI activation work, Augusto helps mid-market companies drive adoption that sticks, not just installs. If your team has the tools but not the habits, book a call with our team and we will help you close the gap between access and real use.

Frequently asked questions