Balmori Software Inc. Balmori Software Inc.We make it simple.
|
|
What to say to clients/prospects seeking GUI version of any BSI product
SITUATION: Caller or visitor asks why we don't have a GUI version of whatever product. Or asks when we are going to release a GUI version of whatever. OUR CANNED RESPONSE: We want to convey all of the following ideas, in the following order, in order to quiet the implied dissatisfaction in the questioner. 1. Sir/ma'am, actually we are working on a GUI version of [whatever product the caller is asking about]. (Reason for making this statement: The caller/complainer may be on the verge of shifting to another software app. By saying that we're currently working on a GUI version, we may be able to stop him making that decision, which is of course not in our interestr.) 2. But sir/ma'am, I'd like to point out that our current SURE! [whatever] is a text-based, 32-bit application. IT IS NOT A DOS-BASED product. Our products have stopped being DOS-based more than 15 [confirm pls] years ago. Proof of this is that all our products run without any problems on Windows 10. In fact, Windows stopped supporting DOS-based software in [WHAT YEAR?]; and yet our solutions have never had any problem running on any version of Windows. (Reason for making this statement: Too many people assume that our products are still DOS-based. We need to address this misconception every chance we get. We have to accept that people will make this mistaken assumption for as long as our products retain a text-based interface.) 3. But, also sir/ma'am, perhaps you should be aware that a GUI application will always run slower than a text-based app like our current [SURE! whatever]. (Reason for making this statement: Maybe this will make the questioner think twice about the wisdom of his quest for a GUI product to begin with. At the very least, this statement may erode his resolve to get a GUI app.) 4. Furthermore, sir/ma'am, using a mouse can get tedious and tiring. For business applications, it is usually not an option to skip input fields. This being the case, it's more convenient for the user to proceed from one field to the next, from one option to the next, by hitting Tab, or Enter, which is what our solutions offer. (Reason for making this statement: Experience has shown that some prospects seeking a GUI app are actively seeking the ability to use a mouse. This statement forces them to question their implied assumption that being able to use a mouse in a software is automatically a good thing. In conjunction with argument #3, this statement may help erode his resolve to get a GUI app. Or, may make him willing to wait until we are ready to release our own xHarbour-based GUI version.) ---------------------------------------------------------------------------------------------- I will continue refining this line of argumentation. The important things to keep in mind are: a) we need to cite all these arguments at every interaction in which a prospect brings up the topic of GUI b) we need to refine our presentation of these arguments so that we can convey our arguments as concisely and as completely as possible. Nothing follows. RSR <<< back to Client/Prospects Concerns page >>> |
|