A colleague turned me on to an article here that talks about 5 stunningly awful mistakes for demos. I don’t think these are all that bad, and certainly not stunning, but I’ll include the 5 here, as we have a few more practical ones to add after:
It used to be, years back, that a certification meant that you were knowledgeable. Problem was, it really only meant that you were able to pass the kind of test given, and that you had enough short term memory to cram for the test’s material. Certifications do not now, nor have they ever, indicated wisdom or knowledge in the application of one technology into the infinite variety of prospect environments.
If anything, these days too many certifications mean that the person has no time for a real job in the real world, and is virtually useless in a Sales Engineering situation. With thousands of certifications for thousands of applications, which ones do you pick? Oh yeah, and there are more every day! Would you bring a perpetual student on the most important sales call of your career? Of course not. More »
[AS2, Flash CS4 Professional]
This might sound silly, but it is extremely useful. I just did a job for a client that needed to rotate their banners on a site that they had done for them 4 years ago. The site was hard coded to:
MovieA_______________________________________________
loadMovie(”flash/MovieB.swf”, intro_mc);
intro_mc is a simple, 1 frame movie in MovieA’s library that holds a Rectangle shape the size of the banner area. You use this rectangle to precisely position the asset in Movie A. intro_mc is placed as soon as it is needed, sometimes before the frame here that loads it.
MovieB_______________________________________________
This movie has the job of loading banners and displaying them. This is a great approach for lots of reasons, but for us the most important is that we don’t have to hard-code our banner rotation worker, MovieB, into MovieA or any other caller.
MovieB loads it’s movies from an XML file called banners.xml, which looks like this:
In this article I talked about my 6 D’s of projects, objectives, goals, sales, designs, etc. For this short article I’ll do a little follow-up to explain another aspect of the same methodology.
There are only 2 buckets that any sale or project ever falls into:
Business Need – They want something they don’t have.
Business Solution – They have something they don’t want.
Based on whichever you are presented with, my 6 D’s will produce something different. Let’s look at each:
One example illustrates how my methodologies help secure business. On my blog I focus on Sales Engineering, and bettering the profession. In this article I discuss the importance of methodologies in the sales process, and one of my high level methodologies. This methodology alone secured the largest proserv engagement in Sprint’s history ($4.5M), and was directly attributable, per the prospect, to my methodologies. You know when you’ve done this properly when at the the start of the signing the prospect leans over and asks me which page he/she needs to sign. :)
Prospects don’t want the lowest price. They want the best value-just like you and I do when shopping. Sales Engineers are in the justification game. Anything, regardless of the price, that can be justified will be purchased. It is our job to do just that.
As for presentations, I routinely create custom flash animations in place of static PowerPoint decks (why are we still putting prospects through PowerPoint?). These serve many purposes that have secured business for our account team in the past:
More »

Categories
Tag Cloud
Blog RSS
Comments RSS

Void « Default
Life
Earth
Wind
Water
Fire
Light 