And regardless, people should finally take this to heart:
If something is important to you, back it up in a format that you can read with offline software. I don't care if you store it on punch cards under your pillow or in The Cloud, so long as it's independent of the primary copy (such that you can access it regardless of access to the primary copy, and such that you don't need the original service to load the data in order to read it). It doesn't sound like that was the case for your friend.
The real lesson here is to never put anything sensitive or personal on corporate devices/services.
I don't think it's the password manager's fault, mistakes like that can happen if you don't double check whose the account is.
I used to do what you described but my base password was rejected by far too many sites because of absurd (and insecure) requirements.
Stupid requirements don't matter. If you have a secure password, e.g. a passphrase consisting of 7 random words (diceware) and the service complains that you're missing digits, uppercase, and symbols, then adding A0! to the passphrase does not make it less secure. Appending anything never makes it less secure. You can also write down in plain text and store on pastebin what you added per site because it's not part of the secret anyway. (Okay okay, might as well keep it private rather than pastebin; it's about the general point.)
> like 12 character max
This is not that common anymore, most services have reasonable limits. If you do run into one and it's too important not to use, then you don't have a choice anyway: you'll have to make an exception to the scheme and memorize or store an actual password for once. Doesn't mean you have to design all your other passwords for one exceptional case.
And while the 12 char max is (mostly) a thing of the past, I run into max char issues (usually around 24) far more than I should in 2021.