Once you've established the unique requirements for your organization (see Car Shopping and CRM Selection: Lessons from a Pontiac Grand Am), use those requirements to send out an RFP, score each vendor's response based on your requirements, and then narrow the field to your top software candidate. Now it's time to arrange a demonstration to your team. A well-executed demonstration is vital for confident selection and implementation of a new system, and your role as the NPO-vendor interface is key.
A good demonstration positions you and the vendor with a thorough understanding of where your requirements exactly fit and where they don't, so you're not talking past one another.
Before the Demo
Preparing for the optimum demo will require more of your time than you may think, but it's worth it! Sure, the vendor has your requirement checklist, but you need to tailor and enrich the agenda. Create a demo script based on your use cases, and unique requirements, to help elucidate system differentiators. JCA recommends sending the script to the vendor three to four weeks before the demo.
You'll also need to think about which of your colleagues will be in the room during the demonstration. Don't invite everyone to the demo. It's tempting to show everyone everything, but this will likely not yield the results you want: honest and deep evaluation of the proposed system. Pick a few, key people for your "Primary Evaluation Committee," and involve them as you develop your script. Select them from specific functional areas, make sure they understand the demo script and scoring system, and invite them to attend the meeting during pertinent, applicable use-cases. You need focused attention and feedback, not just seats-in-chairs.