The Ghost of Blue Sun Corp

The notebook entry for October 14th just says: “Lindsey loves us. This is the one.”

I’ve read it four times now, sitting here with instant coffee I made too strong because I wasn’t paying attention. Each time it hits differently. Not because it was wrong. Lindsey Sinclair did love us. That was the problem - I thought love was enough.

Blue Sun Corp landed in my inbox on a Tuesday with a note from our AE, Scott: “Hot one. They want a PoV. Can you scope by Friday?”

Scott’s definition of hot has historically ranged from “CEO mentioned us at a board meeting” to “someone downloaded a whitepaper and didn’t unsubscribe.” But this time, fair play - it was real. Lindsey Sinclair, Senior Director of Platform Engineering at Blue Sun, had built a comparison matrix, run a proof of concept with a competitor, found it lacking, and come to us with actual use cases, actual infrastructure constraints, actual timelines.

Discovery went like a dream. Three calls, each better than the last. Lindsey knew her environment inside out. She could articulate the gap between where they were and where they needed to be in language that made my job feel almost unnecessary.

In our second call, she mentioned - casually, the way you mention a pothole on your commute - that the infrastructure team reported into a different org than her platform engineering group. I wrote it down. I even underlined it. Then I moved on to the next question about API throughput requirements, because the technical thread was so satisfying to pull that I didn’t want to stop and tug at the organisational one.

I felt that small, cold flicker every SE learns to recognise - the sense that the picture is too clean, that you’re only seeing what’s lit up. But Lindsey was so good. Prepared and specific and generous with her time. Asking “Who else matters?” felt like telling someone their love isn’t enough on the first date.

So I didn’t ask. I drew a neat little diagram in my notebook - discovery findings on the left, PoV success criteria on the right, a clean arrow connecting them. Beautiful. Like a process that actually worked.

The PoV kicked off November 1st. Two-week sprint. Shared Slack channel. Mutual success plan - and I only felt a little sick saying those words.

Week one was textbook. I was sending Scott updates that were borderline smug: “Tracking green across the board. Already talking expansion use cases.”

On November 5th, Lindsey forwarded me a question from someone named Raj Patil. The email chain showed Raj sat under Enterprise Technology - a different branch of the org chart. His question was sharp: how did our platform handle east-west traffic inspection at the segment level?

I answered it thoroughly. Sent it back through Lindsey. Never heard from Raj again.

I could have asked Lindsey to introduce me directly. I could have said: “Sounds like infrastructure has a stake in this - should we loop them in?” Instead I treated his question like a support ticket. Answered it, closed it, moved on. I told myself Lindsey had the internal alignment handled. That’s what makes someone a champion.

That’s also what makes them a single point of failure. But I didn’t have that language yet. I was still using the word champion like it meant invincible.

November 9th, Lindsey messaged: “Heads up - need to loop in Procurement for the commercial side. Shouldn’t affect the technical eval.”

I typed “No worries” and meant it. What I didn’t register was that Procurement doesn’t just appear. Someone tells them to. And that someone usually isn’t the Senior Director of Platform Engineering.

November 12th: our midpoint review got moved from Tuesday to Thursday. No reason given.

I pinged Lindsey. She replied four hours later: “Calendar conflicts. All good.”

Four hours. Lindsey, who’d been responding in minutes, who’d been sending me zero-trust architecture articles at 10pm because she was genuinely excited. Four hours and two words of reassurance I hadn’t asked for.

I almost called Scott. I had the words ready: “We need to go wide. Get me anyone who isn’t Lindsey.” But I thought about what that would look like - going around my champion, signalling distrust. And I thought about the pipeline forecast I’d submitted with Blue Sun at 70% probability, and how that number had become a small but load-bearing pillar in a quarterly forecast that people above me were counting on.

So I waited. I told myself I was being patient. I was actually being afraid.

November 14th: the Thursday meeting didn’t happen. “Something came up - can we push to Monday?”

November 18th: Monday. I dialled in two minutes early. Lindsey joined six minutes late, camera off. Her voice had that careful flatness people use when they’re being watched or when they’ve already made a decision they can’t share.

We got through the agenda in half the time. She said the right things. She asked no questions. Then I asked one - dragged out by desperation rather than diligence.

“Lindsey, is there anyone else we should present the results to? Someone from the infrastructure org?”

A pause. Not long. But shaped like a decision.

“Let me manage the internal piece.”

It’s what champions say when they’re trying to protect you, or themselves, or both. I heard it for what it was - a door closing - and I let it close.

The Slack channel went from twelve messages a day to three. Then one. Then a thumbs-up emoji on something I’d posted two days prior.

Here’s where I became a detective, which is a generous word for someone refreshing LinkedIn at 11pm.

Henrik Beaumont, VP of Enterprise Technology - a name I’d never encountered - had posted about “rationalising vendor relationships” and “consolidating platform investments.” Forty-two likes, mostly internal. Lindsey hadn’t liked it. Raj Patil had.

I clicked through to Raj. Director of Infrastructure Services. Reported to Henrik. Nine years at Blue Sun - twice as long as Lindsey. In his activity feed: a case study from one of our competitors, shared October 28th. Three days before our PoV kicked off.

The picture reassembled itself with a sick clarity. While Lindsey was running discovery calls with me, Raj and Henrik had their own evaluation underway. Lindsey probably knew. She might have thought she could outrun it - that if our PoV delivered strong enough results, the evidence would override whatever Henrik’s side was doing. She was betting on merit. It’s the bet engineers always make, and it almost never pays off, because the people who decide aren’t optimising for the best technology. They’re optimising for the least risk to their own position.

I rang Scott. “Who’s Henrik Beaumont?”

Silence. Then: “Maybe Lindsey’s boss’s boss? Why?”

“Because he’s the reason our PoV is dying. His infrastructure director has been evaluating a competitor the entire time.”

“Can you get a meeting with him?”

“I can’t get a meeting with anyone. Lindsey’s going dark. Scott, we built this whole thing on one person.”

We tried anyway. Scott found a contact in Blue Sun’s finance team who owed him a favour. I rewrote our PoV results - not the version for Lindsey, full of architectural nuance, but a version for Henrik. Business outcomes. Risk reduction. Total cost of ownership. The language of someone who doesn’t care how elegant the solution is, only whether it makes their budget look responsible.

The summary was forwarded to Henrik’s office on November 21st.

We never heard back. And standing there in that silence, I finally understood something I’d been circling for weeks: this deal hadn’t died on November 21st. It had died on that second discovery call, when Lindsey mentioned a different org and I underlined it and kept going. Every moment after - Raj’s email, the four-hour reply, the camera-off meeting - had been the consequences arriving one by one, and I’d greeted each one with the same decision: don’t look, don’t ask, don’t disturb the beautiful clean picture.

I hadn’t lost to a competitor. I’d lost to my own comfort.

I sent Lindsey a wrap-up email. Professional, warm, no passive aggression, which took four drafts. She replied the next day: “Thanks Max. Really valued the work. Timing isn’t right but I’ll be in touch if things change.”

I wrote back something brief and genuine. I thanked her for being the best champion I’d ever worked with. I meant it. I also knew it hadn’t been enough - not because of anything she’d failed to do, but because I’d put the entire weight of the deal on her shoulders and called it a partnership.

Three months later, Blue Sun announced a platform deal with our competitor. The press release quoted Henrik Beaumont. Consolidated buy - platform engineering and infrastructure services together. Raj Patil was named as technical lead.

I read it twice, then closed the tab.

What I felt wasn’t anger. It was recognition. Not of what I should have done - I’d known that for months, had rehearsed the better version so many times it was worn smooth. What I recognised, finally, was why I hadn’t done it. It wasn’t ignorance. It wasn’t lack of skill. It was that Lindsey’s certainty had felt so good - so clean and complete - that questioning it would have meant choosing discomfort over momentum, and I chose momentum every single time.

I go back to that notebook entry now and I see it differently. “Lindsey loves us. This is the one.” The handwriting is confident. No question marks. No margin notes about who else to talk to, what other doors to open.

It’s the handwriting of someone who’d already decided to stop looking.