The demo script is the script for conducting demos. It lists all the requirements the buyer wants demonstrated and demo instructions for each requirement.

<aside> 💡 The Demo RFP and the Demo Script have identical requirements.

</aside>

1. The demo script is organized as the business flows, i.e., from receiving the customer order to fulfilling that order. Clients expect the demo to proceed in the script order, but you can change it.
2. The “Sort” number controls the order of items in the demo script and has no other significance. The sort number may change, so don’t use it as a reference. Rather use the Req ID (requirement ID) because that does not change.
3. During the demo, let your audience know what requirements you are demoing, e.g., with a slide that groups related requirements together.

1. During the demo, show how your software meets each requirement on the script.

   <aside> 💡 Requirements:

   • Requirement descriptions specify WHAT process the software must execute to create value for our client and WHAT process outputs are expected.
   • Requirements are precisely written to include only one “WHAT”. Usually, you will fully meet that requirement.
   • We don’t specify HOW your software should do the WHAT; that is up to the developers. </aside>

2. Your demo will be recorded. After the demo, the client may request that we review it to see how well it meets each requirement. If there is an item on the demo script that you do not demo, we assume that your software doesn’t meet that requirement and will rate it as “Does not meet”. Likewise, if there is a requirement and you only demo a partial fit, you will get rated as “Partly meets”.

3. We will compare the fit score from the RFP with the fit score from our review. If there is a difference between the fit scores, we assume your RFP fit score is “over-optimistic” by that amount.

Using the demo script

You can find the demo script in the Navigator from the home page where the RFPS are at:

• Along the top of the grid are two counters:
  • Parent requirements have a White background They are used to group leaf requirements. Parent requirements have no demo instructions because there is nothing to demo.
  • Leaf requirements have a green background. Leaf requirements have demo instructions that you should follow to show how your software meets that requirement.
• You can search any column with the search box at the top of that column.
• You can change the sort order by clicking the double headed arrow at the top right of a column. Click twice to reverse the sort order.
• You can drag columns wider or narrower (as you mouse between the column headers, a blue vertical bar appears. Drag it to change the column width.)
• The demo instructions column describes the functionality the software buyer wants to see from the demo of that requirement.
• You can use the 👁 icon at the top right of the grid to open a list of columns and use the checkboxes to turn columns on or off.