The next step would be to outline a product or service roadmap that would let the business know what you are working on and in what order. Starting out small with your rollouts tends to go better than "revolutionary" changes throughout and entire business infrastructure. Plan on communicating your successes throughout the entire business so you can ease into some of the changes that might be disruptive later on. "Build a little-Test a little" strategies are often appreciated by the business partners as it affords them an opportunity to participate in small programs and provide valuable feedback.
Picking infrastructure elements that will not preclude the addition of "best of breed" providers later on has proven time and again to be a winning strategy. There is little need to narrow your options too early in a process only to be disappointed later on that certain functions can not be added due to infrastructure limitations. The more standards based elements you can utilize the better things will be later on.
Gaining credibility with your business partners on small projects that are deemed helpful to them in the performance of their job functions is also a proven methodology. Say you can eliminate the use of Fax for taking orders from customers where no one can remember why they are doing by fax in the first place. They will thank you profusely and give you half a dozen other functions to automate for them. Your strategy is now working!
This was first published in February 2008