I agree with the prior response regarding having a story. And that story should be around the relevant benefits of your software, not the features.
Prepare by starting with, “What is it your customer wants to do?”
If you don’t know the answer to that question, you’ll never be able to craft a story on how your software will help your prospect do it better? Nor will you be able to determine the right benefits to highlight.
Also remember that only a fraction of what your software can do will be relevant to the issues of any single prospect. Don’t bore the prospect with details that are irrelevant to their situation or need.
Part of answering the first question is knowing what to highlight in your story. Your homework is to know how all your features work in great detail. This helps you incorporate the appropriate benefits of your features into your story.
Take a mobile phone email software application as an example. It has a lot of features. But what is really valuable for the prospect is that it saves time and avoid surprises.
It saves time by letting you clear out emails: while commuting, while you’re waiting in the dentist’s office, while you’re waiting for your order to arrive at lunch. When you finally get to your office, you’ll be caught up! You can easily build story scenarios around that.
It also helps you avoid surprises by letting you periodically check email wherever you are. If you’re out of the office there will be no ticking time bombs there when you get back to your PC. A story about employee A with the application and employee B without and the consequences of knowing something in advance will bring that message home.
And use “you” a lot when you tell your story. Makes the prospect feel like they already own the software.