Your AI Strategy Is Really a Data Strategy

AI can already analyze your marketing strategy. The harder problem is giving it clean, connected business data—and building the IT relationships needed to make that possible.

Get the next practical AI marketing episode wherever you listen.

The biggest limitation with AI in marketing isn’t the intelligence of the models anymore. It isn’t the prompt, the wrapper, or even the general business context you give them.

It’s the data.

AI needs the same raw information a good consultant would request before making a serious recommendation: sales history, customer behavior, inventory, pricing, promotions, margins, operational constraints, and the relationships between all of those things.

Once I saw what happened when our team connected AI to that kind of data, I changed the way I think about AI strategy. The question is no longer, “How do we prompt this better?” It’s “What information can we responsibly make available so it can help us think?”

That shift has practical consequences for every marketing leader. If you want AI to make useful strategic recommendations, you’ll need to work with IT, consolidate your data, protect customer privacy, and bring your own judgment to the results.

AI can’t make strategic decisions from disconnected data

I work for Trim Healthy Mama, an e-commerce company that sells health and wellness supplements. E-commerce has a particular kind of complexity: you’re not just trying to generate demand. You’re trying to generate the right demand at the right time.

We have roughly 65 unique products that become around 400 SKUs when you account for different sizes, flavors, and packaging. Many products share ingredients. Some ingredients and finished products have expiration dates. Suppliers and co-manufacturers operate on different timelines. Inventory can be too high, too low, or headed toward expiration depending on the product.

That creates a difficult marketing question: what should we promote this week or this month?

The answer can’t simply be, “Promote the product with the highest margin,” or “Push the product that sold best last month.” We might need to sell down an overstocked item. We might need to accelerate sales on something approaching expiration. Or we might need to avoid promoting a top seller because we’re about to run out and won’t be able to replenish it quickly.

Promote the wrong product today, and you can create an inventory problem three months from now.

Other business models have different versions of the same problem. Enterprise software companies may not have inventory, but they have complex buying cycles, multiple sales touches, account-level data, and dozens of variables across the funnel. Lead generation businesses have their own set of channel, conversion, and customer-quality questions.

Every business has data complexity somewhere. The challenge is that the information usually isn’t in one clean place.

The real work is making your data usable

At our company, important information lived across WooCommerce, ShipStation, spreadsheets, and other systems. The data didn’t always line up. Pulling a simple answer could require a manual investigation across several tools.

Questions that sound easy in a meeting could become surprisingly difficult:

  • How long does it typically take a customer to make a second purchase?
  • What is the lifetime value of our 2024 customer cohort?
  • Which products create the strongest repeat-purchase behavior?
  • Which promotions have actually moved revenue?
  • What should we promote now without creating an inventory problem later?

Before we had a connected data source, answering those questions took time and often involved educated guesses. We could look at individual reports, but strategic analysis requires connecting the reports.

Our CTO, Ron Brouwer, led the effort to create a database that synchronized the information from our different systems. Because he understood both the technical side and the operational side of the business, he knew what the data meant and how our teams actually used it.

That combination mattered. A technically elegant database that doesn’t reflect how the business works won’t help much. The goal wasn’t merely to store more information. It was to create a source that could compare the information and make it accessible to the people making decisions.

We also had to think about privacy. We didn’t want to send sensitive customer information directly into an AI tool. The solution was to anonymize the customer data so we could analyze patterns and cohorts without exposing personally identifying details.

That’s a useful principle: make the data available, but don’t make private information available unnecessarily.

What happened when we connected AI to the database

Once the database was ready, our team received read-only access through an MCP connection. That meant we could use tools such as Claude, ChatGPT, or Codex to ask questions about the business without giving the AI permission to alter the underlying data.

The first time I saw it analyze the data, it was both impressive and a little terrifying.

We were trying to figure out how to bring more revenue forward. Instead of starting with a collection of guesses, we asked Claude to review our data and propose a promotional plan.

It examined inventory levels, expiration dates, historical promotions, and product performance. We also gave it access to a Google Sheet containing three years of week-by-week promotions. That sheet didn’t contain all the corresponding revenue data, but it gave the model a useful record of what we had tried.

The resulting plan explained what to promote, when to promote it, and why. It identified patterns in our previous promotions and recommended several plays that had historically moved the needle. It also avoided simply pushing products that could create problems later.

I know how difficult that analysis would have been for me to complete manually. I would have needed to find the relevant reports, reconcile the numbers, check inventory, review past promotions, and then make the strategic decisions. Even with a full week, I might not have produced something as comprehensive.

AI didn’t replace the marketing work. It gave us a much better starting point.

This is the difference between asking AI to write a promotion and asking it to help decide which promotion is strategically sound. The first task needs creative context. The second needs business data.

Use AI as an analyst, not an unquestioned decision-maker

The recommendation still required human judgment. The model didn’t know everything I knew about our audience because it hadn’t talked to our customers. It didn’t understand every emotional or cultural nuance behind the products. I have relationships with the audience, and I’m close enough to the customer that I can recognize when a technically sensible idea won’t land the way the data suggests.

So I reviewed the recommendation, challenged parts of it, and added context. I could say, “This week doesn’t work because of a factor you don’t know about,” and continue the conversation from there.

That human contribution isn’t a temporary inconvenience. It’s part of the job.

AI can quantify patterns and analyze more variables than most teams can handle manually. Humans still supply values, convictions, relationships, taste, responsibility, and lived experience. We decide which goals are worth pursuing and which tradeoffs we’re willing to accept.

That’s why I don’t think a less experienced person automatically gets the same results just because they have access to the same model. Someone with years of experience understands the history behind the numbers. They know which metrics are misleading, which customer objections matter, and which recommendations need more scrutiny.

The strongest workflow is collaborative:

  1. Give AI access to trustworthy, relevant data.
  2. Ask it to find patterns and explain its reasoning.
  3. Check the inputs and assumptions.
  4. Add the context the data can’t capture.
  5. Make the final decision as the accountable human.

This fits with the broader paradox of AI: it can be extraordinarily capable in some areas while remaining dependent on human direction in others.

Marketing leaders need an IT relationship

If you’re a marketing leader, you can’t treat data access as someone else’s problem. You don’t need to personally build the database, but you do need to help define what the business needs from it.

Start talking with your CTO, IT team, operations team, finance team, and anyone else who owns a meaningful piece of the customer or revenue data. Explain the questions you need to answer. Bring real marketing decisions into the conversation.

IT may initially think in terms of one system or one type of data. Marketing often needs the connections between systems. For example, sales data alone might not tell you much about customer lifetime value. You may need customer cohorts, product history, purchase intervals, subscription status, and promotion history together.

I had to go back to our CTO and point out that we had sales data but not enough customer data to answer the questions I cared about. That led to a better solution: anonymized customer information that could be analyzed without creating an unnecessary privacy risk.

These conversations work better when marketing brings specific questions instead of vague requests for “more data.” Ask for the information required to make a decision:

  • What should we promote?
  • Which customer group should we prioritize?
  • Where is the bottleneck in the funnel?
  • Which product has the strongest repeat-purchase potential?
  • Where are we underperforming against relevant benchmarks?

When operations, procurement, marketing, and IT can all ask questions against the same source, the quality of the discussion improves. The team moves away from “this feels like a good idea” and toward “here’s what the data says, here’s what it doesn’t say, and here’s the judgment we need to apply.”

That’s much healthier than copying a competitor’s tactic without knowing whether it worked for them or whether it fits your business.

Small and medium-sized companies have a real advantage

One unexpected advantage here belongs to small and medium-sized companies. Large companies may have more data, but they often have more silos, more approval layers, and more systems that don’t communicate well.

A smaller company can sometimes move from scattered data to a useful shared system much faster. If it has been operating for five or ten years, it may also have enough history to make the analysis meaningful.

A startup with almost no customer or sales history has fewer options. It may need to rely on public data, benchmarks, and assumptions. An established company with real traction can analyze what has worked, what hasn’t, and how different customer groups behave over time.

That combination—enough data and the ability to move quickly—can become a significant strategic advantage.

The companies that build these connections earlier will be able to make better decisions sooner. This isn’t just about saving time on reporting. It’s about increasing the speed and quality of strategic learning.

A practical starting checklist

You don’t need to begin with an enormous data project. Start with one recurring decision that currently requires too much manual work or too much guesswork.

  1. Choose a high-value question. Pick something tied to revenue, retention, inventory, or conversion—not a vanity metric.
  2. Map where the data lives. List the platforms, spreadsheets, databases, and teams that own the relevant information.
  3. Identify the gaps. Decide which missing fields or disconnected systems prevent a reliable answer.
  4. Define privacy boundaries. Use anonymization and read-only access where appropriate. Don’t expose sensitive information simply because you can.
  5. Build a shared source. Work with IT to synchronize and standardize the data needed for the selected question.
  6. Test the analysis. Ask AI to show its assumptions, cite the underlying data, and identify uncertainty.
  7. Apply human judgment. Add customer knowledge, brand context, and business constraints before acting.

Once that workflow works for one decision, expand it. You might move from promotion planning to cohort analysis, inventory forecasting, customer retention, or channel allocation.

This is also why I’ve become less interested in treating AI as merely a content-generation tool. The bigger opportunity is strategic analysis. If you’re thinking about the limits of automating marketing work, the same lesson applies: the quality of the result depends heavily on the quality and accessibility of the underlying information.

The next AI advantage is connected judgment

AI models are already powerful enough to analyze a substantial amount of business information and carry on a long, useful conversation about it. There will be improvements, but marketing teams don’t need to wait for some future model before starting.

The constraint is access.

Can your AI see the information required to understand the decision? Is that information accurate, connected, and current? Can your team explain what the numbers mean? Can you protect customer privacy while still giving the system enough context to be useful?

If the answer is no, better prompting won’t solve the problem.

Start building the relationships and infrastructure that make responsible data access possible. Then use AI to analyze the information, expose patterns, and give your team a stronger first draft of the strategy.

The marketer’s role isn’t disappearing. But it is moving upward—from manually gathering every number to deciding which questions matter, which evidence is trustworthy, and what the business should do next.

That’s the work I’d focus on now: pick one important marketing decision, bring IT into the room, connect the data, and see what becomes possible when AI has something real to analyze.

For the human side of that transition, I’d also revisit the Human Edge Framework. The data gives AI leverage. Your judgment determines how that leverage gets used.