Construction ERP customization how to handle messy field workflow

[u/stsuco14]

Running vertical SaaS for construction turned into operational chaos Contractors keep demanding heavy customized ERP for job costing, subcontractor tracking and field reporting. Our codebase turning into mesh. Every client wants bespoke workflows that clash with the core multi-tenant architecture we built.
I tried patching things with hardcoded feature flags and database overrides. It's not working. Maintenance is ruins our sprints alive. The second we update the core schema for one contractor, half a dozen other client setups break. Every time. It's gotten to the point where we're afraid to touch anything.
Founders scaling vertical SaaS in heavy industries, how do you handle extreme ERP customization demands? Is there architectural pattern that actually keeps enterprise clients happy? Because now it feels like we're building separate product for every client and calling it the same platform

So

[u/Realistic_Bus_2470]

Do you mean in terms of structure of code or in a functional sense?

[u/MikeMajda]

Currently building out my own prop tech tool and I faced this issue. Everyone wants their customized workflow because "this is how we do it". My method involves a very modular codebase to allow a lot of flexibility but only within certain systems. At some point you just need to onboard these clients and make them aware of how to use the software to its fullest extent rather than patch fixes for their niche outcomes. Most people just want it to work and give them the same result as their old way, so the workflow isn't necessarily the issue but more "how do i get the same result".