Why Your AI Initiative Isn’t Building a Competitive Advantage

SubscribeSign in

The Executive Brief<br>The Good Days Are Over<br>Investors stopped asking about your team. They’re asking about your data. Here’s what I’ve been sitting with since the book was finished.

Sarah Chen<br>Jun 02, 2026

Share

These are notes I couldn’t fully articulate while I was inside the year with Arjun. Now that I’m standing outside it, I can name them clearly. I’m sharing them because I think some of you are living exactly what I lived, and because some of what I’m watching happen in the market right now is keeping me up at night in ways I didn’t expect.

There was a version of this that felt responsible.<br>Impact Operations is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

Subscribe

You hired a data team and called it an investment. You approved an AI initiative and called it a strategy. You pointed to headcount, to tooling, to a roadmap, and the board nodded. Nobody asked what any of it was actually generating. The shelter wasn’t incompetent. It was the ambiguity that the market rewarded. As long as you were moving, the hard question stayed quiet.<br>I ran Stock Dropper that way. The decisions were rational within the context that existed. Investors asked about headcount. Boards evaluated on technical capability signals. The incentive structure pushed toward showing momentum, so we showed momentum.

The "Agent Army" Audit<br>None of it was building an asset. I didn’t have the language for that until the conversations around me started to change.

The conversation changed. Most of us missed it.<br>Two years ago, the question was how many data people you had and what stack you were running. Today, the question is how you’re maximizing the data you own to generate value, and what you’ve built internally that nobody else has.<br>That sounds like updated vocabulary for the same conversation. It isn’t.<br>It’s a financial conversation now, not a technical one. That’s why data has been moving from under the CTO to under the CFO in companies that are paying attention. Not as a reporting line preference, as a signal that data is being evaluated as a capital asset with expected yield, not a function with a headcount.<br>I decided that our work with Arjun, which I questioned at the time, I would assume direct ownership of the data portfolio myself. Not delegated. Not overseen. Owned. It created friction internally. People read it as a control move. It wasn’t. It was the only way I could be accountable for what the portfolio was actually returning versus what it was consuming.<br>When we got to the Series C conversation, I understood why that decision was the right one. The investors weren’t asking John about the data stack. They were asking me what our data was worth and how we were allocating toward it. I walked into that room equipped to answer. I wouldn’t have been able to say the same twelve months earlier.<br>Stock Dropper had 100 people when Arjun and I started. We have 200 now. That doubling didn’t happen because we threw more bodies at the problem. It happened because we finally understood which parts of the portfolio were generating yield and which parts were consuming capacity we needed elsewhere. The operating model changed first. The growth followed.

What the good days actually cost<br>Every team is designed to show intent, and every roadmap aims to demonstrate momentum, so they created something. However, it wasn't the value I expected. Instead, complexity arose: a portfolio of products, pipelines, and processes stands between me and the answer needed for the new investor conversation.<br>The cost wasn’t just what I spent. It was the distance between where I was and where the conversation now needed me to be. And that distance doesn’t show on a dashboard. It shows up in the fundraiser. It shows up when someone asks what your data is worth and you reach for a headcount number instead of a yield number.<br>I lost time. I’m naming that plainly because I think some of you are losing it right now, not because you’re making bad decisions, but because you’re making rational decisions inside an incentive structure that has already shifted around you.

The operating model that no longer fits<br>Initiatives made sense in a linear world. You plan a year, execute, measure, plan again. Clean, defensible, boardroom-friendly.<br>We are not in a linear world.<br>The companies generating real yield from their data aren’t asking what they’re building this year. They’re asking what is generating value today, how to allocate toward it, and what to kill to protect the capacity to build what they’ll own tomorrow. That is a portfolio management question, not a roadmap question. It doesn’t fit within an annual initiative structure. It requires constant reallocation based on what’s actually returning versus what’s consuming resources and generating noise.<br>That shift is not a technology decision. It is not a team structure...