Some stories about evolution of Atlas at Sage (and how your current woes had been in unintentional planning for awhile):
1. Factoid: The original project manager of the Sage's SAP implementation by Deloitte Consulting was a former boss of mine and he came up with the phrase Project Atlas, which is in direct reference to Ayn Rand's book Atlas Shrugged. He's a full-on objectivist and Rand disciple. Too bad they used Atlas as the live product name.
2. What was supposed to be a 2 yr implementation of Atlas turned into 4 years (as of 2009) and shortly thereafter it starting rolling out to some Sage campuses. The cost overrun in meantime was staggering and clearly not budgeted for. The product you have in the end is klunky, not user friendly, slower, requires more steps. This is even more true for the Sage employees in Sales and Support who have to use it.
Some of this had to do with Deloitte themselves (who apparently has a rap sheet) and their team of ""brainy-acks"", how they carried around the original project specs like a Bible ready to quote verses to avoid changes and improvements, their many delays, and how they played the blame game.
Also the product itself (SAP) was klunky and whether you looked at it from Sales or Support perspective there were square pegs in round holes everywhere. Every request to make it more user friendly added more costs.
Also no one at Sage truly had any idea of how customized all the current CRM systems in use were when you looked at all the campuses. Remember every campus in North America was an acquisition and they were all using their own disparate systems. Over the years the number of CRM mods on those systems grew and grew and many weren't documented well and all this came out as a surprise AFTER the initial Deloitte project spec'ing (you know this story well with your own clients). Naturally this contributed to lots of change orders.
Also it was to easy to see when we saw alpha versions it was so not the right fit (SAP itself without consideration to Deloitte ), not the right product and there was still a sh-load of money to still be spent. But too much money had been sunk already to pull the plug.
It's a case study of poor enterprise planning and lack of cost controls:
* Rushing to find the singular solution to replace all the disparate systems (my guess is a performance bonus was tied to a due date on this just like it was when the bad fit pre-Atlas Knowledge Base for MAS 90 and 500 was rolled out)
* Poor assessment and research of SAP as the right enterprise solution
* A deceptive implementation partner
* Surprise of how many customized and disjointed existing systems there were and ergo project underbudgeted to deal with
BTW here are some other Deloitte SAP projects with stories similar to Sage:
http://www.courthousenews.com/2012/03/12/44615.htm
http://goo.gl/NrVGS
My opinion - Last thing - the 1st live roll-out of Atlas was in 2009 coincided with timing of largest labor force reduction --> cost recovery .. I'm just saying