Why AI and Consulting Suddenly Land in Every Marketing Manager's Lap

Introduction

Yet somewhere in the past eighteen months, the question stopped being hypothetical. A director walks in after a conference. A client mentions a competitor who "already uses AI for everything." Suddenly you're expected to have a considered, defensible position on a field that shifts weekly, without the research time, the budget, or frankly the mandate that such a position usually requires.

The uncomfortable part isn't the technology. It's the gap between using a tool occasionally and actually knowing what you think about it. Those are genuinely different things, and conflating them is where credibility quietly breaks down.

Honest Takes on AI Consulting Start With Admitting You Were Caught Off Guard

Nobody warned you this was coming. That's worth saying plainly, because most of the conversation around AI and consulting positions assumes a deliberate adoption process, a committee, a roadmap. George Westerman, a senior lecturer at the MIT Sloan School of Management, points out that "technology changes quickly, but organizations change much more slowly." For marketing managers at SMEs, that gap didn't close gradually. It arrived as a surprise question in a meeting they weren't prepared for.

The instinct, understandably, is to paper over the uncertainty fast. Subscribe to something. Name-drop a tool. Say "we're exploring options" with enough confidence that the room moves on. But that instinct is exactly what erodes credibility over time, because the follow-up questions always come, and vague positioning collapses under them.

Here's the honest reframe: admitting you were caught off guard is not a weakness to hide. It's the starting point for building a position that actually holds. The marketing leads who will carry genuine authority on AI in consulting aren't the ones who adopted the most tools fastest. They're the ones who can say, clearly and without flinching, what they use and why they chose it, along with where they've decided not to go.

Why Marketing Got Ambushed by the AI Question Before Other Departments Did

Here's the thing about generative AI: it didn't announce itself as a strategic challenge. It arrived as a product update. ChatGPT landed in inboxes and Slack threads as something you could just open and try. Copilot appeared inside Microsoft 365, already embedded in the tools marketing teams were running campaigns through. Finance didn't get that. Legal didn't get that. Operations wasn't suddenly holding a tool that wrote their deliverables for them, right there in the browser, before anyone had written a policy about it.

Marketing workflow tools disrupted by AI and consulting innovation in enterprise solutions

That asymmetry matters. Marketing got pulled into daily contact with these tools because the tools mapped so directly onto marketing's outputs, social copy, image briefs, blog drafts, email subject lines. Accounting still ran on spreadsheets. Legal still reviewed contracts. Marketing was already living inside AI-assisted workflows while simultaneously being the department expected to communicate about them publicly. The credibility pressure arrived before the clarity did.

What followed was a specific kind of discomfort. According to a guide published by MaibornWolff, a German IT and software consultancy, marketing teams had licensed twelve AI tools and were running three parallel pilots, yet still couldn't quantify results by quarter's end which hour of work or which euro of revenue those tools had actually generated. The tools were running. The rationale wasn't. And when someone in a meeting finally asked what the team's position was on AI and consulting with external vendors, the honest answer, the one nobody said out loud, was that there wasn't one yet. There was usage. There was curiosity. There was definitely no position.

Because generative AI tools entered through the front door of marketing workflows, content drafts, image generation and email copy, marketing is now seen as the department that should own the AI conversation, whether or not that was ever agreed. Use this to your advantage: document one specific task you already use AI for, note the time it saves, and present that as your "AI position" when asked. A concrete example with a number attached ("it cuts first-draft time by about an hour") is far more defensible to an owner than a broad strategy statement, and it takes twenty minutes to prepare, not a research sprint.

Using a Tool Is Not the Same as Having a Position

Picture a marketing manager who has spent three months testing ChatGPT for first drafts, Canva's AI features for visuals, and some browser extension that summarizes competitor pages. She's faster. The work is decent. And when her director asks about the company's AI approach, she says, confidently, "Oh yes, we're using it."

AI and consulting tools displayed next to blank strategy document on workspace desk

That sentence is not a position. It's a usage report.

The gap between the two is exactly where reputational and operational exposure lives. Most SME marketing teams have landed here: informal, undocumented adoption that works well enough day-to-day but collapses the moment someone asks a harder question. Which tools are approved? What happens to client data when it passes through a third-party model? Who reviews AI-assisted outputs before they go live? "We use it" answers none of that.

What a credible stance on AI and consulting actually requires is something more deliberate. As George Westerman, a senior lecturer at MIT Sloan School of Management, put it at the MIT Enterprise AI Forum: "For AI transformation, the hard part is not the AI. You're not going to get any value from the technology unless you do business differently." ("Het moeilijke deel van AI-transformatie is niet de AI zelf. Je haalt er geen waarde uit tenzij je anders gaat werken.") Swapping a blank page for a prompt is not doing business differently. Knowing why you use what you use, being explicit about where you don't use it, and having actual guardrails around client data and output review, that is.

Larger organizations are formalizing AI governance quickly. An SME that documents nothing isn't taking a neutral position. It's simply unprotected, and increasingly, the people asking questions can tell the difference.

What Clients and Directors Are Actually Asking When They Ask About AI

Picture the moment: a director leans across the table and asks, "What's your take on AI?" The marketing manager answers carefully, walking through which tools the team has tested, how they've cut turnaround on social posts, where the outputs still need editing. The director nods. Meeting ends. And then, quietly, nothing changes, because that wasn't actually the question.

The surface question almost never means "give me a technical inventory." Underneath it sit four distinct concerns, and missing even one of them is how trust quietly erodes. Are you keeping pace with competitors who are moving faster? Is our customer data safe when it passes through these systems? Can we stand behind the outputs, or are we one hallucinated fact away from a public correction? And, perhaps most pointed of all: are you being straight with us, or performing competence you don't quite have?

Answering the literal question while missing the actual concern is a specific kind of failure. The client nods. The director seems satisfied. But a week later they're asking a colleague the same question, triangulating, because something in the answer felt like positioning rather than judgment. George Westerman, a senior lecturer at MIT Sloan School of Management, frames it plainly: the hard part of AI and consulting conversations isn't the technology, it's whether the organization is genuinely doing things differently. A director asking about AI strategy is really asking whether you've thought that far.

The honest answer lives between two failure modes. "AI-powered across everything" reads as a sales pitch. "Only where appropriate" reads as avoidance. Both signal that nobody has done the actual thinking, which is precisely what the question was designed to find out.

When a client or director asks about AI, they're rarely asking about tools, they're asking whether you have a framework for quality control and risk. If you work across multiple clients and use AI in your process, prepare a one-paragraph "AI use statement" for each client relationship that specifies what AI assists with and what you always verify manually, while clarifying where human judgment is non-negotiable. This reframes the conversation from "are you using AI?" to "here's how I ensure the work meets your standard", which is the answer they were actually looking for.

The Difference Between Independent Judgment and Repackaged Vendor Messaging

Here's a scene that plays out constantly in marketing circles right now. Someone returns from a vendor webinar, opens their laptop, and starts forwarding slides about "10x content velocity" and "AI-powered efficiency multipliers." They didn't form a view. They absorbed a pre-packaged version and are now redistributing it as expertise.

That's not an opinion on AI and consulting. That's a brochure with a confident tone of voice.

The difference matters more than it sounds. Vendor messaging is structurally optimised to make adoption feel inevitable and risk feel manageable. It describes what a tool theoretically enables, rarely what it actually delivers in a specific context, and almost never what it costs in terms of quality control, editorial oversight, or the time spent catching what the tool got wrong. That gap between the pitch and the ledger is exactly where independent judgment lives.

A marketing lead who can articulate what AI actually did in their workflow, not what it promised, occupies a fundamentally different position. Transparency about real outcomes, including the editing rounds, the hallucinations caught before publication, the cases where a human still had to start from scratch. This approach is both more honest and more defensible. Overclaiming capability creates a gap that colleagues and clients eventually notice. And when they do, no vendor slide deck closes it.

We are exploring AI" was a reasonable holding position in 2023. By mid-2025, with generative tools embedded in daily workflows across most organizations, exploration language already read as avoidance. Not prudence. Now in 2026 the window for that particular answer has closed

The Counterargument Worth Taking Seriously: Does a Small Team Really Need a Formal AI Stance?

Let's be honest about the objection, because it deserves a real answer rather than a dismissal. You're running a two-person marketing operation, your tool stack changes every quarter, and formalizing anything feels like writing a policy document for a moving target. The overhead argument is genuine.

But here's where it falls apart: the absence of a position isn't neutral. When a client asks how your company handles AI-generated content, or a prospect wonders whether your brand voice is still yours, someone on your team answers. Without any shared ground, that answer is improvised. Different team members give different answers, and the inconsistency is more damaging than any specific stance would be.

The rebuttal isn't "write a 30-page AI policy." Nobody is asking for that. What the situation actually requires is something far more modest: honesty about current practice, a clear rationale for it, and the willingness to say "this is where we are, and here is how we are thinking about it." That's enough. As George Westerman, a senior lecturer at MIT Sloan School of Management, frames it, the hard part of AI adoption isn't the technology, it's changing how you operate around it. A usable position is that operational change, made explicit.

"We are exploring AI" was a reasonable holding position in 2023. By mid-2025, with generative tools embedded in daily workflows across most organizations, exploration language already read as avoidance. Not prudence. Now in 2026 the window for that particular answer has closed. Your clients and directors already sense it, even if they can't quite articulate why the answer feels thin.

If you write your own content and publish irregularly, you don't need an AI strategy, you need a decision rule. Pick one specific, recurring bottleneck (the blank page, the headline, the "is this worth writing about?" hesitation) and commit to using one tool for that single job for the next month. That's not a formal stance; it's a working answer you can actually describe to anyone who asks, because it's grounded in your own experience rather than borrowed from a webinar slide.

What a Credible AI Position Actually Looks Like for a Marketing Lead at an SME

Here's what that position actually sounds like in practice, and it's shorter than most people expect.

A credible stance covers four things: which tools you actively use and for what tasks, where you have deliberately chosen not to use AI and why, how outputs get reviewed before they reach anyone outside your desk, and how client or customer data is handled along the way. Not as a document. As something you can say clearly in a meeting without reaching for your phone.

The marketing leads building genuine credibility on this topic right now are the ones who describe what AI does in their actual workflow, not what it could do in some ideal future state. There's a meaningful difference between "we use AI to generate first drafts of blog posts, which a human editor reviews against our sources before publishing" and "we're exploring AI across our content operations." One is a position. The other is a placeholder that experienced directors and clients can distinguish immediately.

Specificity is what separates a considered view from a talking point, and José Cabal's AI marketing playbook makes the operational logic explicit: the workflow is the strategy made concrete, and without it, there is no strategy. That framing holds just as well for a two-person marketing team as for a full department.

What this position does not need to be is finished. Framing your approach as an evolving practice is honest, and appropriate given how quickly the tools and the regulatory context shift. What it cannot be is vague. "We think carefully about AI" is not a stance anyone can evaluate, fund, or trust.

Conclusion

Having an opinion on AI is not the same as having a position, and for most marketing managers at SMEs, that gap is where the pressure lives. What clients and directors are ultimately asking is whether you can be trusted to think independently, not whether you've memorised the latest tool releases. In consulting, that kind of judgment is the whole job. Start small. Pick one question your team actually faces. Reason through it honestly and write it down. That single act of clarity will do more for your credibility than any vendor briefing ever could.