Ask for the PowerPoint someone sent to a prospect last week. The one with a slide copied from an old deck, ideally. I’d like to know what’s on that slide and why it keeps finding its way back in.
Say it’s an implementation diagram. It’s a bit cramped and the arrows could do with some attention, but it shows exactly when the customer’s IT team needs to get involved. Their head of IT can look at it and say, “Fine, but we can’t do that until September.” That’s a useful conversation to have before anyone signs anything. It’s also a good reason to keep the diagram, even if the new brand guidelines would make it look quite different.
There’s a risk in simplifying an identity from the homepage down. Everything gets a bit more consistent and some of the useful oddities disappear. The sales team quietly puts them back.
What the salesperson says over the slide
Take a hypothetical security software company. Its product helps analysts decide which alerts to investigate first. The sales deck has a screenshot of the dashboard under the words “Prioritise what matters”. During the demo, the salesperson points to two alerts with the same severity rating. One affects the checkout. The other is on a test server. That’s the moment the buyer sees what the product brings to the decision, and it happens somewhere between the salesperson’s cursor and the sentence she’s halfway through saying.
I’d put those two alerts on the slide. Keep the identical severity ratings visible and label the affected services in plain English. You can lose most of the dashboard at that point. The buyer who forwards the slide to their boss now has something to point at.
If the company shows this sort of comparison often, it’s worth designing a few versions. Put the service name in the same place each time. Make room for the label that takes two lines. Try it with three alerts, because somebody will need three by Friday. The arrangement can become familiar across the website, the demo and the proposal precisely because it keeps helping people read something they need to understand.
How much of a rebrand do you need?
Before settling on a rebranding strategy, give one of those slides to someone who didn’t sit through the pitch. Ask what they’d write in the email if they had to forward it. “It shows why we’d deal with the checkout alert first” tells you the example is doing its job. “Looks like another monitoring tool” gives you a reason to go back to the product team and ask what customers are buying it for.
There might be a fairly small design job here. A sales team working from six versions of the same deck probably needs a few decent layouts and an afternoon to try them with real material. If the team struggles to agree on what those slides ought to say, you’ve got a positioning question to settle before you spend much time on the layouts.
When we look at a rebrand at Studio Gallant, the deck that went out last week is a good place to start. Send us that one, including the slide you usually have to explain.
Related reading: The fastest part of a website project is rarely the bit holding it up.
Photo by Slidebean on Unsplash.
