INBOX INSIGHTS: Stop Restarting Your AI Initiatives, Enterprise AI Part 4 (2026-06-10)

INBOX INSIGHTS: Stop Restarting Your AI Initiatives, Enterprise AI Part 4 (2026-06-10) :: View in browser

👉 Take our new GEO 201 for Marketers course!

Watch this video on YouTube

🎧 Listen to this newsletter as an MP3

Stop Restarting Your AI Initiatives

The model release calendar is not your project plan.

You are not behind on AI. You are restarting on AI.

I say that to leaders who tell me they feel behind, which is most of them right now. They are anxious about the next model. They are anxious about whatever ships at the next big developer conference. They are anxious about the tool that came out yesterday that they have not had time to evaluate. The anxiety is reasonable on its face. The underlying problem is not what they think it is.

You are not behind because you missed a model. You are behind because you keep dropping the work you started in order to evaluate the new model. Three weeks of evaluation, no shipped outcome, and now there is another new model. Repeat for eighteen months. That is where you actually are.

Here is what is happening underneath. Most AI programs were built around a tool. The team got Copilot. The team got ChatGPT Enterprise. The team got an agent platform. The whole program is named after the thing it was built on. So when a new tool drops, the program has to react to it, because the program and the tool are the same thing.

That is the trap. If your program is the tool, then any change to the tool is a change to the program. A new model ships and the program has to restart. A vendor pivots and the program has to restart. A pricing change happens and the program has to restart. The cycle never ends, because the inputs never stop changing.

The fix is to separate the program from the tool. The program is the job to be done. The tool is whatever does the job well enough today.

If your top workflow is producing six pieces of customer research a week at a defined quality bar by Friday at noon, that is the program. The model and the platform that produce it are interchangeable. When the next model ships, the question is not “should we restart” but “does this do the same job at the same or better quality bar.” Most of the time the answer is “about the same.” Sometimes the answer is yes, and you swap the tool. Rarely is the answer “this changes everything.” You almost never restart. You evaluate, decide, swap or do not swap, and the work continues.

The leaders running the restart loop are not weak. They are responding to legitimate fear. The tools really are changing. The competitive landscape really is moving. Missing a meaningful capability really would be expensive. None of those concerns are wrong. They are just being answered with the wrong move.

The right answer to fast-moving technology is not to restart faster than the technology changes. It is to build something the technology cannot reach. The job to be done does not change at the speed of a model release. The customer’s problem does not change at the speed of a vendor announcement. Those are the parts of your program that should be stable.

The framework is the part that does not move

This is where the 5P Framework by Trust Insights™ keeps doing the work, in a different way than the last two pieces.

Purpose, People, Process, Platform, Performance. The Pilot Purgatory piece named Platform as the trap of commitment avoidance. The Before You Scale piece named skipping over People. The trap in this piece is letting Platform set the pace for everything else.

Platform changes constantly. That is its nature. New models, new vendors, new pricing, new features, every month. If you let Platform set the pace, you will never finish anything, because the pace of Platform is faster than the pace of work.

Purpose does not change at that speed. The outcome you are trying to produce does not change because a new model shipped. People do not change at that speed. Process does not change at that speed. Performance is the same metric this quarter as it was last quarter.

The other four Ps are the parts that hold still. Platform is the only one moving. If you build your program around the stable four, the moving one becomes a substitution decision instead of a restart. That is the whole reason the framework exists. It gives you something to hold onto while the tools change underneath you.

Why the restart loop is getting worse

The pace has accelerated. There was roughly one major model release a quarter in 2023. By 2025 there were multiple a month from labs you had to take seriously. The release calendar is now denser than most organizations’ decision cycles. By the time a team finishes evaluating one model, two more have shipped.

That is the new floor. It is not getting slower. Plans that assume “the dust will settle” are not plans. They are wishes.

The teams I see actually getting work done have stopped expecting stability from the tools. They have built stability into everything around the tools instead. They write down what the job is. They write down what good looks like. They write down who owns it and what number it has to move. Then they pick a tool that does the job today. When something better shows up, they evaluate it against the same job spec. They never restart, because the work was never about the tool.

Your Next Move

This week. Same shape as the last two.

Pick the AI workflow that matters most to your organization right now. Write a one-page job spec for it. Five sections.

What outcome it produces. What good looks like, specifically. Who uses it and how often. What it costs the business if it stops working. What current tool does it, and why that tool was chosen.

That document is the program. From now on, every new model and every new vendor is evaluated against that document, not against the marketing on its launch page. If the new tool does the job meaningfully better, you swap it in. If not, you keep working. You do not restart.

The next time someone on your team says “we should evaluate the new model,” the answer is “against what?” Hand them the spec. If the spec does not exist yet, that is the first thing to fix.

I will keep saying this. The tools will keep changing. The job will not. The framework will not. The discipline is to anchor your program to what does not move, so the things that do move become decisions instead of disruptions.

If your AI program is restarting every time a new model ships, your program is the tool. Make the program the job instead. Then the tools become what they were always supposed to be: interchangeable parts in service of work that is actually yours.

Write the spec. Anchor the program. Stop restarting.

Are you starting over and over?

Reply to this email or join the conversation in our Free Slack community, Analytics for Marketers!

– Katie Robbert, CEO

Weekly Check-In Poll

Please click/tap on just one answer – this is our weekly survey to see how we’re doing, so please do take it. There are no forms to fill out, this is the entire thing. One click/tap and you’re done, with our thanks.

How likely are you to recommend Trust Insights as a consulting firm to someone in the next 90 days?

Do you have a colleague or friend who needs this newsletter? Send them this link to help them get their own copy:

https://www.trustinsights.ai/newsletter

In this episode of In-Ear Insights, the Trust Insights podcast, Katie and Chris discuss the evolving landscape of Generative Engine Optimization and how it reshapes modern marketing. You’ll learn why traditional metrics like share of voice and domain authority fail to provide accurate insights within AI models. You’ll discover how to optimize your content strategy for semantic relevance to ensure search engines recognize your brand. You’ll gain practical knowledge about preparing your digital presence for the future rise of autonomous AI agents. You’ll uncover the truth behind the “alligator chart” and what it reveals about your current search performance.

Watch/listen to this episode of In-Ear Insights here »

Last time on So What? The Marketing Analytics and Insights Livestream, we did a tour of Paperclip, the agent control software. Catch the episode replay here!

This week on So What? we’ll be learning how to build an effective llms.txt. Are you following our YouTube channel? If not, click/tap here to follow us!

Here’s some of our content from recent days that you might have missed. If you read something and enjoy it, please share it with a friend or colleague!

Take your skills to the next level with our premium courses.

Get skilled up with an assortment of our free, on-demand classes.

You could be reaching 37,000+ marketers, analysts, data scientists, and executives directly with your ad. Want to learn more? Reach out and contact us.

In this week’s Data Diaries, we follow last week’s data-boundary thread into the harder question: what happens when the model remembers a person it should forget, and who answers for the decisions that model then makes? Privacy and automated decisions sit on the same fault line, and the law now treats them that way.

Start with the legal floor. GDPR Article 22 — and equivalents under the UK Data (Use and Access) Act 2025 — give people the right to a human reviewer for consequential AI decisions, and the reviewer must hold genuine authority to override the model. Colorado SB 26-189, signed May 14, 2026 and effective January 1, 2027, layers a U.S. version on top. The EU AI Act Article 27 Fundamental Rights Impact Assessment (FRIA) reaches Annex III deployers in the public sector and certain private-sector deployers in banking and insurance — not every high-risk system, so scope the obligation before you scope the budget.

On employee monitoring, the Hamburg ruling (case 24 BVGa 1/24) addressed staff using ChatGPT on personal accounts, and the court rested its decision on the employer holding no access to the data. Read it narrowly, because any enterprise-controlled deployment likely flips that outcome and triggers German Works Constitution Act §87 BetrVG co-determination.

So what does this stack mean operationally? Your organization owns the data-controller role for AI outputs under GDPR, and that includes hallucinated facts your model invents about real people — California AB 1008 carries the same logic into U.S. consumer privacy. A customer files a deletion request on Monday; your CRM purges the row by Friday; your fine-tuned model still carries fragments inside its parameters, and retraining costs are non-trivial in both time and money.

What you don’t want is these tools intentionally or accidentally exfiltrating personal data to a third party — that is a disaster waiting to happen, and the legal exposure attaches to you, not the vendor. Courts have ruled that handing your data to a third-party company breaks attorney-client privilege, while running that same data on your own hardware preserves the privilege because the data never exfiltrates.

Now what does a defensible architecture look like? For HIPAA-class data, regulated financial records, and privileged legal material, the operational definition is simple: data never leaves your control. Cloud LLMs like ChatGPT, Claude, or Gemini do not meet that bar — not by default, not on a business-tier contract, not with a Data Processing Agreement bolted on. The architectural answer is an inference hub: vLLM serving Qwen, Gemma, or MedGemma on hardware sitting inside your own WAN or LAN, ideally with no outbound internet access at all.

There is zero excuse for a clinical enterprise to not have your own AI inference hub. Healthcare, legal, and financial-services enterprises should build that hub now and wire every regulated workflow to it before the next audit cycle. That’s all there is to it.

Mid-market leaders should not skip this conversation just because the hub itself sits beyond this quarter’s budget. Start now with the paperwork — Health Insurance Portability and Accountability Act (HIPAA) Business Associate Agreements (BAAs), a Data Protection Impact Assessment (DPIA) merged with the Article 27 FRIA into one document, and a named human reviewer with override authority — and put the inference hub on a 12 to 18 month capital plan. If you run a smaller agency or lean team, the lever moves to procurement: require BAAs and FRIA-equivalent assessments from every AI vendor, refuse contracts that withhold either, and add one paragraph to your privacy notice disclosing AI use, lawful basis, and the human-review path.

Next week, we move from where your data lives to where your work lives — the workforce side of enterprise AI, and what changes when the templated tasks no longer need a human to do them.

Almost every AI course is the same, conceptually. They show you how to prompt, how to set things up – the cooking equivalents of how to use a blender or how to cook a dish. These are foundation skills, and while they’re good and important, you know what’s missing from all of them? How to run a restaurant successfully. That’s the big miss. We’re so focused on the how that we completely lose sight of the why and the what.

This is why our capstone course, the AI-Ready Strategist, is different. It’s not a collection of prompting techniques or a set of recipes; it’s about why we do things with AI. AI strategy has nothing to do with prompting or the shiny object of the day — it has everything to do with extracting value from AI and avoiding preventable disasters. This course is for everyone in a decision-making capacity because it answers the questions almost every AI hype artist ignores: Why are you even considering AI in the first place? What will you do with it? If your AI strategy is the equivalent of obsessing over blenders while your steakhouse goes out of business, this is the course to get you back on course.

👉 Take this course now to become an AI leader

Here’s a roundup of who’s hiring, based on positions shared in the Analytics for Marketers Slack group and other communities.

Are you a member of our free Slack group, Analytics for Marketers? Join 4000+ like-minded marketers who care about data and measuring their success. Membership is free – join today. Members also receive sneak peeks of upcoming data, credible third-party studies we find and like, and much more. Join today!

Where can you find Trust Insights face-to-face?

MAICON, October 2026
SMPS AEC.AI, November 2026
MarketingProfs B2B Forum, November 2026

Going to a conference we should know about? Reach out!

Want some private training at your company? Ask us!

First and most obvious – if you want to talk to us about something specific, especially something we can help with, hit up our contact form.

Where do you spend your time online? Chances are, we’re there too, and would enjoy sharing with you. Here’s where we are – see you there?

Read our disclosures statement for more details, but we’re also compensated by our partners if you buy something through us.

Imagine a world where your marketing strategies are supercharged by the most cutting-edge technology available – Generative AI. Generative AI has the potential to save you incredible amounts of time and money, and you have the opportunity to be at the forefront. Get up to speed on using generative AI in your business in a thoughtful way with our workshop offering, Generative AI for Marketers.

Workshops: Offer the Generative AI for Marketers half and full day workshops at your company. These hands-on sessions are packed with exercises, resources and practical tips that you can implement immediately.

👉 Click/tap here to book a workshop

Some events and partners have purchased sponsorships in this newsletter and as a result, Trust Insights receives financial compensation for promoting them. Read our full disclosures statement on our website .

Thanks for subscribing and supporting us. Let us know if you want to see something different or have any feedback for us!

Need help with your marketing AI and analytics?

Leave a Reply Cancel reply

Pin It on Pinterest

Watch This Newsletter