The main benefits of using a demo script are: It facilitates a similar demonstration from each software vendor, and hence You can more easily see how each vendor would (or not) meet your needs and requirements It enables an easier comparison of the vendors Staff can attend just the part of the software demonstration that’s relevant to them It is more detailed than an agenda or ‘software demonstration checklist’

DETERMINE YOUR OBJECTIVE FOR / LENGTH OF THE DEMO SCRIPT

If you are looking for a demo script to help give you a good overview from a 2-hour demonstration, then keep the script much shorter and less detailed than one for say, a 2-day software review.

DETERMINE THE DATA TO BE USED IN THE SOFTWARE DEMONSTRATIONS

Your choices are: Use the vendor’s data – less work for you and the vendor, possibly confusing but probably acceptable for a short overview demonstration. Use your data – either a copy of some real data or dummy data you have created. It’s much more work for both you and the vendor, but you will see the system with recognisable data. And this may be very useful if you are looking at critical or complex processes in detail.

THE KEY STEPS

The key steps to creating a software demo script based on either your own systems requirements document or one of our RFI/RFP Templates, that you have completed, are: 1. Make sure you are working in Excel or spreadsheet software. It’s much faster and easier to amend than a Word / word processing document. 2. Delete all unnecessary items from your original RFI/RFP Template (requirements spreadsheet), to leave only your mandatory and high priority software requirements to form the basis of the demo script. So delete the following: o all low priority or nice-to-have software requirements o all non-functional requirements eg support, training needs o all unrequired software functionality o possibly even your desirable or medium priority requirements (depending upon how much detail you need) 3. Check that you have included all your commonly used processes and that the ‘requirements’ left in the demo script spreadsheet follow these processes from start to finish. Add any critical processes or steps, which have been omitted. 4. You may have some complex processes / system requirements, which you need to ensure are covered by any new software early on in your evaluation. If so, add these in. 5. Optionally, you could amend the requirements to form statements about what you wish to see demonstrated. Alternatively, you could just add a comment such as “Please demonstrate the following software functionality” at the top of the demo script. 6. Within the spreadsheet, add extra columns to enable you to collect additional information during the demonstration eg o Time to complete a system task o Number of steps to complete a system task o Complexity / ease of use o How well requirements are met o Notes or other information you require Consider using a simple scoring method eg (0) requirements not met, (1) partially met, (2) fully met, (3) requirements exceeded. NB: if you are creating the demo script from a RFI/RFP Template, delete other unrequired rows and columns as necessary. 7. Split up the demo script spreadsheet by key functions / software modules eg accounts receivable, general ledger etc. This will enable you to more easily bring in different people, each for their specific job responsibilities, rather than have people trying to cover areas they are not familiar with. NB: the RFI/RFP Templates are split this way already – so just leave them as they are. 8. Allocate a rough time limit for each key function / module you wish to cover and tailor the demo script accordingly. 9. It is probably still easier to hand write notes on paper when attending a demo, rather than typing into a laptop or tablet. So, test printing out the demo scripts. Check that there is space to write any comments against the relevant points. Review the demo script and then print out copies for attendees. 10. Obviously, you will need to communicate with the software vendors well in advance – not only to obtain their agreement and willingness to participate, but also to help them prepare. Email the demo script, data requirements, answer any questions the vendors may have or hold preparatory meeting(s) well before the software demonstration. For more software demonstration information, visit Vendor Software Demonstrations, Tips for Attending Software Demonstrations, How to quickly create a software demo script
How to Quickly Create a Software Demo Script (Or quickly convert your RFI/RFP Template into a Demo Script)

Axia Consulting

© 2020 Axia Consulting Ltd. All rights reserved.
17 New Road Avenue, Chatham, Kent ME5 9RL, United Kingdom Contact Us
The main benefits of using a demo script are: It facilitates a similar demonstration from each software vendor, and hence You can more easily see how each vendor would (or not) meet your needs and requirements It enables an easier comparison of the vendors Staff can attend just the part of the software demonstration that’s relevant to them It is more detailed than an agenda or ‘software demonstration checklist’

DETERMINE YOUR OBJECTIVE FOR /

LENGTH OF THE DEMO SCRIPT

If you are looking for a demo script to help give you a good overview from a 2-hour demonstration, then keep the script much shorter and less detailed than one for say, a 2-day software review.

DETERMINE THE DATA TO BE USED IN

THE SOFTWARE DEMONSTRATIONS

Your choices are: Use the vendor’s data – less work for you and the vendor, possibly confusing but probably acceptable for a short overview demonstration. Use your data – either a copy of some real data or dummy data you have created. It’s much more work for both you and the vendor, but you will see the system with recognisable data. And this may be very useful if you are looking at critical or complex processes in detail.

THE KEY STEPS

The key steps to creating a software demo script based on either your own systems requirements document or one of our RFI/RFP Templates, that you have completed, are: 1. Make sure you are working in Excel or spreadsheet software. It’s much faster and easier to amend than a Word / word processing document. 2. Delete all unnecessary items from your original RFI/RFP Template (requirements spreadsheet), to leave only your mandatory and high priority software requirements to form the basis of the demo script. So delete the following: o all low priority or nice-to-have software requirements o all non-functional requirements eg support, training needs o all unrequired software functionality o possibly even your desirable or medium priority requirements (depending upon how much detail you need) 3. Check that you have included all your commonly used processes and that the ‘requirements’ left in the demo script spreadsheet follow these processes from start to finish. Add any critical processes or steps, which have been omitted. 4. You may have some complex processes / system requirements, which you need to ensure are covered by any new software early on in your evaluation. If so, add these in. 5. Optionally, you could amend the requirements to form statements about what you wish to see demonstrated. Alternatively, you could just add a comment such as “Please demonstrate the following software functionality” at the top of the demo script. 6. Within the spreadsheet, add extra columns to enable you to collect additional information during the demonstration eg o Time to complete a system task o Number of steps to complete a system task o Complexity / ease of use o How well requirements are met o Notes or other information you require Consider using a simple scoring method eg (0) requirements not met, (1) partially met, (2) fully met, (3) requirements exceeded. NB: if you are creating the demo script from a RFI/RFP Template, delete other unrequired rows and columns as necessary. 7. Split up the demo script spreadsheet by key functions / software modules eg accounts receivable, general ledger etc. This will enable you to more easily bring in different people, each for their specific job responsibilities, rather than have people trying to cover areas they are not familiar with. NB: the RFI/RFP Templates are split this way already – so just leave them as they are. 8. Allocate a rough time limit for each key function / module you wish to cover and tailor the demo script accordingly. 9. It is probably still easier to hand write notes on paper when attending a demo, rather than typing into a laptop or tablet. So, test printing out the demo scripts. Check that there is space to write any comments against the relevant points. Review the demo script and then print out copies for attendees. 10. Obviously, you will need to communicate with the software vendors well in advance – not only to obtain their agreement and willingness to participate, but also to help them prepare. Email the demo script, data requirements, answer any questions the vendors may have or hold preparatory meeting(s) well before the software demonstration. For more software demonstration information, visit Vendor Software Demonstrations, Tips for Attending Software Demonstrations, How to quickly create a software demo script
How to Quickly Create a Software Demo Script (Or quickly convert your RFI/RFP Template into a Demo Script)
© 2020 Axia Consulting Ltd
All rights reserved. Contact Us

Axia Consulting