What Data Really Costs

The invoice arrived on a Tuesday.

€89,000. The consultant had done exactly what she had hired him to do. Two months of stakeholder interviews across every department. A working session at the offsite where people had actually talked to each other, not just presented at each other. Deborah's team had participated. The shareholders had come away energized. And the output, thirty-eight pages, well-structured, clear ownership columns, a sequenced roadmap through the following year, was the most coherent document the data function had ever produced.

Sarah approved the invoice without hesitation. You cannot navigate from a destination..

She sent it to George with a note: good investment. She meant it.

Deborah had been quieter than usual in the final readout. A few of her senior people had the particular expression of people being diplomatic. Sarah had noticed. She had filed it away, but it stayed with her on the walk back to her office.

She sent John a message that afternoon.

Can we find thirty minutes this week? Want to talk through the Deborah situation.

John replied within the hour. They met the following morning.

"She's resistant," Sarah said. "The whole team is. The consultant did excellent work. The plan is sound. And her people sat in that room for two days and came out looking like they'd been asked to do something unreasonable."

John nodded carefully.

"I think," Sarah said, "we may have a people problem."

John said he would keep an eye on it.

What Sarah meant, though she did not say it in those words, was that she was beginning to build a story about Deborah. Talented technically. Possibly not the right fit for where the company needed to go. The kind of leader who protects her team instead of pushing them. The kind who mistakes discomfort for dysfunction.

She did not say it yet. But she was starting to think it.

"The other thing," Sarah said. "The investment this year is significant. The strategy, the tooling, the team cost. I need to be able to walk into a board conversation and show what it's returning. Not just what we're building. What it's worth."

John agreed it was important.

"So, let's make that part of the year," Sarah said. "We have the roadmap. We have the initiatives. By Q3 I want to be able to stand in front of Christoph and show him the return on what we've put in."

John said he would work on it.

She felt good about the conversation. She felt like she was asking the right questions. She felt like the year ahead had a shape.

The question she had asked John, what is this returning, was exactly the right question.

It was that she had never built a language to describe the data function as anything other than a service. And without that language, it could only ever be measured as a cost.

This is the story of the year she found out what the invoice actually bought.

The first message appeared in #warehouse-ops:

Mikael (Warehouse Manager): "Urgent. Physical inventory count shows 203 units of SKU-4782.

The system shows 500. Please advise."

Sarah Chen, CEO of Stock Dropper, was reviewing Q4 projections with George, her CFO, when the second message arrived in #customer-service:

CS Team Lead: "Getting multiple calls about canceled orders. Valentino handbag SKU-4782, flash sale. Customers said they were charged, but orders disappeared. What's happening?"

Then her phone started vibrating.

Marcus. Elena. Carlos. All are calling simultaneously.

She answered Marcus first.

"Sarah, we have a situation. In the flash sale, we oversold. Badly."

"How badly?"

"We sold 500 Valentino handbags in six hours. We only have 203."

Sarah felt her stomach drop. "How is that possible?"

"I don't know. But we have 297 customers who paid €1,200 each for bags we can't deliver."

The math hit immediately. €356,400, and €89,100 in gross profit, on orders they couldn't fulfill.

"Get everyone in the management meeting room. Now."

Sarah, Marcus, Carlos, Elena, and Deborah crowded into the conference room.

"Walk me through what happened," Sarah said.

Deborah pulled up her laptop. "The flash sale launched Thursday evening. By Friday morning, we'd sold 500 units. The website showed 500 available, so the system accepted all orders."

"But we only had 203," Carlos said, voice tight. "My warehouse team did a physical count this morning because something felt off, and updated the system."

"Why didn't they match?" Sarah asked.

"The warehouse and the website track inventory separately," Deborah said. "An automated process keeps them in sync. Somewhere, that process stopped working."

"When?"

"I don't know yet. We're investigating."

Marcus leaned forward. "What do we do about the 297 customers who already paid?"

"Refund them," Sarah said immediately. "Full refund plus a 20% discount code. Send personal apology emails. Do whatever it takes."

"That's €356,000 in refunds," George said quietly. "Plus, maybe another €50,000 in discount redemptions. Call it €400,000."

The room went silent.

"Get me answers by the end of the day," Sarah said to Deborah. "I need to know what broke, when it broke, and how we fix it."

Sarah noticed John, their CTO, wasn't in the meeting room. He was in Belgium speaking with regulators. She texted him. He replied: "Deborah has it. Keep me posted."

That was their dynamic. John hired Deborah, delegated data to her, and focused on infrastructure. Sarah trusted it without watching it