Thursday night. Doug is downstairs. I know this because I can hear the specific silence of a man watching television with the volume at exactly 14 because he thinks anything above 15 is “blasting it.”
I opened the laptop at 9:40 and started writing the telecom story.
The $2.2 million renewal was Wednesday. Tonight I wrote the one from 2021. A telecom client, mid-size, three years into a five-year deal. Usage metrics looked fine. Better than fine, actually. Logins were up 12% quarter over quarter. If you were reading a dashboard, you’d say the account was healthy.
I wasn’t reading the dashboard. I was reading who was logging in.
The mix had shifted. Engineering had doubled their usage. Product management had dropped by half. Marketing, which had been our heaviest department, was barely touching the platform. The numbers were up but the people were wrong.
What I recognized, and what I couldn’t have told you I was recognizing at the time, was the footprint of a new CTO. New technical leadership changes who uses what. Engineering gets access to everything because the new CTO came from engineering. Product management pulls back because their workflows are under review. Marketing stops logging in because nobody has confirmed their budget line still exists.
I called my contact. She confirmed: new CTO, hired six weeks ago, already evaluating their entire software stack. We were on the list. Not the chopping block yet. The list.
I set up a technical review before the CTO could commission his own. Walked their engineering team through integration depth, migration costs, what it would actually take to replace us. The account renewed eight months later without going to competitive bid.
That one took me twenty minutes to write.
The first one took forty. I thought about that. Not because faster is better, but because the second story came out organized. I already knew the shape. Problem, signal, intervention, result. The structure was the same.
I put them side by side. Not literally. I read one and then scrolled to the other. Here is what I noticed.
In both stories, the data looked fine. The dashboards were green. The metrics said everything was on track. And in both stories, a person had changed. Not the data. A person. The VP moved divisions. The CTO was new. And the metrics hadn’t caught up yet because metrics trail people by weeks, sometimes months.
I wasn’t reading dashboards either time. I was reading people. Or rather, I was reading the absence of people. The ones who stopped showing up, stopped responding, stopped being in the room. And I was reading it before the numbers reflected it.
That’s the pattern. Two stories, same pattern. Someone goes quiet, and I notice before anyone else does, and I do something about it while there’s still time.
I sat with that for a while. It felt important and also insufficient. Because “she notices when people go quiet” is an observation, not a service offering. You can’t invoice for noticing.
Or can you. The consultants invoice for frameworks. For “stakeholder mapping” and “renewal readiness assessments” and “executive alignment workshops.” I’ve sat through all of those. The good ones, the ones that actually help, are doing exactly what I do. They’re looking at who has stopped talking and figuring out why. They just wrapped it in a methodology and gave it a name.
I don’t have a name. I have two stories and a pattern and a growing suspicion that I’ve been doing something valuable for 24 years without ever putting language around it. Which might be the most corporate-female sentence I’ve ever written, and I’m not sure I’m wrong.
Tomorrow I might write the third one. The healthcare client from 2022, the one where I mapped the decision-maker network on a napkin at a conference dinner and identified the blocker before the QBR. Three stories might be enough to see if the pattern holds or if I’m just finding what I want to find.
I went downstairs at 11:20. Doug was already in bed. His tea mug was in the sink, rinsed but not washed. The TV was off. The house was quiet the way it’s been quiet lately, which is not the comfortable quiet of two people who don’t need to talk. It’s the quiet of two people who might need to talk and haven’t started yet.
I rinsed my own mug and put it next to his.
Two stories written. A pattern named, maybe. A service I still can’t describe in a sentence. A husband upstairs who I keep meaning to tell and keep not telling. Six times now, but I’ve stopped counting. Which probably means I should stop putting it off.
I know what connects the case studies. I’m less sure what connects any of this to an actual business. But I didn’t know the pattern existed until I wrote the second story, so maybe the third one will show me something I can’t see yet from here.