The Form That Ate the Deal

I should have known something was off when the procurement portal asked me to confirm I wasn’t a robot, then asked me again, then asked me a third time but in French.

It was a Tuesday. Tuesdays at Nakatomi Solutions were supposed to be my “deep work” days - a concept I’d borrowed from a productivity book I’d never finished. In practice, Tuesdays were the days I caught up on the admin that Monday had vomited onto my desk.

The deal was with a facilities management company called Gresham Park. Mid-market, decent budget, genuine pain. Their lead architect - a bloke called Henrik Schmidt - had basically said the words every SE dreams of hearing: “Can we just get this into a proof of value?”

Beautiful. Clean. I wrote it in my notebook and underlined it twice.

Our AE, Lauren Phillips, pinged me on Slack: Henrik’s ready. Let’s get the PoV scoped this week.

I cracked my knuckles. I made a cup of the good instant coffee - the kind that comes in a glass jar and costs enough that you feel something about it. I opened the scoping template.

And then Henrik sent the email.

“Before we can formally engage in any evaluation activity, we’ll need you to complete our Vendor Assessment Intake Form (VAIF-1). This is standard. Should take about twenty minutes.”

Twenty minutes. Fine. I once completed a security questionnaire that asked whether our software could survive a nuclear electromagnetic pulse. I wrote “untested” and moved on.

The VAIF-1 was hosted on a portal that looked like it had been designed in 2007 by someone who actively disliked users. Under “Primary Use Case,” my choices were: Facilities Management, Fleet Tracking, Catering Services, or Other. I selected Other. A text box appeared: “If Other, please submit Form VAIF-1b.”

VAIF-1b was a scanned PDF of a printed Word document, slightly crooked, with someone’s coffee ring on the second page. I filled it in using a stylus I found in a drawer and emailed it back.

Henrik replied within the hour. “Thanks Max. Now we’ll need the Technical Risk Disclosure (TRD-4), countersigned by your Data Protection Officer.”

Our DPO was a contractor named Rupert Pendleton who worked Mondays and Thursdays. It was Tuesday. His Teams status said “Away.” It always said “Away.” I once saw Rupert in the kitchen, actively online, eating a Twirl, while his status said “Away.” I think it was a philosophical position.

Thursday, Rupert signed the TRD-4 with a note: “This form doesn’t actually ask anything about data protection.” He was right. It mostly asked about fire suppression systems. I sent it through without questioning it.

Friday. Henrik again. “Next step is the Evaluation Authorisation Request (EAR-7). This needs sign-off from our Commercial Partnerships team.”

The Commercial Partnerships team was one person: Cassie Beaumont, on secondment to Dubai since March. Her responsibilities had been temporarily reassigned to Pieter van der Berg in Rotterdam, who had a four-hour overlap with UK business hours.

Pieter was responsive, professional, and deeply apologetic. “The EAR-7 was introduced in 2019,” he explained over video. “It was meant to be retired when we moved to the new vendor management platform, but the new platform was never fully rolled out, so now we have both systems running in parallel, and neither one talks to the other.”

I wrote that down. Not because it was useful. Because it was the most honest sentence anyone at Gresham Park had said to me.

Pieter signed the EAR-7. He also warned me about the Supplementary Technical Addendum (STA-12), which required a counter-signature from a “Senior Innovation Sponsor.”

“Who’s the Senior Innovation Sponsor?”

Pieter looked at his screen for a long time. “A gentleman called Edward Sinclair.”

“Great. Can you connect me?”

“Edward retired in 2021.”

I took a sip of my coffee. It had gone cold. It was the cheap stuff now - the kind that comes in a plastic tub and tastes like a decision you made at a petrol station.

“So the form requires a signature from a role that doesn’t exist, held by a person who’s retired, for a process that was supposed to be decommissioned three years ago.”

Pieter nodded the way you nod when someone has described your house and you’re not sure if they’re complimenting it or condemning it.

Meanwhile, Lauren was getting anxious. Pipeline review in two weeks, the deal still showing as “Discovery.” “Can’t you just start the PoV informally?” she asked.

I’d been down that road. The shadow PoV - the one that exists in a quantum state between “real engagement” and “favour for a mate.” You do the work, show the value, and then someone says, “We can’t accept these results because they weren’t conducted under a formally approved evaluation framework,” and you realise you’ve spent three weeks building a sandcastle below the tide line.

So I said, “Let’s make sure we do this properly,” which is the SE way of saying no while maintaining the appearance of enthusiasm.

Henrik’s manager, Astrid Schneider, did something radical: she read the STA-12, crossed out the phantom signature line, wrote “ROLE DISSOLVED - APPROVED PER A. SCHNEIDER, HEAD OF INFRASTRUCTURE,” and sent it back within the hour.

It felt like we’d crested the hill. I sent Lauren a thumbs-up emoji, which in SE parlance is practically champagne.

Next morning, an email from compliance-review@greshampark.co.uk informed me the STA-12 had been rejected. Astrid wasn’t listed as an Approved Signatory on the Vendor Evaluation Authority Matrix - a spreadsheet maintained by Governance Oversight, a team I hadn’t known existed and was beginning to suspect didn’t fully exist in any operational sense.

Henrik picked up on the first ring. “I know,” he said. “The VEAM hasn’t been updated since Q2 of last year because the person who maintained it moved departments.”

“Which department?”

“Governance Oversight.”

I wrote that down too.

“Henrik,” I said, “I’ve filled in nine forms. I’ve spoken to people in three time zones. Nobody has asked me a single question about the technology. Not what it does, not how it works, not whether it can solve the problem that keeps your team up at night. Is there a path through this, or are we just feeding the machine?”

Henrik was quiet. Through his partition wall, I could hear someone else’s Teams call - the word “synergies,” which felt appropriate.

“I’ve been here eleven years, Max. I’ve watched three vendors give up at this stage. One sent a polite email about ‘reprioritising strategic resources,’ which I think meant their SE had a breakdown. Give me until Monday.”

Monday came. Henrik called.

“I spoke to Astrid. Astrid spoke to our COO. The COO didn’t know the VEAM existed, which I found both alarming and encouraging. He’s authorised a direct approval. No form. Just written confirmation.”

The email arrived while we were still on the phone. Three lines from a man named James Whitfield: I’ve reviewed the request. Approved. Let’s stop making it harder for people to do their jobs.

I stared at it. The most beautiful piece of procurement documentation I’d ever seen, precisely because it wasn’t procurement documentation. It was a person cutting through the fog, saying yes.

The PoV kicked off thirty-one days after Henrik first said the magic words. Nine forms, six people, three time zones. A retired Innovation Sponsor, a ghostly Governance team, a COO who’d never heard of his own approval matrix, and a DPO whose perpetual Away status I’d come to regard with something approaching envy.

At no point had anyone asked me a single question about the technology.

The PoV itself took four days. Four days. We proved the concept, validated the architecture, showed Henrik’s team something that made their lead engineer say, “Why haven’t we been doing this already?” - which is the second-best sentence an SE can hear, right after the one that started all this.

Lauren updated the CRM. The deal moved to “Technical Validation.” She sent me a message: Finally. You’re a saint. I wasn’t a saint. I was a man who’d spent a month doing paperwork to earn the right to do four days of actual work.

But that stayed with me. After the final readout, Henrik pulled me aside - virtually, which meant he stayed on the call after everyone else dropped off.

“Max, I want you to know something. The reason I kept pushing internally is because your team was the only vendor that didn’t disappear. The other three gave up at the forms. And? Their technology might have been just as good. We’ll never know. The process didn’t filter for quality - it filtered for stubbornness.”

I sat with that for a long time after we hung up.

I opened my notebook to a clean page and wrote: The hardest part of proving value is getting permission to prove value.

I underlined it once. Twice felt excessive.

Then, below it, something I hadn’t planned to write but couldn’t stop myself: And the worst part is knowing that somewhere, right now, a better solution is dying in someone’s procurement portal - not because it wasn’t good enough, but because its SE ran out of coffee, or patience, or Tuesdays.

I closed the notebook. Somewhere in Rotterdam, Pieter was probably filing something. Somewhere in a kitchen, Rupert was eating a Twirl. Somewhere in retirement, Edward Sinclair was blissfully unaware that his phantom signature had almost killed a deal.

I made a fresh cup of coffee - the good stuff, the glass jar - and opened the next scoping template. Another deal, another customer, another portal that would almost certainly ask me to confirm I wasn’t a robot.

I clicked the button. I confirmed. I was, after all, only mostly sure.