Clients passing off broken processes as system requirements
Clients submit lengthy requirement documents that literally just type out their current broken workflows in bullet points. When an audit reveals what they must do to fix their messy systems and enable new capabilities, they refuse the solutions because they do not want to change.
Core Friction Pattern
Analysis of 2 peer accounts across online developer and community forums reveals that “Clients passing off broken processes as system requirements” repeatedly surfaces due to edge-case mismatches between standard defaults and real-world environments. Standard troubleshooting frequently falls short, compelling practitioners to develop custom workarounds.
+1 alternative community-tested workaround cataloged below.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
Clients passing off broken processes as system requirements
- 1Start with a small, highly visible fix for sales reps to build momentum and secure buy-in for larger changes.Did this help you?
- 2Bill by the hour to protect yourself financially when clients resist the necessary work.Did this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“Client: I need help, our Hubspot is mess, our Sales people are just doing whatever they want, etc etc Me: after deep research/audit - Ok, you have to do this, this and this. Otherwise you can't do xyz (AI Agents...) Client: no, not like that! We don't want to change!”source ↗
“My client just sent me a 47-page "requirements" doc that's literally just their current broken processes typed out in bullet points.”source ↗
Where this came up
People with this problem also raised
Related community dilemmas clustered by discussion consensus
How to document company processes that only exist in people's heads
Internal processes are usually fragmented across employees' minds with conflicting versions depending on who you ask, making standard documentation efforts take months instead of weeks. This leaves companies dependent on a 'bus factor of one' where critical knowledge disappears when key personnel leave or retire, resulting in written manuals that bear no resemblance to how work actually gets done.
Why built-in software AI features don't fit real work
Generic software AI tools are added just to stay relevant rather than matching daily workflows or communication-heavy demands. Because the features are disconnected from how people actually work across multiple tools, professionals ignore them entirely except for basic note synthesis.
Why do internal auditors ask for so much useless information?
Internal audit and compliance teams demand endless document requests and procedural changes without understanding daily operations or month-end close. Trying to satisfy these endless, nitpicking questions while keeping up with normal tasks prevents teams from focusing on work that actually adds value.
Helpdesk alternatives to an overwhelmed shared inbox
Shared email inboxes require manual sorting and tagging every day, which easily overwhelms teams and allows inbound customer requests to get missed. Moving to a dedicated ticketing system automates the routing, but enterprise platforms like Zendesk or ServiceNow often introduce prohibitive implementation costs, forced features, and frustrating interfaces.
How to explain a major tech outage to management
Translating a technical disaster into business speak for upper management leaves engineers sleepless and deeply impacted by the stress. When management has previously insisted on tools like MS 365, however, they may not seek any explanations or questions about the failure.
Why do big companies require so many rigid formalities?
Large enterprises enforce strict communication rules and documentation templates primarily to create a visible paper trail of active work rather than to aid team handoffs. This bureaucratic overhead forces employees to suppress their individuality and navigate rigid standards of professionalism, leaving them questioning whether they can survive in corporate culture or if they need to return to smaller companies.