[leokennis]

The issue is, if you create an internal tool that allows you to order printer paper for your departments printer you might name it "PaperSupplier": https://papersupplier.acme.com. If it doesn't work, just send a mail to [e-mail]!

And it works so well, the company now also wants employees to order staples and hole punchers through it.

What do you do now?

Are you going to rename the tool, change the address, change the e-mail?

Or is your company now going to have you order your staples through "https://papersupplier.acme.com"?

We all know it's the second.

My strategy would be to go for very generic names: even though it (initially) only allows you to order paper, name it "Internal Supply Portal" or something.

[tauwauwau]

You are right that function may evolve over time and name may not be completely accurate but it's still partially accurate opposed to being being completely inaccurate. In your example papersupplier, I would want to create a new site for staples or better create a new site for all categories of stationary instead of modifying the old one.

I like the idea of having a generic but still descriptive name.