The customer call you stopped doing

The founder pulled up his calendar for the quarter and counted. Year 1, he'd taken 5 customer calls a week. This quarter he'd taken 2. Not 2 a week. 2 total. Somewhere across three years the number slid from 20 a month toward zero, and no invite, no decision, no memo marked the moment it happened. He hadn't noticed until I asked him to count.

In year 1 the roadmap was the calls. His team knew which features mattered because he opened every internal meeting by repeating what he'd heard that week from customers, by name. Prioritization sessions started with him reading quotes off the last call. The strategy was, in operational terms, the aggregated signal from the customer base.

By year 3 there were 2 layers of management between him and the customer. CS produced a monthly summary. Sales forwarded the interesting calls. He hadn't sat on a real call, by himself, with the block protected, in four months.

When I asked him to name his top 3 strategic priorities, he listed them fast. When I asked which of the 3 came from a customer conversation he'd been in that quarter, he stopped. None had. One came from the board, one from an industry article, one from a competitive teardown the strategy team built. The roadmap was being set by the room, not the market.

This is the most predictable decay in a growth-stage company. Early on, the founder is the primary sensor for customer signal. As the company grows, he's pulled into managing the organization, and the calls get delegated, summarized, filtered.

The summaries are accurate as far as they go. But they're summaries. The texture, the unprompted aside, the thing a customer says in the silence before they answer. None of it survives.

By the time the signal reaches him it's been shaped by the CSM's framing, the team's read, and the dashboard's categories. It's no longer the signal. It's the company's interpretation of the signal.

Flattened signal is enough to make tactical decisions. It isn't enough to make strategic ones. Strategy needs the founder to feel the market, to register before the data shows it which segments are softening, which use cases are quietly catching fire, which competitive threats are real and which are noise. That doesn't come from summaries. It comes from being on the call when the customer says the unexpected thing, in a tone the dashboard can't hold, against a business context the notes never recorded.

Decisions made against flattened signal are wrong in directions the founder can't see. The threat the team waves off as noise is already showing up as a soft pattern in three calls he wasn't on. The product opportunity the team is excited about isn't the one customers want; it's the one the team built a roadmap around. The pricing concession under discussion is calibrated against a willingness-to-pay he hasn't heard in months.

The practice decays because of calendar physics. Internal meetings create accountability. Someone noticed when the CEO skipped the leadership offsite. Customer calls create none. Nobody on the team is graded on whether the CEO took five calls last week. The reward is real but slow and invisible; so is the penalty. With neither, the calendar fills with the meetings that carry immediate political weight, and the calls get pushed to next week. Next week has the same calendar as this week.

It compounds with growth. More people means more internal stakeholders who need the founder's time. Each ask is reasonable. The aggregate is a calendar captured by internal demand. The CEO who spent most of year one on customers is, by year 3, spending almost none of it there, and the shift never showed up as a decision. It was distributed across hundreds of small calendar acceptances, each one easy to say yes to.

What restores it is mechanical. A weekly two-hour block, protected, dedicated to customer conversations. Not sales support. Not CS escalations. Time for the founder to sit with customers, listening, with no goal except to hear what they're saying. The block survives competing demands because he's decided, in advance, that it does.

That decision costs something. The board member who needs thirty minutes gets told the block is unavailable. The offsite that conflicts gets scheduled around it. The internal review that wants the slot gets deferred. Each defense is socially uncomfortable. Together they preserve the one input the founder needs to operate strategically at all.

Companies whose CEOs hold this line make different decisions than companies whose CEOs don't. The first kind operates against current customer signal. The second operates against the company's interpretation of it, sometimes right and sometimes not, with no way to catch the difference when it's wrong.

If you can't remember the last unprompted thing a customer said to you directly, you've stopped running a customer-centric company, whatever the deck says. The roadmap now belongs to whoever talks loudest in the leadership room. Put the block back. The signal returns inside a quarter, and the clarity returns with it.

Before your next quarter starts, count:

• How many customer calls did you personally take in the last four weeks?
• Of your current top three strategic priorities, how many trace to a customer conversation you were in?
• What block on your calendar is protected for customer calls, and how many times was it overridden last quarter?
• If you asked your CSMs to name the three customer concerns they most wish you'd heard firsthand, what would they say?

Most founders who run that count find a calendar that drifted into internal demand one reasonable yes at a time. One defended block reverses it. It's uncomfortable to hold at first and clarifying within a quarter. The gap between the decisions you make on live signal and the ones you'd have made on the team's filtered version is the whole reason to hold it.