Archives for posts with tag: B2B

In a recent post I explained that the 4 basic questions you need to cover when you introduce yourself is who you are, what you do, who you do it for and why it matters.

A really good follow up question from someone who is sufficiently engaged with you is ‘how do you do that?’ They’ll only care about the how if they’re genuinely interested or they’re making polite conversation. This got me thinking about how I would explain the process by which I get companies to accelerate their time to market and their sales growth.

Imagine holding an imaginary set of bellows or a concertina in your hands. Then you bring your hands together, before bringing them apart. That’s exactly what you do in sales and marketing to grow more quickly.

You have to reduce in order to increase. By that I mean that you start with your market, then you narrow down the segments of that market until you’ve identified the ideal target audience for what you do. Then you design your offering and your marketing and sales messaging to that audience. Because it’s tailored to the specific requirements of your tightly defined target audience, you have good success and you quickly grow your business or your new product or service.

So, how you do it is by reducing to increase. I imagine that the next time someone asks me how I do what I do I will accompany my explanation by the bellows or concertina hand actions, to reinforce my point.

When we’re introducing ourselves to people for the first time, even if we’re not in the selling business, there’s the opportunity to sell ourselves, to make a good first impression, or to influence people in a positive way. They might not need our services, or to be our friend, but they might know someone who does.

So what are the four introductory must dos? I see four questions that we should answer for the person we’re meeting:

  • Who? Who are you? What’s your name? Not necessarily the organisation you’re with, your name is more important. They have to remember it. I’m sometimes not a fan of leading with yourself, but in this case they need to remember your name when you accompany it with a handshake
  • What? What do you do? What do you provide? Can you describe this simply, without jargon? This is the bit that’s going to catch their attention, since they will use it to pigeonhole you in their mind
  • For whom? Who do you provide what you provide for? Who are your customers, stakeholders, patients, students or constituents?
  • Why? Why should the people for whom you provide what you provide care? What do they get out of it? This is the bit that adds value, your chance to say what makes you different

For some people, you don’t need to cover these four bases. “Hi, my name’s John Smith, I’m a dentist.” You can pretty much stop at second base. But for others, perhaps those in more complex business-to-business roles, you’ll probably need the last two, especially if you’re networking. “Hi, my name’s Paul Dilger, I’m a sales and marketing consulting to small to medium-sized companies so they can grow their business more quickly.”

If it feels unnatural to add the fourth point, you can always drop it into the conversation later, especially if the first three points resonate, make a connection or provoke a positive reaction.

 

Funnel and Hubspot Flywheen

Funnel and Hubspot Flywheel

For decades we’ve been talking about funnels – or hoppers – to talk about how we manage sales, especially in B2B circles. Marketing throws leads into the top of the funnel, perhaps helps leads advance down the funnel, and sales pushes them down through the bottom until they emerge out of the funnel as a customer, a sale. It’s also assumed that the funnel has holes in the sides, since leads and opportunities get qualified out or are lost during their journey, but that’s not really talked about and not what I’m talking about either.

Then there’s the flywheel. The flywheel analogy and image is a Hubspot creation, – at least I think they originated it – and aims to better integrate the customer, ideally the delighted customer, into the selling process from an advocacy point of view. After all, with the funnel, once the opportunity emerges as a customer there’s not a natural way for it to come back into the funnel as a repeat customer or as an influencer to a new customer.

I like the flywheel approach, although I prefer a wheel analogy myself, and I can see where they’re going with the idea that a flywheel increases in speed due to the rotational energy of delighted customers feeding fuel to the marketing and sales engine.

Hubspot acknowledges that you still need funnels in a business that measures its success, and argues that you can put funnels within the various stages of the flywheel. That doesn’t seem particularly elegant and they don’t even try to present it visually. But, viewing your customer’s buying journey as a circle rather than a straight line certainly helps you keep your focus on developing your existing business and leveraging customers to bring in new business.

There are two types of business-to-business client. I found this out in my first job after my MBA in the 1990’s when I worked for a design and marketing agency and had to get out there and sell.

The first type of client is the type that respects your work, trusts your expertise and domain knowledge, and generally takes your advice.

The other type of client is the type that wants it done his or her way, tells you what they want, because they know better, even though what they want may not be the best for them. They respond to what they want to hear rather than what they need to hear.

The one factor that affects this division is the amount of experience and and expertise you have with regard to your client’s industry. The less you have, or can demonstrate, the less likely they’ll be inclined to take your advice and the more command and control their approach becomes.

You know the saying: ‘you get the clients you deserve’. Clients also get the agencies, suppliers or delivery partners they deserve.

The term ‘client’ is also problematic for me. We used it in the agency and some companies still use it, depending on their sector. It puts the customer on a pedestal. I agree that everything stems from the customer, and that we all should be customer-centric, but when you elevate your customer to almost divine status it makes it hard both to have a peer-to-peer relationship that’s based on trust and to strike a fair deal. Then you have a vendor/supplier-client relationship that’s unequal and approaches that of a slave-master relationship. That’s what the term ‘client’ feels like to me.

Do you subscribe to a lot of email newsletters? I do, partly because I’m interested in the content but also because some of what I do touches on the design and production of them. I almost never unsubscribe to them either. I prefer to scan the subject line, give them 2 seconds and delete, rather than missing out on some nuggets.

So it’s fair to say, then, that I’m a fairly experienced writer and consumer of them, in both B2C and B2B environments. I have read up a fair amount on best practices for getting people to open them and beyond.

Here’s my most obvious tip. Don’t title them This Month’s Newsletter. It just doesn’t cut it, especially to a sophisticated reader who gets a lot of them.

Putting that in the subject line offers nothing to the reader and pretty much guarantees a rubbish open rate. There’s no indication of the subject matter lying within which might be of interest, so readers can self-select. There’s no call to action or invitation. This Month’s Newsletter is focused on the sender of the newsletter, not its intended recipients.

This Month’s Newsletter…who cares?

In this last post, for now, in the mini-series on product marketing in agile environments, I offer you my third thought on what has worked well for me. In fact, I talked about it briefly at the end of my second thought.

The third thought is this – and how difficult is that to say for a non-native speaker, with 2 voiced ‘th’ sounds and 2 voiceless ones! – leave the detail until the end. The detail is the filler, the proof points, the things that are only needed when the audience has engaged and wants to go deeper.

In your earlier iterations of the content to support your new product or enhancement, you focused on the high level, the really important stuff that resonates with your audience, the reason why you developed the product in the first place. People are busy, they are subject to a constant, heavy flow of information. They don’t have perfect memories; they’re only going to remember one thing you tell them, if you’re lucky, and you’re probably going to have to tell them multiple times anyway.

This is a good thing, because in an agile environment the exact detail of what you’re offering isn’t decided and baked in until the end. So your job is to build up the interest and demand with high level, highly distilled and focused messaging which helps your personas self-select. Once they have engaged and want to know more, then you can hit them with the detail which you now have.

This is the third post, and my second thought, as part of a mini-series on what to focus on in product marketing where the software development is agile and releases are small and quick fire, rather than traditional, infrequent and sometimes slightly ponderous.

My second thought is this, and it borrows from the agile philosophy itself. Approach your content and your communications in iterations. It’s no good disappearing into your bunker at the beginning of the creation process and coming out right before launch with the finished article before anyone’s had a chance to comment on it.

You need to iterate, and iterate often. Quick fire drafts get your thoughts out early and give key stakeholders the chance to sense check the direction you’re heading in and feed back so that you can adjust if necessary. Reviewers can track their changes in your documents so that when you evolve your work for a second and third look they only need to focus on the new stuff and not re-read everything again. Your job is to make sure that each new version still hangs together, makes sense and is a coherent, unified piece of work.

This is how I approach almost all of my work, including product marketing assignments. Do the homework, collate all the information, get a sense of the patterns, distil everything down to the key messages, and do a first pass. The early, high level draft allows you to align everyone’s thinking and affords you the time to change accordingly. The detail can wait til later, when you’re closer to the finish line.

 

In a previous post I introduced a mini-series offering thoughts and experience on how to do product marketing in an environment where agile software development creates a sea of small releases rather than a desert with a few major milestones affording you time to circle the wagons.

My first thought is that you should stay true to the principles of what you’re trying to do. Faced with a barrage of product enhancements and releases of all sizes and shapes, you have to prioritise in terms of your audience, your audience segments, and their personas.

What is most important to them? What will attract their customers and keep them loyal? What does your enhancement or release do to help them help their customers? Answering these questions should drive what you devote to building a story about, and, perhaps more importantly, what you choose not to focus on.

When you wear this special lens which focuses on what their customers care about, you can develop messaging which helps your customer solve these problems or capitalise on these opportunities. It’s never about your products’ features and functions, unless they uniquely guide your customers to an understanding of how you can solve their real problem, which is sometimes not the problem they think they have.

Don’t get bogged down in the iterations of your solution, get bogged down in why your customers should care about where you’re heading.

I thought it worthwhile to do a short series on product marketing in an agile environment.

Many product marketers are used to gearing up to perhaps 3 major releases a year. They have runway, they can plan with an end goal in mind, and they have time to align the resources and get the detail right.

When faced with an agile software development methodology, however, they find the traditional approach more difficult, since the cadence is now ‘sprints’ every two weeks and a release every three weeks, or something of that order. It requires a different approach.

First, however, some definitions are probably in order. By product marketing I mean the process of influencing customers to buy – and enabling sales people to sell – business-to-business products. Agile software development is the process of developing software in iterations and a bit at a time, allowing for flexibility and course correction on the way, rather than traditionally going from a start to a finish line in one big go. Noice that I’m not talking about agile marketing, which is essentially doing marketing activities in a way that borrows from agile software development.

What tends to happen to marketers not used to agile are the following symptoms:

  • You’re not sure what you’ll be getting in the end product
  • You’re not sure when you’ll be getting it (stifle your sniggers if you can make that argument for traditional development…)
  • Stuff happens and the product is out there before you’re ready or before you even know about it

What product marketers generally prefer is a small number of large meaty releases that they can get their teeth into. With agile you can sometimes feel you’re faced with a roadmap littered with lots of small releases, all vying for attention.

It’s against this background that I thought the subject warranted a mini-series. Stay tuned if this is your bag. If not, feel free to click away…

Software can help us improve our productivity and automate our operations, which in turn can feed better revenues and increase profitability. Many of us feel strongly that automating B2B processes are the way to go. Removing manual tasks helps people focus on the areas where they can really add value.

With new software coming in, it’s easy to forget that you’re not actually buying software, you’re buying change. This is where the problems start, because you need to manage change. It’s not something we humans are particularly good at it. It’s why 70% of change programs fail.

With any kind of change program, you also need to change your processes. Before you start the change, you need to audit, improve and tweak your processes. Then, with the new processes in place and properly embedded, you can bring in the new software, the change.

If you don’t do this, you’re simply spending money and automating the mess, the current mess you have.

And that’s probably worse than doing nothing at all.