- Tell how many users you need for the system. If there are different groups of users such as internal and external reviewers, or occasional users, try to differentiate among them. The number of users make a big difference in the price of software licenses.
- Tell us your budget. I know this seems impossible, but it would save a great deal of time for the buyer and the seller. Buyers have budgets set before they send out solicitations, and some proposals are rejected because they are outside the budgeted amount. Even bids that are too low may be rejected as unrealistic.
- Be specific about requirements. Tell us the details of your particular process and especially what you think makes it unique. Include samples of forms and documents that you use, or the manual for the system you are planning to replace. Describe your processes and workflows step-by-step in plain English, either as use cases or in another format.
- Describe your environment and your hardware and software standards. How strong are these preferences?
Now for some items that you should not include in an RFP:
- Platitudes are not requirements. If I had a nickel for every time I saw "user friendly" or "completely integrated"... These are meaningless expressions that don't help you get a better system in the end.
- Unless you have already chosen a vendor and the bid process is a formality, don't ask vendors to claim they have done exactly what you want with a customer exactly like you. This may eliminate some innovative proposals that might save you time and money.
- Don't ask for open-ended integration. I have seen several RFPs which ask for integration to other systems which are not even named (or the dreaded "etc."). Integration costs cannot be estimated without detailed information on the systems to be integrated and a definition of how that integration will work.
I have seen several strong RFPs recently which included significant detail and seem likely to result in successful projects. Perhaps the tide is turning and quality will continue to improve.
For more information on grant management and Grants Manager Plus:
5 Ways to Ensure Compliance with Your Grant Management System
6 Things to Look for in Grant Management Software
Estimating the Cost of a Microsoft Grants Manager Plus Implementation
Extending Grants Manager Plus
Flexible Grant Management Software: Long Term Considerations
Grant Management for Community Development Block Grants (CDBG)
Grant Management Portal: What to Include
Grant Management with FedRAMP Certification: Microsoft Dynamics 365
Grants Manager Plus: Theme and Variations
InfoStrat Grants Manager Plus Review on FinanceOnline
InfoStrat Releases New Version of Grants Manager Plus
InfoStrat Releases New Videos on Grants Manager Plus
Microsoft Grants Manager Plus
Microsoft Grants Manager Plus Frequently Asked Questions (FAQ)
Online Resources for Microsoft Grants Manager Plus
Portal Options for Microsoft Grants Manager
Statewide Grant Management Systems
The DATA Act Driving Grant Management Automation
The Story of InfoStrat and Grant Management
Usage Scenarios for Microsoft Grants Manager
User Stories for Grants Manager Plus
Understanding Budget, Payments and Milestones in Grants Manager Plus
Understanding Grant Management Data: CDBG-DR Programs
Understanding Programs in Grants Manager Plus