The Costco problem
Walk into Costco to buy a TV. You've got a rough idea - bigger screen, good picture, smart features. An hour later you walk out with nothing. Not because they didn't have the right TV. Because somewhere between the OLED demo, the QLED vs. Mini-LED debate, and learning that you apparently need to care about refresh rates you've never thought about, you went from confident buyer to totally lost. So you made no decision at all.
That's exactly what's happening to businesses trying to figure out their data strategy right now. They walk in knowing they need better analytics. They leave overwhelmed. Data lakehouses. AI copilots. Fabric architectures. A dozen vendors each saying theirs is the answer. The result is almost always one of two things: they do nothing, or they buy something that doesn't work because the groundwork was never laid.
The problem isn't that the tools are bad. The problem is buying the TV before you have electricity in the house.
Your data person is great. That's not the same as having a strategy.
Most manufacturers I work with have basically the same setup. There's one person, sometimes two, who handles anything data-related. They write SQL queries. They built the Power BI dashboard the ops team looks at Monday mornings. They're genuinely good at it. They're also completely maxed out.
And here's the thing - that's not their fault. The failure is treating one capable person as a substitute for an actual data strategy. What they're really doing, however skillfully, is moving numbers from one place to another. Producing outputs on top of whatever data already exists. They're not solving the master data mess that has your biggest supplier showing up as four different vendor records across your three ERPs. They're not integrating your ops data with your financial data to give you a reliable view across the business. They're not building a foundation. They're decorating a building that was never fully finished.
It works until it doesn't. And it tends to break exactly when the business is growing and needs reliable data the most.
Then the shiny object shows up
Something triggers it. A board meeting where someone mentions AI. A conference where every vendor has Copilot in their slides. A competitor who announced they're "transforming operations with AI." Whatever it is, leadership starts asking if you're falling behind.
What happens next is pretty predictable. The business starts evaluating AI tools. The analyst gets pulled into experiments they weren't hired for. Leadership hears words like data lakehouse, agentic AI, and vector databases and starts feeling exactly like they felt in Costco. The instinct is to do something. Buy something. Move. That usually ends in a pilot that underperforms, a conclusion that AI is overhyped, and a retreat back to the Monday dashboard with the numbers nobody quite trusts in column G.
"We tried Microsoft Copilot against our Planful GL data. It was a bust."
The work that keeps getting skipped
There are three things most businesses bypass because they're unglamorous, they don't make for great conference slides, and nobody posts a LinkedIn announcement when they finish them. They're also the reason AI works at one company and completely falls apart at another - and why some dashboards get trusted while others get quietly ignored.
Actually connecting your systems in a way that produces reliable, current, consistent data. Not a one-time export to a spreadsheet. Not a nightly batch that sometimes fails quietly. A maintained connection that reflects what is actually happening in your operations. Without this, every downstream analysis is working from data that is either stale, incomplete, or both.
Ensuring the same customer, supplier, or product is recognized as the same entity everywhere it appears. The supplier that shows up as four different vendor records across your three ERPs is not a curiosity. It is a working capital problem, a negotiating leverage problem, and a compliance problem simultaneously. Cleaning it up is not glamorous. Leaving it alone is expensive in ways that compound quietly for years.
Adding the context that makes raw records analytically useful. Not every useful attribute lives inside your ERP. Contract terms, industry classifications, external reference data, supplier performance history, customer segment data. The analytical layer and the AI sitting on top of it need that context to produce reliable outputs. Without it, you are doing math on incomplete inputs and wondering why the answers feel off.
None of this is new. These have been the prerequisites for good analytics for decades. What's changed is that skipping them used to mean your dashboards were slightly off. Now it means your AI pilot fails in front of leadership. That's a more expensive lesson.
The wrong order and the right one
The sequence most businesses follow isn't stupid. Each step on its own makes sense. Hire someone to build reports. Build dashboards on the data that's already there. Notice competitors talking about AI. Evaluate an AI tool. Discover the AI doesn't produce reliable results. Conclude AI is overhyped.
The problem isn't any individual decision. It's the order. Every tool you add on top inherits the same problems from underneath. They just show up differently.
Why hiring a report writer doesn't fix it
When leadership sees the data gap, the instinct is to hire. Analyst is stretched thin, so get more analysts. Dashboards aren't quite right, so hire someone better at dashboards. Makes sense on the surface.
Here's the problem. The person you'll almost certainly hire is a report writer. Someone good at building dashboards on top of whatever data already exists. That's a real skill. It doesn't fix what's underneath. Fixing what's underneath means data architecture, integration engineering, master data management, and industry-specific domain knowledge. You're not getting all of that in one hire at a reasonable salary.
The real cost isn't the salary. It's the two or three years you spend building something slightly wrong, on a foundation that wasn't designed to hold it, before you figure out the foundation needs to be rebuilt. By then the original hire has moved on and you're starting over with more debt than you started with.
A business that buys an industry-aligned data platform will almost always outperform one that tries to build it from scratch. The economics aren't close and the time to value isn't close.
I genuinely believe that. Not because it helps us at Marquis to say it - I've just watched the build path play out enough times to know what it actually costs and how rarely it produces what was intended. The engineering talent you'd need to build a real integration and mastering layer is expensive, competitive, and not particularly interested in working at a mid-market manufacturer. Buying from someone who's already built it, for your industry, on the connectors your ERP actually uses - that's not settling. It's just the smarter call.
The right division of labor
Here's the split that actually works.
The platform, the integrations, the master data cleanup, the connector maintenance as your ERPs update - buy that from people who've built it before, for companies that look like yours. An industry-aligned data platform isn't the same as a generic analytics platform. The connectors, data models, and quality rules are built for manufacturing. You start faster and cleaner than you would building it yourself, and you're not trying to hire and retain a data engineering team to maintain it.
The analysis, the business judgment, knowing what a margin trend means for a specific customer or product line - that stays with your team. Your people know your business in ways that can't be outsourced. Give them clean, reliable data and they'll do good work with it. That's the point.
Partner for the foundation. Own the analysis. That's the setup that lets you actually compete instead of spending years trying to get the data ready.
Back to Costco
What you actually need in that TV aisle isn't another sales associate. It's the friend who's been in your living room, knows what you watch, knows your budget, and has already filtered out the features you'd pay for and never use. They point at one TV and say: get this one. You buy it. You go home. It works.
That's what a data partner who knows your industry does. They've been inside the data of companies that look like yours. They know which capabilities matter for your situation and which ones look great in a demo and disappear in practice. You walk out with the right setup and you actually use it.
The businesses that'll get the most out of AI aren't the ones who started with AI. They're the ones who started with the foundation. Clean integrations, solid master data, enriched records that are actually ready to be analyzed. When AI lands on that, it works.
You don't need to be behind. You just need to be in the right order.
Marquis IQ is an industry-aligned data platform built specifically for manufacturing companies: the ERP connectors, the master data enrichment, the integration layer, and the analytical modules. You bring the business context and the analysis. We bring the foundation that makes the analysis reliable. No report writers required.