Why we walked away from our largest FR account after seven years.

In 2024 we did something that does not fit on a sales deck. We walked away from our largest single FR program at the contract renewal. Seven-year relationship. $1.9M in annual revenue. About 11 percent of the workwear book at the time. The customer wanted to renew. We said no. I had to call our CEO the morning of the meeting to tell him what we were about to do, and the conversation was not fun. This is why we did it and what it taught us about every account since.

The seven years before the meeting.

The account started in 2017. A petrochemical operator with a Gulf Coast workforce, around 1,400 field employees on FR. We were two years into building out the workwear side of Brand Junkie and this was the program that legitimized us as a serious player in the FR category. The first three years were what every vendor relationship should look like. Tight scope, real partnership, monthly cadence, both sides bringing improvements to the table. The customer's procurement director ran a tight ship and we ran a tight account team. The program performed.

Around year four, the customer's procurement director retired. The replacement came in with different priorities and a different approach to vendor management. Year five, the EHS director changed. Year six, a corporate restructuring split the procurement function from operations and put workwear under a centralized strategic sourcing group. Year seven, the strategic sourcing group brought in a consulting firm to "right-size the spend categories" and the consulting firm recommended a category-wide RFP cycle that would put all six of the customer's workwear vendors on a common scorecard.

None of this is unusual. Customer organizations change. Our job as a vendor is to navigate the changes and continue delivering. We did. For most of the changes. The last one is the one that broke us.

What broke the program.

The new strategic sourcing model put workwear into the same category bucket as office supplies and uniform rental. Same scorecard, same monthly KPIs, same competitive bid cycle. The KPIs were almost entirely price metrics. Unit cost, on-time delivery percentage, invoice accuracy, defect rate. There was no measure of program compliance, no measure of worker satisfaction, no measure of inventory match to actual exposure profile, no measure of safety officer time saved.

This is not the strategic sourcing team's fault. They were doing the job their leadership had given them with the tools they had. The problem was that the program had grown into something that did not fit on a procurement scorecard. We were managing FR lifecycle, regional inventory, project-level documentation, OSHA-ready records, custom badging across three operating divisions. The strategic sourcing team was measuring whether the invoice came in correct on the fifteenth.

By month six of the new scorecard era, we were optimizing the program against the wrong objective function. The metrics that mattered to the customer's safety officers and field operations were starting to drift because the metrics that mattered to the sourcing team were the only ones that produced quarterly reviews. The program was losing the substance that had made it work, and there was no mechanism inside the customer's organization to surface that drift to the people who actually depended on the program.

The conversation that triggered the decision.

The trigger was a Tuesday in late September. The customer's strategic sourcing lead called a quarterly review with our account team. The agenda was the scorecard. We had landed at 92 percent on the scorecard for the quarter. Strong number. The conversation should have been a short congratulatory check-in and a forward look at the upcoming year. Instead the sourcing lead spent 40 minutes on the 8 percent we were not at and how we could close the gap by Q4.

One of our account managers asked, near the end of the call, whether anyone had heard from the regional safety officer in Beaumont about the FR inspection backlog she had flagged in August. The sourcing lead said the safety officer's concerns were "operational" and would be discussed in a separate forum. The account manager hung up the call and walked into my office and said: "Grant, this is over. They're not measuring the program. They're measuring us against a scorecard that doesn't include the program."

She was right. I sat with that read for three days before I picked up the phone and called the customer's VP of Operations. The conversation lasted 18 minutes. He listened. He thanked me for the call. He did not commit to anything. The renewal RFP was scheduled to go out two months later. We had a decision to make.

The internal debate.

I want to be honest about this part. The decision to walk away was not unanimous on our side. There were three positions in the room.

Position one: stay, optimize for the scorecard, take the renewal at slightly lower margin, accept that the program substance was going to keep drifting and that we would eventually lose it on quality grounds in 18 to 24 months anyway. Most of the sales and finance team supported this. It was the rational position from a quarterly P&L standpoint.

Position two: stay, but make a final attempt to escalate the program scorecard issue to the customer's leadership before the renewal. Try to get the program metrics added to the scorecard. Operations and our account leadership supported this. It was the optimistic position and it required the customer's leadership to be willing to push back against their own sourcing function, which is rare.

Position three: walk away. Decline the renewal. Tell the customer's VP of Operations honestly why we were declining and let the chips fall. I held this position alongside our account manager who had been on the program from day one. It was the position with the worst short-term financial outcome and the only one that did not require us to either compromise the work or hope someone else would fix the misalignment.

Why we picked the third position.

I picked the third position for three reasons that have crystallized over the 18 months since.

First, the program substance was already degrading and we knew it. Staying meant accepting that we were going to deliver worse work to the customer than we had delivered for the prior six years. The customer's workers, their safety officers, their operations team were going to be the ones experiencing that degradation. We were the only people in the chain who could see it coming and we were also the only people in the chain who could prevent it. Staying was a quiet way of saying that the financial value of the renewal was more important than the quality of the work we were going to deliver.

Second, this was going to recur. The strategic sourcing model the customer had implemented was not specific to us. It was the framework they were applying to every category. The next big account with the same procurement structure was going to put us in the same position. If we accepted the trade-off here, we were committing to accepting it everywhere. The downstream implication was a company that gradually lost the ability to deliver the kind of work we had built our reputation on, because we had repeatedly chosen revenue continuity over program substance.

Third, the calculus on the alternative was actually less scary than it looked. $1.9M in revenue is a real number. It is also one large account that, lost on quality grounds in 18 months, would have been replaced by an angry customer reference. Walking away on principle, communicated honestly, was lost as quiet revenue. Lost on quality after compromise was lost as reputation. The first is recoverable. The second is not.

The CEO call.

I had to call our CEO the morning of the renewal meeting because the decision needed an executive co-signer. He had been generally aware of the trajectory but not the operational specifics. The call was uncomfortable. He asked the questions I would have asked. Are we sure the relationship cannot be repaired. Is there a smaller scope we could retain. Are we walking away from $1.9M or from a relationship with intrinsic future value we are giving up. I had answers for the first two questions. The third one I had to sit with for about 90 seconds before I told him I genuinely did not know.

He approved the decision. We declined the renewal in the meeting that afternoon. The customer's strategic sourcing lead was surprised. The VP of Operations was not surprised at all. He told me, after the meeting, that he had been expecting the call since I had reached out two months earlier. He said the program had changed in a way he did not have political capital to change back, and he did not blame us for the decision. We shook hands. The program transitioned to the second-place vendor 90 days later.

What happened next.

Eleven months after we walked away, the customer's VP of Operations called me on a Friday afternoon. The replacement vendor had failed two consecutive OSHA documentation requests. The new strategic sourcing lead had been reassigned. The procurement function had been folded back under operations. He wanted to talk about getting us back. I told him I would be honored to have the conversation and that we needed to talk about what the scorecard was actually going to measure this time. We are now nine months into a re-acquired account. It is currently 60 percent of the size of the original, growing back toward parity by year three.

What I would do differently.

The lesson that holds for every account.

The lesson is not that you should fire your biggest customer. The lesson is that when a program is no longer serving the customer the way the relationship was originally designed to serve them, the vendor is the only party in the room who can see that fact clearly. The customer is too close to their own internal politics. The vendor has the outside view. The vendor's job is to surface the misalignment honestly, work to repair it if possible, and walk away if not.

The vendors who quietly accept the misalignment and try to optimize against the wrong objective function eventually become the bad vendors in the relationship's memory. The vendors who name the problem and accept the financial consequences of being honest are the ones the customer remembers when the strategic sourcing experiment ends, the consultant moves on, and somebody asks "who was the last vendor that actually understood our program?" That is the bench from which the next decade of revenue gets recruited.

It cost us $1.9M to learn this. It is the most important $1.9M we ever spent. Every account we have signed since has a stronger relationship architecture, a clearer joint operating model, and a vendor team that is more willing to surface bad news early. None of that exists in our company if we had stayed on that account through year eight.