People assume the constraint is typing speed. It is not. The constraint is how many things can be wrong at once before you stop making progress.
So the first rule is that anything done twice gets automated. Deployments, backups, error alerts, dependency updates. An hour spent automating a weekly task pays for itself inside two months.
The second rule is shared foundations. All five products use the same auth service, the same payment ledger and the same component library. A bug fixed once is fixed everywhere.
The third rule is the hard one: refuse features. Every feature is not just built once, it is maintained forever. I now ask what we will remove before agreeing to add.
None of this is heroic. It is just refusing to carry work that does not need carrying.