Every business survives on repetition. It sells the same thing again and again, then streamlines operations to make that repetition as cheap and efficient as possible.
But the line between what must repeat and what only repeats because of bad design is often blurred. Too often, we accept recursion as a cost of doing business without asking whether it should exist at all.
There is a difference between necessary repetition and poor system design. If onboarding a new client requires your development team, your system is badly designed. If onboarding takes multiple days, you have probably made the wrong design choices.
This kind of monotony destroys team morale by wasting time, energy, and talent on work that should have been solved once, not solved through repeated human involvement.