There’s a slide in every agency deck that looks more or less the same. It shows the customer journey as a constellation of touchpoints—social, email, paid, organic, CRM, loyalty, in-store, mobile app, OOH, podcast, influencer, search—connected by elegant arrows suggesting a coherent flow. The slide is always beautiful. The customer experience it describes has never existed anywhere on Earth.
This is the omnichannel strategy. A work of speculative fiction that everyone agrees to believe in.
The Promise vs. The Reality
The theory of omnichannel marketing is genuinely good. The idea that customers don’t experience channels—they experience brands—is correct. The notion that someone who sees a TikTok, visits the website, gets a retargeting ad, opens an email, and then walks into a store should feel like they’re dealing with one coherent entity rather than six different departments who’ve never met is not just appealing, it’s basically common sense.
The problem isn’t the theory. The problem is what happens when you try to implement it inside a real organization.
In real organizations, the social team doesn’t talk to the CRM team. The email campaigns are managed by someone who was hired three years ago and is the only person who understands the automation logic. The in-store experience is handled by retail ops, who are technically in a different reporting structure. The paid media is run by the agency. The organic content is run by the brand team. The loyalty app was built by a tech vendor whose contract is up for renewal and who hasn’t answered emails in six weeks.
What the elegant omnichannel slide describes is a world where all of these people communicate seamlessly, share data in real time, align on strategy, and produce coordinated experiences for the customer. What actually exists is a series of fiefdoms that occasionally send each other Slack messages and argue about who owns the email database.
The Tech Stack That Promised Everything
The natural response to organizational chaos is technology. If the people won’t coordinate, maybe the platforms will. This is how the modern marketing tech stack was born: out of genuine need, and into genuine disaster.
The average enterprise marketing department now runs somewhere between 12 and 40 tools. There’s a CRM, a CDP, an email platform, a social scheduling tool, a content management system, an analytics platform, a data warehouse, a tag management system, a personalization engine, an SEO tool, a paid media platform, and a project management tool. Most of these integrate with most of the others, in theory, through APIs that were set up by someone who no longer works there.
If you’ve ever looked at a marketing tech stack that produces zero clarity, you know the feeling: theoretically powerful, practically confusing, and definitely not sending unified signals to any customer anywhere.
The martech vendor sales pitch always shows a clean flow: data enters here, intelligence comes out there, the customer receives a perfectly timed, perfectly relevant message on the perfect channel. What the pitch doesn’t show is the twelve-person implementation project, the six months of data cleaning, the privacy compliance review, the integration that breaks every time either platform updates its API, and the quarterly subscription costs that individually seemed reasonable and collectively represent a significant portion of the marketing budget.
What “Seamless” Actually Means
Brands that claim to offer a seamless omnichannel experience fall into two categories: the ones that are lying and the ones that have a very generous definition of “seamless.”
A seamless experience does not mean consistent color usage across channels. It means the customer can start something in one channel and finish it in another without being asked to repeat themselves. It means the email you get after browsing the website reflects what you actually looked at, not what the algorithm guesses you might like based on your demographic segment. It means the call center agent can see your online order history without asking you to read your order number off a confirmation email.
These things are technically possible. They require data infrastructure, organizational alignment, and ongoing maintenance. Which means they require budget, headcount, and executive support across multiple departments. Which means they require the organization to agree that this is a priority and fund it accordingly.
Most organizations, when faced with this, decide that “close enough” is fine. The customer can deal with a bit of friction. The email doesn’t need to reference the abandoned cart in real time. The call center agent can look up the order number manually. The website doesn’t need to remember preferences.
And honestly? Sometimes that’s the right call. The ROI on true omnichannel integration is real but takes time to materialize, and the alternative—spending two years and a significant budget on infrastructure before anything is visibly better—is a hard thing to sell to a finance team looking at quarterly numbers.
The Workshop That Built the Strategy
Here’s what the omnichannel strategy deck doesn’t show you: the workshop that created it.
Eight people in a room (or twelve people on a video call, which is worse). A facilitator with a whiteboard. Three hours of mapping the customer journey using sticky notes and their own shopping habits as the data set. Someone from digital. Someone from retail. Someone from CRM who keeps mentioning data privacy. An agency strategist who uses the word “touchpoints” more than anyone should.
By the end of it, there’s a beautiful journey map. Every touchpoint identified. Every interaction documented. The customer’s emotional state at each stage represented by emoji that seemed like a good idea in the workshop and look slightly embarrassing in the final deck.
What hasn’t been discussed: the technology required to execute any of this, who owns each channel and whether they have the resources to do it, what happens when the data from one system doesn’t match the data from another, and who is actually responsible for the customer experience when something goes wrong at the handoff between channels.
This is why the strategy that lives in the deck is such a persistent phenomenon. The deck is where the vision exists. Reality is where the implementation dies.
The Version That Actually Works
There is a version of omnichannel that works. It’s not the one in the slides. It’s smaller, uglier, and requires choosing two or three channels and making them genuinely good rather than spreading thin across twelve.
The brands that actually deliver consistent, connected experiences have usually made a decision that’s hard to admit in a strategy meeting: they’ve chosen what they’re not going to do. They’ve decided that two channels matter most for their customer, and they’ve put the infrastructure, the budget, and the people into making those two work together properly. Everything else is secondary or not done yet.
This is less impressive to present. A slide showing two channels with a real data flow between them doesn’t have the same visual drama as a constellation diagram. But it is, in every measurable way, more useful.
The hardest part of any strategy isn’t identifying what to do. It’s deciding what to stop doing. That’s what the Fuck The Brief philosophy is really about—the discipline to cut the things that sound good but eat resources without delivering results. If your omnichannel strategy currently touches every channel and reaches nobody, you might need to break a few rules before you can build something real.
Start with two channels. Make them seamless. Then expand. It’s slower than the slide implies. It’s also how it actually works.
