I had a similar challenge late last year and wrote a business plan for a
CMS. I believe I got the template from one of the vendors we decided
against (they're all very helpful when it comes to helping you sell
their software to upper management).
Anyway, after the executive summary, I described the benefits, our
current situation, and why our existing tool-set wasn't helping us
accomplish corporate goals.
The logistical part was the hardest. I had to address such concerns as:
* What other departments would be involved and how much so
* Responsible, Accountable, Consulted and Informed resources (RACI)
* Staffing requirements
* Training and support costs
* Security and continuity issues
* Milestones and dates
* Quality assurance
* Financial aspects
* Statement of Work
* Comparisons with other researched solutions
It wasn't easy, but well worth the effort. The plan was approved and
we're in the process of negotiating the purchase with the vendor. Soon
the real work will begin, but frankly I'd be flailing with the effort if
I hadn't gone through the process of creating the business plan.
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of Ann Balaban
Sent: Monday, February 18, 2008 07:21
To: framers at lists.frameusers.com
Subject: Software Purchase Justification
Have any of you written a software purchase justification? I am trying
the Adobe Technical Communications Suite and my boss says I'm missing a
things in my justification. If anyone has any examples I could use, I
abalaban at tsystem
You are currently subscribed to Framers as glenn.voyles at mitchell.com.
Send list messages to framers at lists.frameusers.com.
To unsubscribe send a blank email to
framers-unsubscribe at lists.frameusers.com
Send administrative questions to listadmin at frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.