I know what it's like working in a place where ten things are asked of you, but you can only do six of those things. You ask the user.. Does project F need to do 'squats'? And they say "no no.. that's not needed, no.. will it be easier without 'squats'? Then don't do them..'

So you repeat yourself, Are you super duper sure project F will not need squats? I feel it might at some point require squats, and without squats, this is a just a hack of a solution, which is ok.. but if someday project F will require squats.. we might as well do them right now.

How long has perlmonks been around? How was it created? Who implemented the login system? Was it changed at some point? Did the person in charge get handed this as project B...
Jack: Let's go live with project B.
Jill: No way, the login system's not done.
Jack: Waddya mean? It's working fine!
Jill: No no.. that's just a hack for development, it's not production grade..
Jack: Look, let's focus on 'situps' for project X, we can come back to the login for project B later, at this point it's working fine..
Jill: I dunno, Jack.. I think we need to-
Jack: Look, we really need to do 'situps' for project X..

At this point, when someone has the time and space to 'unhack' something, is the tast daunting? Is it overwhelming.. is it.. who knows. It sounds easy enough. But maybe not- It's not really starting a system from scratch anymore.