The Fulfillment Doctor On: Scripted Demos and the OMS Aug 1, 2007 1:26 PM
, By Curt Barry
JobZone
Search and post jobs for the Multichannel Merchant. Including jobs for brand & agency marketers, e-commerce, catalog marketers, ops & fulfillment, direct marketing and more.
Question: We have been investigating replacing our order management system, and we have had vendors in to demonstrate their systems. While we have spent a lot of time, we don’t ever seem to see the whole system or the particular features that are critical to our business.
Answer: Two words: scripted demos.
First, there are two types of demos. The first type, lasting one to two hours, is used to get the general feel for a system early in the search process. What you get is a high-level overview of a couple of system functions. The second type of demonstration, which lasts six-to-eight hours, is the kind we'll focus on. This longer demo is used to select the finalists after vendors have responded to your request for proposal.
Remember, the job of the salesman is to show you the strengths of the system he’s selling. Your job is to make sure that you have done your due diligence to determine which system fits your business best. In working with our clients on hundreds of order management and warehouse management systems projects, we have found the most effective way to make that determination is to literally script what it is that you want the vendor to demonstrate.
By scripting the demo we mean getting the vendors to show you the features and functions of the software at a level of detail that allows you understand how it would fit your business. You take control of the demo content, the agenda, the data to be presented, and the amount of time the vendor will spend on various subsystems.
Here are some guidelines:
• Who are the key department users? They should prepare a list of specific items or functionality they want the vendor to demonstrate from the RFP responses (e.g., promotion set-up, blanket purchase orders, item master, quantity price break discounts, etc.).
• Start with your user requirements. What were the essential functions that you needed? Which do you think are unique to your business? These may be loyalty clubs, discounting, carrier rate shopping, bill-me-later, product numbering schemes, etc.
• Make sure that the vendor has your media (catalogs, inserts, Website URL, etc.) and uses data that you have prepared to demo his system. Dummied-up customer records, products, and SKUs, different discount options (free freight; buy one, get one free), kitting/de-kitting, product numbering, length of fields (e.g., name, address, SKU).
• Write out a literal script and a time agenda, including the order of topics to be demonstrated. If you don’t conduct the demonstrations in the same way and following the same sequence, you won’t be able to compare one system to another. This is a major reason for taking control of the demo.
You should recognize that of course the vendor has his own agenda—ask for it in advance, view it, and only use that portion of it that benefits the system selection process. Let me give you an example. Vendors always want to start with a detailed background of their business. You do need to understand the company, its market, who the installed customer base is, and so on. But can’t you do that over the phone or through Webinars? Remember that you are doing the demo after presenting your requirements and receiving a response back from the vendor. The vendors who are going to conduct these demos are already on the short list.
• Assign a “scribe’ to document the key pluses and minuses of each system as well as vendor follow-up items. Department users should be responsible for keeping track of any changes, follow-up items, or feature/function that appears to be a strength or weakness. Don’t rely on the vendor to take the notes. Don’t think that you will remember or be able to recall what you saw after the fact.
• Use the demo to validate the vendor responses in the RFP. You should go through any major requirements that you questioned or didn’t understand, or any for which you want to see how the function works.
• Update the RFP response with any changes or new impressions based on the demo.
• Mark results on a score card. After the vendor leaves, get the participants together to score their impressions on each functional area, A–F, and enter key observations on a form. For what functions do key users need more explanation? What are their concerns?
• Follow up with a memo to vendors of items they agreed to research, and include any outstanding concerns and questions. Some questions may require an additional demonstration of a specific function or functions, this should be easily accommodated by the vendors through a Webinar.
The better prepared you are and the more firmly you take control of the demo, the better you can ensure that the system fits your business.
Curt Barry is president of F. Curtis Barry & Co., a fulfillment consulting company. For more information , visit http://www.fcbco.com.
The Fulfillment Doctor On: Scripted Demos and the OMS
