Getting a software Request for Proposal, also called RFP or RFQ (Request for Quote), wrong can be an expensive business.

Ensuring a new software system meets the expectations of the company was the most common and important factor raised by research from 250 IT business heads in our latest white paper.  The must-read white paper offers valuable insight for IT business leaders and highlights common reasons for project failure.

The following areas are common reasons given for project failure:

1. Unrealistic expectations for the finished system on the part of the user/management
2. Scoping - defining the parameters of development
3. Project delivered late/unrealistic timeframe for completion
4. Poor project/supplier management
5. High total cost of ownership (software more expensive to own than budgeted for)
6. Project delivered over-budget.

Avoiding these potential pitfalls is crucial when writing a successful RFP. If it is not done correctly, it can produce no bids or responses that don't deliver what you need.  Spending time and money in the early stages of a project to ensure that you get the requirements specification right can save you a lot of money, time and headaches in the future.