"The primary color is navy. I asked for slate. This is a breach of Section 4.2, Subsection B of the SOW."
Meet Julian Croft. Julian is the founder of a mid-tier logistics software company that has just received its Series B funding. By all external metrics, he is a success story: pressed shirts, a GMT Master II on his wrist, and the particular vocal fry of a man who has fired three agencies in the last eighteen months. Julian is my acrimony client. acrimony client
The project was a simple dashboard redesign. Wireframes were due in week two. We presented three distinct concepts. Julian’s face, frozen on the Zoom screen, did not move for a full eight seconds. "This looks like my five-year-old drew it with his non-dominant hand," he said. He then demanded we scrap the entire UX research phase and rebuild it based on a sketch he had made on a napkin during a flight to Dubai. When we gently explained the principles of user testing, he accused us of "gaslighting" him. "The primary color is navy
By month three, the relationship had entered what I call the "litigation pre-phase." Julian stopped approving invoices on time, claiming that the "quality did not meet the contractual threshold." He started cc’ing his personal lawyer on emails about font sizes. He created a shared document titled "Master Failure Log," a living spreadsheet where he timestamped every perceived slight, every missed emoji in a status report, every email that took longer than fourteen minutes to receive a reply. Julian is the founder of a mid-tier logistics
That is the acrimony client. You do not manage them. You survive them. And if you are lucky, you learn to recognize the smell of sulfur before you sign the dotted line.
Julian replied seven seconds later. He did not say thank you. He did not say goodbye. He wrote: "Finally, you made one smart decision. I’ll be posting about this experience on LinkedIn. You have been warned."
The acrimony client operates on a paradox: they hate you for the sins of your predecessors, yet they expect you to work for the price of a saint. Julian had negotiated our fees down by thirty percent, citing "efficiency savings," yet he demanded the white-glove treatment. He wanted daily stand-ups, direct access to the development team’s Slack channel, and the ability to "pop in" on weekend deployments.