true, but don't forget strategy projects tend to be short, on avg say, 6 to 12 weeks while ERP lasts almost a year. If there is a consistent stream of strategy related work, the strategy revenue is also significant (though annual revenue will still be small comparing to ERP since more people needed in one ERP project comparing to strategy).What I hv seen in this part of the world is that the ERP people wanting to win the project (it is a competitive landscape since ERP is almost a commodity nowadays, unlike in the late 90s), usually promise the client a free strategy evaluation projects for FREE. In these cases, the strategy team only get cost recovery (usually from hardware team as ERP projects bundle with hardware and software teams), and the outcome of the strategy project should mainly lead to the need to improve IT and system integration. At the end of the year, strategy team tends to get cost recovery and the work sucked, so consultants leave (and they start bringing in ERP/SI/ Outsourcing people into strategy group). Worst, IBM gives free strategy for ERP is an open secret. The sad part now is that even if the team is really good, the clients' won't pay IBM the price they would pay for strategy jobs by other consultancies since they can sometimes get it for free. Plus, when the free piece of strategy work start looking like a canned food (conclusion either didn't make sense or always conclude the need for IT), don't expect the client to look for IBM when there is a real serious strategy work - even if it is free or 50% cheaper than the nearest competitor. Clients' ain't stupid. IT/system is a tool and it won't solve all business problems. IT will be a powerful tool only if one know what one need for the business.