The Intelligence Company

I keep noticing the same conversation happening on repeat.

A team gets excited about AI. Someone shows a demo. Meta's Advantage+ already writes the ads. Google's Performance Max already allocates the budget. Everyone agrees this is the future, and everyone starts asking the same question: which tool should we add.

I used to ask that question too.

It took me a year of watching my own answer fail to notice what was actually wrong with it.

I built the MarTech stack before the data architecture. Every campaign optimized on the platform's own numbers, the way the platform wanted them read. The results looked great in every dashboard I checked. Then a VP asked me to explain why a specific segment was underperforming, and I couldn't. Not because the answer was hard. Because the data that would have answered it didn't live anywhere I controlled.

That's the moment the belief actually changed, not the moment I could have stated it.

Here's what I noticed once I started looking for it. Google knows what people search. Meta knows what people like. Neither one knows what happens after the click. Neither knows which leads actually close, or the real path from first touch to signed contract, or why the good customers stay past year one. That knowledge lives in the CRM, the call logs, the sales conversations, the customer success notes nobody reads twice. It's the one dataset the platforms will never have, because it never touches their systems.

I own the invoice for what a recommendation costs when it's wrong. That's not a caveat on the work, it's the actual product. A tool now writes the first draft of most marketing copy for the price of a subscription. If drafting is still the thing on my invoice, I'm competing with something that gets cheaper every quarter, and I will lose that race even on the days I win it. What's still scarce, and stays scarce, is judgment: knowing which of fifty plausible campaigns is the right one for this constraint, this client, this specific moment. Anyone still pricing themselves on output volume is pricing themselves against a machine built to undercut exactly that.

I used to think the fix was a better MarTech stack. It isn't. It's a data architecture: first-party data connected across systems, with a traceable line from source to insight to the decision it actually changed. Curated, not just collected. Most companies already have the raw material sitting in a spreadsheet named Q3 Final v2 FINAL, last opened in August, and mistake having the data for owning the asset.

The difference between those two things sounds technical. It isn't. It's strategic, and it's the whole difference between a campaign team and an intelligence company.

A campaign team rents access to someone else's algorithm and calls the rental a strategy. An intelligence company owns the thing that makes every algorithm it touches perform better, because it's feeding the algorithm something the algorithm can't get anywhere else.

I've watched this play out as a cycle more than once. The quarter looks bad. Someone pulls off a brilliant campaign under pressure. The team celebrates the save. Then the quarter after that looks bad again, for the same underlying reason nobody fixed. We reward the person who put out the fire and forget to ask why the building keeps catching. An intelligence company doesn't win by getting better at the save. It wins by building the thing that makes fewer fires start in the first place, which is a much less applauded kind of work, and the only kind that actually compounds.

I don't know yet whether this is the whole answer or just the part I've been able to verify from where I sit. What I do know is which question I stopped asking, and which one replaced it. Not which tool should we add. Whether the AI is using your data, or you're using theirs.

That's the question that decides who leads, and who rents.