产品驱动销售终极指南 | Elena Verna
The ultimate guide to product-led sales | Elena Verna
The Interview Transcript
Elena Verna: The most important thing in product-led sales is that there is a different configuration internally of collaboration that needs to occur. In traditional sales world, marketing creates pipeline for sales. Sales sells product. Product engages with a paid user to drive retention. In the product-led sales, product acquires and activates a customer and product creates pipeline for sales, so relationship is not that there’s a go-to-market org with marketing and sales and product just kind of throws features across the fence for them to sell.
The collaboration here is between product and sales, but that means the product has to take on accountability over pipeline. The worst thing that you can do is to say, “I’m going to do product-led growth,” or, “I’m going to do product-led sales and I’m going to do it in marketing.” Recipe for disaster. You’ll be failure mode within six months because product has to take accountability over selling of the product itself.
Welcome Back to the Podcast
Lenny: Welcome to Lenny’s Podcast, where I interview world-class product leaders and growth experts to learn from their hard one experiences building and growing today’s most successful products. Today, my guest is Elena Verna. If that name sounds familiar, Elena is a return guest and you be the judge, but I think this episode is even better than the first, which is a very high bar because that first episode continues to be one of the most popular of the podcast. Elena has worked at or advised companies like Miro, Amplitude, SurveyMonkey, MongoDB, Netlify, and a dozen others. She’s also a longtime instructor and EIR at Reforge where she helped create their experimentation, monetization, growth, leadership, and their soon-to-be released PLG course.
In this conversation, we go incredibly deep into the emerging space of product-led sales. Elena explains what exactly is product-led sales, how it fits together with product-led growth and sales-led growth, who and when you should consider investing product-led sales, how product-led sales changes your approach to sales and marketing, what sorts of data, tooling, and people you need in place to do it well, and what common pitfalls you need to avoid. I’ve said this before and I’ll say it again, Elena is possibly the smartest and most experienced growth person in the world, especially when it comes to B2B, and I never get tired of learning from her. Enjoy this episode with Elena Verna after a short word from our sponsors.
What users love about Linear are the powerful keyboard shortcuts, efficient GitHub integrations, cycles that actually create progress and built-in project updates that keep everyone in sync. In short, it just works. Linear is the default tool of choice among startups and it powers a wide range of large established companies such as Vercel, Retool, and Cash App. See for yourself why product teams describe using Linear as magical. Visit linear.app/lenny to try Linear for free with your team and get 25% off when you upgrade. That’s linear.app/lenny.
Take it from DoorDash, Airbnb, Plaid, and hundreds of other high-growth startups that have shaved their hiring process from months to weeks at less than a quarter of the cost by hiring through Braintrust’s network of 20,000 high-quality vetted candidates ready to work. Whether you’re looking to fill in gaps, upscale your staff, or build a team for that dream project that finally got funded, contact Braintrust and you’ll matched with three candidates in just 48 hours. Visit usebraintrust.com/lenny or find them in my show notes for today’s episode. That’s usebraintrust.com/lenny for when you need talent yesterday.
Elena, welcome back to the podcast.
Elena Verna: Thank you for having me back. I thought I would be the first returning guest. I’m a little bit upset that I am been beat by Casey, so you should explain yourself on that one.
Sharing Recent Personal Updates
Lenny: Okay, here’s the explanation. You’re the first that we rebooked back and then this one just kind of got pushed a little bit and Casey had a slot earlier, so technically you were the first scheduled return guest.
Elena Verna: All right, all right. I’ll accept that.
What Is Product-Led Sales
Lenny: Okay, great. I’m off the hook. I guess I’ll just say I am really excited to have you back. Your episode that we did maybe a year ago is still one of the most popular episodes of all time. I still see people tweeting about it and sharing it, and so I am really excited to have you back and have a take two.
Elena Verna: I’m excited to be back. Let’s dive in.
The Role of Sales in PLS
Lenny: Before we get into the content, when we met last time you were Interim Head of Growth at Amplitude. What are you up to now? What’s happened in the past year?
Classic Enterprise Problem Examples
Elena Verna: I just wrapped up interim gig at Amplitude in February, so it’s just been a couple of months since then. I’m passively exploring if I’m going to take another interim position, but between interim roles I always take about six to eight months of break because interim rolls are very intense because there’s so many deliverables that are loaded in in the first year that you’re working at the company, so I’m just advising. I have incredible companies that I started advising such as Veed.io and Sanity and Clockwise, and I’m building up my next level of frameworks that I’m going to dive into potentially a new interim position to prototype.
From Organic Demand to PLS
Lenny: Ooh. If people are listening to this and they’re like, “How do I get to work with Elena?”, should people reach out to you? Are you booked up? What do you suggest?
Elena Verna: I’ll never take down an opportunity to have a great conversation and to learn about the business and to see how I can be helpful, but I’m not proactively sourcing clients, but that doesn’t mean that I don’t have availability to schedule something in the future.
When to Invest in PLS
Lenny: Awesome, so if it’s amazing enough, you’re open to it?
Elena Verna: Absolutely, always.
Path From Self-Service to PLS
Lenny: Okay, great. Okay, here we go. Great [inaudible 00:07:07]-
Elena Verna: I always have to be-
Why Sales-Led Companies Need Product-Led Elements
Lenny: … [inaudible 00:07:08].
Elena Verna: … open to new opportunities, yes.
How Product Teams Own Revenue
Lenny: I love that. I feel the same way. FOMO. FOMO kicks in. Anyway, as you know, we’re going to be devoting this entire podcast to just one topic, which is product-led sales, which is this go-to-market motion that seems to have emerged over the past year maybe a bit longer and just feels like there’s this increasing amount of interest and also this increasing amount of confusion around what it is, how to approach it, who it’s right for. We’re going to spend the next hour diving really deep into product-led sales.
Elena Verna: Let’s go for it.
PQA, PQL, and Related Terms Defined
Lenny: Let’s do it. Okay, so let’s just start with a bigger picture kind of question of just, how do you define product-led sales? What is product-led sales, especially when it comes to what is it versus product-led growth?
Elena Verna: Great question, so let’s start with product-led growth. We’ve talked about it a little bit in our first episode, but let’s revisit the topic. Product led growth is all about product’s ability to self-serve activate, self-serve engage, and convert that usage to a monetization opportunity. You bring people, you get them to an aha moment into the habit loops, and then you able to extract value back out of them. Extraction of the value can be direct where you’re actually capturing revenue from them, or it can be indirect where they’re participating in your growth model via virality or user-generated content and bring additional business through the doors.
Let’s talk about direct phase to capture that value. There’s self-serve monetization, so I’m using product self-serve. I go to the pricing page. I find the plan that best suits me on features that I want to unlock or usage that I want to unlock and I buy it. However, that’s not the only way to monetize that usage. You can monetize that usage with sales, too. Why? Self-serve monetization has a cap of about 40,000.
Self-serve monetization is very much a prosumer use case where an individual is trying to solve the problem on their own. Product-led sales converts the usage that you’ve generated via self-serve into a sales opportunity and it attaches a salesperson to close a much larger contract, which can be 15, 20, a hundred thousand dollars in order to bring an enterprise-level solution to a company that has already been using it in a self-serve manner.
Three Lead Attribution Paths
Lenny: Amazing. Would you say that product-led growth has always been in a sense product-led sales because sales was involved and theirs has been kind of like way of describing it? Or is this a new trend and way of approaching product-led growth?
Elena Verna: Product-led growth has actually started more on individual use case-
Don’t Force PLS Into Traditional Playbooks
Lenny: Mm-hmm.
Elena Verna: … so an individual has a problem. They have a job to be done. They come into the product and they solve it, and that was product-led growth in a nutshell for a lot of the B2B companies. However, if you’re going to attach a salesperson, there is nobody in the company that is going to pay 10, 15, $20,000 for one individual to solve their problem. Product-led sales assumes that there’s a migration from an individual use case that you acquired an end user with and an escalation into an enterprise-level solution that solves enterprise-level problems. Let me break it down and let me use just, for example, Amplitude as an example.
Building the Data Foundation for PLS
Lenny: Mm-hmm.
Elena Verna: Amplitude, individual, what is individual wanted with Amplitude? I need data at my fingertips to make better decisions for my product, so I’m going to put an Amplitude SDK into my product and it gives me behavioral data to help me build my pillar better. What is the company-level solution? Well, it’s more self-serve ability of the data. It’s democratization of data. It’s enhanced insights in the more data-driven culture. That’s what company’s solving for. Individual is not solving for data-driven culture. Individual is just solving for data insights for them. Company’s solving for data-driven culture.
In product-led growth, you can just have an individual be very happy with their solution for their job to be done. However, what product-led sales assumes is that there is an escalator to an enterprise-level solution, and enterprise escalator is valuable to attach sales resources to because products fundamentally do a really bad job at communicating enterprise-level value prop. They’re very good at showing you as a user what you can do. They’ve very terrible at showing what organization actually can benefit out of the solution.
Sales can tell that story. Sales can bridge that gap, and then you can increase the perceived value in order to bridge the gap to that $15,000, 20, hundred-thousand dollar contract. I would say self-serve monetization is very much an individual use case versus product-led sales is turning that individual use case and self-serve usage into a sales pipeline with enterprise-level value.
Key Metrics and Attributes
Lenny: I really like that way of thinking about it. Basically product-led growth has a ceiling. You’re only going to get-
Elena Verna: Yes.
A Simple PQA Model
Lenny: … so high in terms of spend. You can only explain things so much to a potential user and then sales comes in and solves a lot of those problems, and product-led sales is essentially this. I think you even have this visualization now that I’m thinking about-
Identifying Key Behavioral Signals
Elena Verna: It’s a bridge.
The Cost of Sales Spam
Lenny: … as a bridge. Right, yeah, this bridge between the two, and so in this world of product-led sales, does sales as a function, outbound sales, continue to exist? One, and then two, is it radically different in this world of product-led sales?
Starting With Existing Systems
Elena Verna: Yeah, so to understand how sales should be applied in the situation, you need to understand end user’s motivation, ability, and permission. Simple organization, so for example, if the end user is very motivated, they have full sense of ability to solve the problem and they have all of the permission from organization, or maybe not even permission, maybe forgiveness from organization, to go and explore and bring in a new solution. Then, it can be a very much organic motion up that escalator. However, that’s not always the case. A lot of times the end users miss permission of solving enterprise-level problems. There’s lots of stakeholders, there’s a committee that has to make a decision. It impacts departments outside of their purview and maybe they even lack ability to do it. Maybe they can do their little job to be done, but not the entire enterprise-level integration.
In my Amplitude example, yeah, I can drop an SDK in my product area, but how do I convince entire product to adopt Amplitude and put an SDK on every single interaction across the entire app? There is different level problem statements, and this is where product-led sales is either can be a truly organic motion where people raise their hands, they submit sales forms and there’s already a need, a desire, an understanding of it, or end user might hit friction points. Product-led sales has to bridge those friction points by either attracting the right decision-makers to the process so they can find an enterprise buyer out there. They can understand who’s the champion and what their capabilities and what their permission levels are. They can create a committee for the decision.
There is… They almost slap a bandaid on the problem of people not be able to and not wanting to necessarily resolve the problem on their own. They can be very powerful with that as well as marketing because we cannot forget about marketing where they can educate of how to help people bridge that gap and how to sell things internally.
Lenny: You mentioned this idea of enterprise-level problems. It might help if you give an example or two of what those might be. Then, also, just what are examples of companies that are doing enterprise or product-led sales well just to kind of give people a mental model as you’re talking about some of this stuff?
Four Key Roles Needed for PLS
Elena Verna: Sure, so let’s go through a couple of them. Let’s go through Miro. Miro is an online whiteboarding platform. What is individual problem that people come to Miro to solve? They have a workshop they need to facilitate. Maybe they need a board to just do brainwriting in and they use Miro for individual jobs to be done. However, what Miro is designed for is a team-level problem. I come in and I bring you in and we collaborate together, so now there’s two, three, four people involved, but even that is still on the project level, it’s on the team level. Nobody’s going to pay a hundred thousand dollars to solve a team-level small problem that is solving. What is the enterprise-level problem? It’s increased innovation, it’s increased productivity across the entire team because now we have this new outlet in which we can collaborate.
Now, can Miro very clearly show increase in productivity across the organization by using the product? No. Can sales tell the story? Yes. Miro takes you from an individual user to a team step, and then sales bridges the gap to an enterprise. Let’s give another example of Figma. In Figma, I come in as a designer and I just need a better way to capture feedback from my stakeholders, a more scalable way to capture it so I can iterate on the perfect design. What is it at the team level? Now there is a team that can collaborate with me more openly. I can capture more feedback from more stakeholders faster and get the project done sooner.
What is it on the enterprise level? Well, on enterprise level, our designs are just better fit the business needs. They have faster turnaround time and our product is performing better. That’s an enterprise-level value prop and, again, we’re, I think, in the product development space gotten a little bit lazy of actually showcasing that enterprise value in product. We rely on excellence of sales team to tell that story. I do hope that changes, by the way, in the future, that we put more pressure on the products to take it all the way up the escalator so we don’t have to be a hundred percent dependent on the sales team going and showcasing that story. The product can really empower that escalator from the starting point till the end on its own.
Lenny: I want to dig into that for sure. I know that’s something you just shared on LinkedIn recently and I thought that was a really interesting topic, but before we get there, let’s talk about this bridge a little bit more. People might be listening to this that are maybe a product-led growth company and they may feel like, “Hey, wait, we’re already doing this. We have this product-led growth motion, we have a sales team. They figure out who to talk to.” What exactly is in that bridge that makes product-led sales so interesting? I imagine it’s like helping you identify who to go after, helping people go further and further and escalate it themselves. How do you think about that bridge between product and sales?
Starting Sales-Led vs. Product-Led
Elena Verna: Let’s talk about how product-led growth companies start with product-led sales. It usually starts by an organic demand from a user base. They reach out to them through support channels by just pinging people who work at the company saying, “Hey, I want to purchase this for my entire company.” That’s an organic pool that you start feeling from product-led growth model into enterprise sales world and, by the way, you should never hire any salespeople until you feel that pool because if nobody’s asking to purchase, then you cannot just hire an SDR and make a purchase happen. You need to see those hand-raisers, you need to see those people demanding an enterprise-level adoption. Then, you hire starts hiring salespeople to actually suffice that demand and that’s great, and you’re starting to do sales and surfacing really addressing organic demand within your product.
That organic demand very quickly dries up if you rely on hand-raisers of your champions. If you rely on having enterprise buyers in your user base that are asking to just sign on the dotted line, then you have a very limited ceiling for your growth because what majority of the usage transforms to be is to have product qualification that there’s a meaningful sales conversation that could occur based on the signals within usage that the buyer is missing. 90% of product-led sales is converting the usage into an opportunity by finding a buyer outside, by finding the decision-maker outside. This is where marketing and sales are so crucial in the process. Connecting that decision-maker to the usage and then driving an opportunity through sales funnel all the way to closed one deal.
It’s great when you start having sales team and you’re surfacing this organic demand. That’s beautiful and power to you. Just it doesn’t last very long just because end user fundamentally does not equal enterprise buyer and that organic demand ends up plateauing very shortly because you cannot just make enterprise buyers happen from your users.
The Zero-Sales Miracle in PLG
Lenny: If a founder is listening to this right now and they’re like, “Okay, so I have maybe a product-led growth component, they’re self-serve, maybe I have a sales team, maybe I don’t,” what’s a sign that your product is a fit for investing in product-led sales? Essentially every product-led growth-oriented company should be eventually investing in this area. Or is there certain companies that are like, “No, you don’t need to worry about it, just stay product-led growth forever or just stay sales-led growth forever?”
Elena Verna: To have product-led sales means you’re going upmarket-
Internal Collaboration Shifts in PLS
Lenny: Mm-hmm.
Elena Verna: … period. That means you going for contract values that are probably over your sales floor, so the minimum that the sales is willing to engage and close, which is traditionally around 15,000, that means you’re probably trying to close a hundred, 200,000 contract? It’s not going to be a small startup. It’s not going to be an SMB. It’s probably going to be higher end of more of a mid-market segment, so 200 employees-plus. More likely it’s going to be towards the enterprise segment of a thousand employees-plus.
If you are not ready to go upmarket, I would say keep it easy on the product-led sales because sales means quotas. Sales means large contract values. Sales means you are going upmarket whether you like it or not, and some products, they should stay in the prosumer individual space. Maybe they’re geared towards contractors or freelancers or squarely towards startups. Those persons are not interested in talking to sales in the first place. They have much lower bearing of how much they’re willing to spend, so their price sensitivity is much higher. They prefer to do all self-serve in the first place, so it’s really need to be conscious about what that will do to your go-to-market motion because it definitely skews it and pulls it up.
Why Product Teams Must Own Revenue
Lenny: Got it, so what I’m hearing is that if you’re starting as a self-serve-oriented product and you’re starting to maybe hire for a salesperson, is the approach start approaching it from product-led sales motion versus now we’re going to add the sales independent team that’s kind of doing their own thing?
Elena Verna: Right, so there’s two ways to get to product-led sales. First little wave is that we talked about, I start as product-led growth company. I really started with this individual use case and I’m escalating to a company-level value prop and this is what I need product-led sales for. On the other side, I might start as a top-down sales traditional organization, so I have product that I only sell through sales. Those are usually anchored at larger segments in the first place. In order to build a top-down sales engine, you’re most likely going after enterprise segment of a thousand-plus employees or maybe upper mid-market of 500 employees-plus. The reason to go into product-led sales is either your existing top-down motion is not working because customers need to see value before they sign the contract. They want to see that usage and at least the first signs of perceived value before they sign on the dotted line.
Or you’re going downmarket and your fixed cost of sale that you have from the traditional sales motion does not scale. It stays fairly constant, yet your contract values are starting to drop as you’re doing downmarket, so you want to create a lot more automation in the selling process to remove as many as possible humans out of it. You can approach it from both ways. Adding PLS on top of product-led growth or adding PLS on top of existing sales-led growth. For PLG, you’re going upmarket by adding PLS. For SLG or sales-led growth, by adding PLS you’re going downmarket.
Defining Revenue Targets
Lenny: Awesome, and we’re going to talk about how to actually build this infrastructure and what’s required, but it reminds me one of the biggest takeaways from our first podcast and something I’ve quoted many times now, is your bet that every sales-led growth company needs to add a product-led growth element. Otherwise, they’ll be disrupted by someone that does. Is that still your perspective?
Elena Verna: Absolutely. Now, I think there’s different stages of, what does it mean to add product-led growth elements? I think every sales-led company should be putting pressure on product to assist with the sales process. That does not mean that there is product-led growth, but there is a product assist in the existing sales-led motion that can materialize into product-led growth if you can truly solve for self-serve activation, self-serve engagement, and have product be able to sell itself. The biggest difference here that starts to come in, and that is so apparent in every single company, is that in B2B, unfortunately, we’ve let go of the products having accountability over monetization model. We’ve gotten into the spiral of product just builds a product and it throws it over the fence to marketing and sales to sell.
Marketing and sales have done an incredible job over the last couple of decades of coming up with these stories and elaborate playbooks of how to attract enterprise buyers and how to sell them this product. Product literally only obsesses after contract is closed and there’s usage that starts materialize after contract close. We’ve alleviated our product management in B2B from monetization ownership. When a SLG company actually goes into product-assisted tactics or product-led growth, the biggest pain point is actually educating product team on how can you get product to sell itself, which is all about monetization awareness, monetization friction of conversion to get into the paid plan, and then having actual correct value metrics that are understood self-serve by the customer.
I mean, yes, I agree with you. Every single… I agree with myself, so I should say that every single sales-led company should at least add some product-assisted tactics, but I would even take it further that every sales-led company should start educating and putting pressure on the product to own monetization components of the business.
Self-Service ARR vs. PQA Targets
Lenny: Let’s pull on that thread a little bit more. What does that actually look like? Does the head of product for that or the head of product or specific group PMs, let’s say, have revenue goals and responsible for P&L and things like that? Or what does that generally look like when they start to own revenue?
Elena Verna: There’s two ways that you can own revenue. Revenue stream one will be your self-serve revenue, and if there’s self-serve revenue, that means product is selling literally itself, so yes, there has to be somebody in product that has self-serve revenue target.
How to Track Monetization Perception
Lenny: Hmm.
Common Pitfalls of Product-Led Sales
Elena Verna: Now, a lot of times it doesn’t fall in the core product managers. A lot of times it falls on the growth team, and that’s because core product management is really focused on feature deliverability and just that incremental expansion of the core use case, and growth product management owns the product distribution strategy. Then, the PLG case, it would be a true self-serve monetization model. Now, when it comes to PLS, you don’t own revenue target in my opinion, but what you do own is the pipeline that was created by product that you have a handshake with sales team over.
What that materializes in is product qualified accounts, and it’s actually a product threshold of engagement that differs from activation and it differs from core engagement. It’s what volume, velocity, feature breadth, or behavioral signals that account is throwing that says, “Hey, right now is the time to engage with sales.” That is the bridge to monetization, that product team should own as a… even on the core team in order to drive a healthy, predictable, and sustainable pipeline to sales.
Industry Benchmarks for Key Metrics
Lenny: Okay, so this is a really important topic. There’s this concept you just described, product qualified account. It might be a good time to define a couple other acronyms and kind of compare them. THere’s PQA, there’s PQL, product-qualified lead. There’s marketing-qualified lead. Can you just maybe describe the suite of acronyms? Then, I want to follow up on the PQA because that seems really important.
Elena Verna: I’ll start with PQA just because we just breezed over it. PQA is product-qualified account. It’s on account level, it’s aggregation of multiple users that are using the account. It might be on the overall logo level, so let’s say you’ve attracted a company, so you qualify PQA across the entire company usage, or it might be on a specific team or workspace level depending on what is the better predictor for you and who the sales team is going to be engaging with. Product qualification is very much product metrics. It’s the volume of use, it’s the velocity change. For example, yesterday I’ve been adding one user per day and then today I’ve added 15 users to account. That’s a velocity change that you need to pay attention to. Or there is a feature usage that can be highly correlative to enterprise interest. That product should be driving towards every single account reaching in order to qualify them for sales conversation.
Now, within the PQA, there may or may not be PQL, so PQL is a product-qualified lead. Lead assumes there is a person in the account that I can go and sell to. Now, leads are those buyers. They’re those decision-makers in the account, and if you have a smaller segment, so for example you had more in small businesses or lower end of mid-market segment, you may very have PQLs in there because user is maybe equals buyer. User can make those buyer decisions. However, the more you move up the market, the more end user is many steps separated from the buyer, so you might have very healthy usage and you might have a PQA that is off the charts, but you don’t have a PQL in it.
If you just stick your sales against that account, you’re going to have a very terrible situation and very terrible user journey where users are like, “Why is sales talking to me? I have no decision-making power in my organization. I love the product, but please leave me alone.” This is where you get a bunch of cold outbound, and I put big quotations on outbound emails that are just not getting returned. You need to very clearly understand who’s your buying persona and, are they in your user base? If they are, you have a PQL. Pass them, go for it, but if they’re not, go find it out there. This is where MQL concept really comes into play because then marketing has to still qualify a lead to bring it and connect it to PQA. PQA can have a PQL as a user already in the user base, or you might need an MQL with marketing or sales, bringing their lead over and connecting them with the usage.
Specific Advice on User Personas
Lenny: Amazing, so we’re going to share a link. You have this awesome visual that shows kind of like the funnel of PQAs and PQLs funneling into sales along with marketing qualified leads. Basically there’s a kind of instead of one path to sales, knowing who to talk to, now there’s two. Product is funneling you people that are qualified, and then marketing following you people that are qualified.
Elena Verna: There is a third path. There might be a marketing funneling people that have no usage whatsoever and that is a true top-down lead, so you have three buckets of lead attribution that is coming in. I have usage and one of the users is my lead. I have usage. I have no lead in the account. Marketing is bringing me the lead, but I have to leverage that usage against that lead or have a lead coming through, there is no usage. I have to sell the entire thing still to them, so there’s no context that I can use of existing usage. Those three channels are super important to identify. They all have very different conversion rates. They all have different playbooks of how you close them and, honestly, they require often different sales team to go after them because it’s a very different sales enablement.
What Comes After Product-Led Sales
Lenny: You remind me of… You have so many hilarious memes that you share on LinkedIn. By the way, everyone listening should go follow Elena on LinkedIn and subscribe to our newsletter because it’s hilarious and also informative. It’s a magical combination. One of my favorite memes of yours is The Shining one that we just kind of touched on where someone’s-
Elena Verna: Oh.
Lenny: … just using a product for five minutes and then, “Hey, do you want to,” a sales guy just reaches out with the ax, “Hey, do you want to chat?”
Elena Verna: That actually… It’s painfully true. That’s one of my most highly engaged memes that I’ve put out there. I have also one of the urinals where the man-
Lenny: Oh, with the [inaudible 00:33:29].
Elena Verna: … using the urinal and then like one comes over. A salesperson comes over. “Would you like to chat about our-
Lenny: Right-
Elena Verna: … “enterprise plan?”
Lenny: … it’s like 10 urinals and he’s right next to yours.
Elena Verna: Yeah, exactly, so the piece here that a lot of companies miss, unfortunately, is that they jam product-led sales into a traditional top-down sales playbook. Now, what does that mean? In traditional top-down sales book, an MQL that you have or a lead that you gather already is in consideration cycles for your enterprise-level offering. However, in product-led sales, a new user that signs up, they know we’re close to enterprise-level consideration. They’re just trying to complete an individual job to be done. They’re not solving a problem for their company. If you can imagine, it is like a very large funnel. You start with just users looking for problem solve. Then, you transition to awareness, consideration, and intent channels for team level problem. Then, you escalate for awareness, consideration, and intent channels for enterprise-level problem.
Top-down sales process goes after the bottom of that funnel where there’s already an intent to solve company-level problem versus at the very top is where product-led growth starts on individual-level problem. It’s a different timeline. If you go after individual user that just signs up for the account and you reach out to them 10 minutes later after sign-up asking, “What’s your budget and are you ready to buy?”, it’s a complete mismatch of where they are in their consideration journey. You cannot consider a new product sign-up an MQL in the traditional sense. They’re just not there yet. They have a fraction of the enterprise problem that they’re solving and they’re not ready to buy.
Lenny: That’s especially annoying because there’s so many SaaS products now and everyone is coming for you, especially if you’re at an awesome company that they’re trying to sell, so got to be [inaudible 00:35:34]-
Elena Verna: Yeah, I mean-
Lenny: … [inaudible 00:35:34].
Elena Verna: … anytime I even started… I remember I started at Amplitude when I started a year ago, it’s like my inbox was just filled with like, “Now you’re doing this, now you’re doing this. Buy, buy, buy.” I mean, I don’t know, I can’t even notice anything in that outbound [inaudible 00:35:52] unless somebody reaches out to me with something authentic that is already usage- based, it’s ignore.
Lenny: It’s going to get worse with GPT-oriented cold outbound emails. Oh my God.
Elena Verna: Absolutely.
Lenny:
Or if you’re working with sales, you can natively plug Stripe, Salesforce, or HubSpot directly into Rows. When you’re done, you can share your work as a beautiful spreadsheet that’s easy to read and embed charts, tables, and calculators into Notion, Confluence, or anywhere on the web. I’ve already moved some of my favorite spreadsheet templates to Rows. Go to rows.com/lenny to check them out. That’s rows.com/lenny.
Okay, so let’s shift to actually, how do you actually do this? How do you actually build a system of product-led sales? I feel like there’s maybe three buckets. There’s, what data do you need? What infrastructure systems do you need in place? Then, what are the people you need in place and how do you resource it? Maybe let’s start with the data. What sort of data do you need in order to do this well?
Elena Verna: There’s different levels of scale on how you should be attacking this problem. First of all, it starts with just top-down intuition. What are the signals that you’re seeing around the accounts that are highly correlative to sales being very excited-
Lenny: Hmm.
Elena Verna: … about this hand-raiser or about the sales form submit out of the usage? You just start with that. It’s as simple as, how many of others are exhibiting those signals? When you have very low lead volume still, you don’t want to get too complicated with it at the beginning. You want to be very transparent. You want to just understand what sales are seeing, what they get excited about, and feed them as many accounts that fit that model. The one thing is not to do is just to start sending every single user to sales because that’s the fastest way for sales to say, “This product channel is garbage and I don’t ever want to see a lead from it again.” They have such close rates and their quota, their salary depends on their ability to close that they just start disregarding this as a meaningful channel.
Now, the second escalation to it is, okay, now you will know intuition, but now let’s actually look at the reality of who is hand-raising in the product. You look at the signal of who looks like a hand-raiser, smells like a hand-raiser, acts like a hand-raiser, but is not hand-raising. That’s a maybe very simple regression model. It might be just a simple histogram analysis that you do of what differentiates people that are hand-raising from people that are not hand-raising and who else fits into criteria and looks like a hand-raiser based on those differences.
That should be your first PQA model. It should be very simple. It should just be if you can run a linear regression against some of the top coefficient that you notice so you know which has the biggest weight to predictability and you go with that. The main piece here is to involve sales very early on so you’re partnering with them. You are not just dumping it on them and that you have a very strong feedback cycles from sales or whether what you’ve identified is correct or not correct because PQA definitions should not be static. They’re constantly evolving. Just because it’s right right now, that doesn’t mean it’s going to be right next quarter, so you have to have a lot of rituals with sales team to gather that feedback.
Lenny: One thing I’ll mention is Amplitude and Mixpanel both have a regression tool that help you identify correlations and causal kind of connections between metrics, so maybe shout-out there. I think it’s called Compass-
Elena Verna: Yep.
Lenny: … and then Mixpanel’s I think is called Signal.
Elena Verna: Yep. Honestly, to be fair, most of the time I’ve done it manually at first because it requires so much understanding of the data, and if the data is correct and if I’m even seeing because you don’t want to throw in too many co-related variables into the model because then you have issues of those variables like describing themselves, so to speak. Even if they’re firing, there might not be actual predictive. It’s partnership with analytics team and it’s partnership with the intuition from the sales team. Then, you can start throwing it into a regression model and start to automate and think about scaling it, which there is a lot of PLS platforms that are coming up and finding their product-market fit at the moment that can do that for you.
I don’t know if I would start there right from the beginning unless you actually understand the data because buying a platform will not bridge the gap for you understanding what actually matters in your data. Buying a platform or using a third-party solution will help you scale your efforts once you hit the first first, let’s say, data sales fit that you can then scale and disincrease distribution of.
Lenny: Data sales fit. Wow, that’s a new term. There we go. I have not heard that before. Data sales fit. I love it, so you’re saying basically start manually to make sure you fully understand what’s going on?
Elena Verna: That’s my take. Yeah. I-
Lenny: [inaudible 00:41:42].
Elena Verna: … just… I don’t… I have a hard time scaling something that I don’t fully understand because data can tell you lies and you can just fit any story that you want into data. I need to really understand it and how it fits and what you are observing and that it makes sense before you go and start using automation on it.
Lenny: Cool. Okay, and then just one last question on what you were just talking about, which is finding correlations and causal relationships between usage and users and understanding who to send to sales. What are some common metrics and attributes that you’ve found that are indicative of they should go to sales?
Elena Verna: One of the most important things is to create network effects within the company, within a team, which each additional team member added to an account benefits from everybody else. This does not mean you have to have platform network effects. You’re not trying to be LinkedIn. You’re not trying to be Instagram. Those are platform network effects. What you are trying to create is the value of each additional user into account. What that means, I’m going to go through slight deviation here is that there should not be only pulling mechanism where I pull you into my account. There also should be pushing mechanism. Any new sign-up that happens from the company that already has an account in my system should be presented with an option to join that account, not just create a brand new account.
What you don’t want to create is hundreds of rogue individual accounts that don’t know about each other. We as humans, we are creatures of community, we’re creatures of we like to be surrounded by people, to be validated by people, and at least you want to create that herd mentality inside of the company and push and pull people into the account. One of the biggest PQAs is number of users in the company using your product. By the way, the magic number is usually seven. The more time you have seven or more users in the company and there’s like some weird parallel here to seven friends at Facebook and seven collections at LinkedIn, but seven I’ve seen very often as a check mark. “Hey, there’s enough value here distributed across multiple people inside the company that there might be an enterprise conversation to be had.”
The second-most important is usually some sort of volume threshold. For example, for Amplitude, it’s number of events that you’re sending through, which means that you are really starting to tackle your entire application with analytics as opposed to just a small portion. Or with Miro, it was number of boards that you have in the account. With Figma, I think it’s number of revisions that you have on any given design. The last one I would say is velocity. Velocity is the trickiest one just because we don’t have a very easy way to measure velocity in our transactional data, but it’s actually one of the most powerful one that triggers the right timing for the involvement because the change in velocity either number of users being added or events being sent or storage that is being utilized is usually a fantastic predictor.
Lenny: Amazing. Okay, so kind of like the simplest model to tell you there’s a peak-y way is number of users usage and velocity.
Elena Verna: Yep-
Lenny: Amazing.
Elena Verna: … and users, by the way, can be either usage of velocity metric, too. It’s just like if you’re going to do anything, just look at whichever accounts have most users. It’s like an 80-20 rule. For 20% of the efforts, you’re probably going to get 80% of the value.
Lenny: Love it. Okay, so I took us off track and you were talking about what data you may need in place. Is there anything else along those lines?
Elena Verna: I would say that it’s very important to identify behavioral signals as well, and I’ll give an example. At Miro, we had a very strong behavioral signal that if there is an admin switch in the account, some sort of evaluation is happening. Admin transfer, new admin being assigned, that should be ding, ding, ding, all of the bells are ringing that you should maybe reach out to that person and see what’s going on. The other one that is fascinating is your terms of use pages, your privacy and policy. Nobody cares about it unless they’re considering enterprise deal. If you see anybody from account land on your terms of use pages, reach out to that person. More likely than not, you have a buyer on the hook and you can assist them in increasing their perceived value.
Lenny: Wow, that is so interesting. That’s the kind of stuff you only learn having done it.
Elena Verna: Many, many times, yes, but those-
Lenny: Oh.
Elena Verna: … signals are, by the way, universal. We looked at it at MongoDB, it was very much true, so these things of when you… What in product constitutes evaluation process? What are the enterprise buyers are looking for? I wouldn’t say, by the way, watching a webinar or landing on an enterprise landing page is a good behavioral signal because it might be annoying that I just like on accident landed on a landing page and now I’m being spammed by outbound SDR sequence. More meaningful actions that are deeper with an engagement user journey are incredible predictors.
Lenny: You talked again about this idea of spamming from sales and it made me think about like… I don’t even know if I want to ask this, but have you seen downside to sales just continuing to hammer you as a potential user? Does that actually hurt? I don’t want to know almost because I feel like the answer is no, but what do you think?
Elena Verna: I think you have to look at the channel effectiveness. You have only so many channels to communicate with a customer. Email is obvious. You can communicate with them in app. You can have some sort of chatbot. Maybe you can deploy some sort of paid marketing, maybe social or retargeting display ads, but those are very expensive to utilize. Stepping back and thinking when it’s the right time to reach out. How can I grab their attention? If you highly saturated the channel that is your primary for reaching out to the user, they’re not going to react even if it’s more of a right time for them to react.
Will it hurt you? I don’t think you’ll notice it right away, but over time I think people become blind to channel communication if it’s not applicable to them because, “Fool me once, shame on you.” Like, “Fine, you tricked me to opening this email.” Fool me twice, it’s shame on me and I’ll be a lot more frugal of which emails I open or which notifications I react to. I think that you have to put user journey first and you have to really think about the timing that it’s right for user and PQA.
All it is is the right time to engage with the customer and then go hit them hard over all of the channels of communication, but then, also know that accounts go in and out out of PQA. Today I might be in the PQA, next week I might not be, so you need to sunset the efforts if you didn’t get in touch with the customer and wait for the next PQA moment. It will happen if your product is holding that goal and is accountable for getting more and more accounts to reach a threshold PQA.
Lenny: Wow, that’s really interesting. I’m also happy to hear that answer. Great. Okay, so let’s continue down this track of what it takes to implement a product-led sales motion. Just talked about the data component. What about just systems and infrastructure and tooling? What do you recommend there as a start?
Elena Verna: I approach the subject always as an evolution, not a revolution, so start with your existing systems as much as possible. I would say the biggest mistakes to avoid if your sales team is very heavily embedded into Salesforce, don’t try to have them switch to a different solution. It’s just not going to work. You need to try to figure out how to embed what you need the data into Salesforce, not get them to use some other third-party tool. Then, I wouldn’t jump into any big commitments until I really prove out viability of product-led sales motion before automating any of it. I’m more of kind of Wizard of Oz it as fast as much as possible to get the initial traction so then we can validate that there is investment to be had in scaling it and there’s a business value in it.
Lenny: The tools you’re using at that point, is it like Google Sheets? Or is there something else involved in [inaudible 00:50:17]-
Elena Verna: It’s-
Lenny: … [inaudible 00:50:18]?
Elena Verna: … Google Sheets, it’s your Looker, Tableau dashboards, it’s your Amplitude charts and reports. It can be widgets within Salesforce or ETLs that you pipe through HubSpot and Marketos into Salesforce, or it can be CRM solutions for PLG specifically that you literally deliver in Excel sheets to sales team to prototype a different outreach.
Lenny: Have you shared any of this kind of like MVP product-led sales stack that you recommend? If not, I think you should because that seems pretty useful.
Elena Verna: Yeah, I think I definitely should.
Lenny: All right, there we go.
Elena Verna: I have my idea for a next blog post. Done.
Lenny: There we go. Okay. If we got anything out of this chat, we’ve got that. Okay, in terms of people, so we talked about data, we talked about tooling, infrastructure, what do you suggest in terms of people and resources to invest in this area as a start, and then also as you evolve?
Elena Verna: For PLS, the people that you need is product managers that will be able to get account to PQA stage. You will need salespeople that will understand which usage triggered PQA and how to apply that information to find a buyer and to enable a buyer to convert them to an opportunity. You need marketing to educate both the end user or enterprise buyer on why the value of this enterprise solution is going to make sense to you, and you need analytics team. You need a data analyst that will continuously dig in the data to find correlative signals that you can test causation in. Those are the four people that you need, product, analytics, marketing, sale. I should say engineering, too, obviously, but I’m kind of bundling them together with product,
Now, it’s an evolution, not a revolution, so if you’re starting from sales-led growth, I would highly suggest of you going to a sales team and asking for somebody to run a pilot with you. Don’t just throw these leads into the top-down sales process and assume that everything is going to be just fine. Attach to yourself a pilot AE, so account executive, or an SDR and see how that works. You kind of separate yourself from the mothership of the sales engine and you actually prototype this separately in a little bit of a vacuum, not under pressure of them top-down quota relief. If you in a product-led growth company, then I would suggest do your own sales. It’s kind of like a founder-led growth, so think about it like, “Hey, you need to close maybe first couple of deals you sell first so you truly understand what’s happening,” and would not get first hand-raisers and say, “Oh, we can’t close it unless we have a salesperson.”
No, just have somebody support to do it. Have somebody on finance do it. You do it. I’ve been on chat myself plenty of times trying to close the deals just to understand what’s the sales process for the customers looks like. Then, you can figure out who to actually hire and who to actually scale, but for PLS that starts in PLG, you actually just start with more of blend of an SZR and AE together because you don’t need two separations. The same person can both outbound to a customer and close them at the same time, and then you can go into specialization of the role. Start small, start nimble, prove it out, scale along the way, but have marketing and analytics support you the entire journey.
Lenny: That is really simple. What I’m hearing is you don’t need to hire someone new necessarily. You have the resources most likely, and then it’s just, how do you allot some time of this team to start investing and violating?
Elena Verna: Yeah, I’d say that my philosophy is that I want to have an ROI for a new hire before putting a job rec out there, and to create an ROI, I need to prove it out of what potential can there be myself first. I can almost like fund this hire with the revenue that we can generate out of this channel originally. Obviously that includes a lot of individual contributor work that you have to do in the area potentially that is not comfortable, but that’s the fastest way to grow in your career, so I think that’s a necessary step for a successful execution.
Lenny: You want to hear a crazy stat about product-led growth and not hiring sales?
Elena Verna: Sure.
Lenny: Okay, great. I was chatting with the founder of Notion for the series I’m working on and Notion didn’t hire their first salesperson until they were past 10 million ARR.
Elena Verna: I believe it. Miro did not hire their first salesperson until they were like 5 or 7 million in ARR. They were literally closing the contracts through support team and it was just fine.
Lenny: Same with Notion, it was their customer success and support team.
Elena Verna: Yep.
Lenny: That is some product-led growth right there.
Elena Verna: Yeah.
Lenny: I love it. Amazing. Okay, so we’ve talked about data, tooling, people. Is there anything else that you find is really important to being successful with rolling out a product-led sales bridge motion?
Elena Verna: The most important thing in product-led sales is that there is a different configuration internally of collaboration that needs to occur. In traditional sales world, marketing creates pipeline for sales. Sales sells product. Product engages with a paid user to drive retention. In the product-led sales, product acquires and activates a customer and product creates pipeline for sales. Relationship is not that there’s a go-to-market org with marketing and sales, and product just kind of throws features across the fence for them to sell.
The collaboration here is between product and sales, but that means the product has to take on accountability over pipeline. The worst thing that you can do is to say, “I’m going to do product-led growth,” or, “I’m going to do product-led sales and I’m going to do it in marketing.” Recipe for disaster. You’ll be failure mode within six months because product has to take accountability over selling of the product itself. That is not to be taken lightly because so many product teams are deeply, deeply uncomfortable with owning monetization targets. Now, I’m not saying that product should just be gold and revenue because that’s a very short-term short outcome past performance. There has to be a very clear designation onto long-term goals and long-term objectives and revenue ownership.
By revenue ownership, I don’t mean that individual product manager also should have a revenue target on their back. What I mean is that the product leadership should be accountable for the revenue target, but the product people should be responsible for more of KPIs, free to paid conversion rate, package mix, PQA, maybe even PQLs, but those are all of the KPIs into revenue. The piece to me that is of utmost importance is to keep product accountable. You cannot start this product-led stales motion in marketing and sales and think that it can continue with the same configuration inside the company and still succeed. Product has to have a seat at the table and product has to feel accountable and responsible for it.
Lenny: When you say accountable, what does that actually look like? Is it like their OKRs have certain goals around, “Here’s how many PQAs you’re driving?” Is it a number? What does accountable mean in this-
Elena Verna: I think so. Every product has some sort of goals and they definitely should have goals on keeping healthy, engaged user base. They should definitely have goals in terms of maybe feature utilization or customer satisfaction, but what I’m saying is to have also some sort of monetization goals. What that is for each company, I think, differs depending on their level of comfort and how close they are to revenue capture mechanism. Let’s say at Miro, our head of growth product had a self-serve revenue target on her back. She drove it. She had revenue goal that she had to hit in product and she shared marketing because I ran marketing in that company. We shared a pipeline goal creation because pipeline cannot be created without marketing, too.
Marketing will need to educate. Marketing will need to find the buyer. Marketing will need to do accounts-based marketing in order to attract the buyer and connect it with the usage. Product and marketing now pull together to create the pipeline and give it to sales, but product can no longer sit on this island as a feature factory. It only works with the top-down sales organizations, which, as I said, I think are going to be heavily disrupted over the next 10 years with value-first product-led growth.
Lenny: This is another hilarious meme that you shared on your LinkedIn, so another reminder, go check out Elena’s LinkedIn with this hilarious meme of product teams being presented, “Hey, you’re going to own some revenue targets.” They’re like, “Oh no.” Yeah, exactly.
Elena Verna: It’s actually super interesting because a lot of growth leaders shy away from revenue targets. Acquisition target, sure. Retention target, engagement target, sure, but monetary target, “Oh no. How can I possibly own a revenue target?” I think we all in tech, and I specifically point a finger at my industry in B2B industry, just got a little bit complacent with revenue ownership from product side. I do think it’s catastrophic for us in the long term if we don’t fix it.
Lenny: I love it. I want to do a whole podcast on your meme strategy and your parodies that you put out, but we’ll stay on track here. In terms of the revenue target, what is that goal like? Is it just in this quarter X million dollars of revenue? Is it a growth rate from quarter over quarter? How do you find people actually define that revenue target?
Elena Verna: Right, so there’s different targets that you would have for self-serve revenue versus product-led sales revenue. For self-serve revenue, your KPIs should absolutely be free to paid conversion rates or trial to paid conversion rate. It’s the package mix, it’s the average revenue per user or ARPU. It may be retention rates, first-term retention rate, second-term retention rate in order for you to sustain the healthy revenue. That’s what outputs self-serve revenue. Those should be the pieces. Do I have a problem in friction and acquiring new paid user in maximizing their value or in retaining that paid user? Those are the three inputs that go into self-serve ARR targets, and you should just understand where the biggest opportunity for your team to focus on driving it.
In any of those cases, most of the time free to pay conversion is the biggest focus of any given team just because we want to better convert and inflow into our user base, assuming we have good product-market fit so we have a solid retention happening. In free to pay conversion, there’s three pillars that you constantly need to work on, and one pillar dominates them all. It’s monetization awareness. Simple as that. If you have a freemium product, I guarantee you 75% of your customers in freemium product are not aware of what you’re selling. Only focusing on monetization awareness can give you incredible output on driving monetization, and it’s really it’s product’s ability to communicate via feature walls, via usage walls, via trials, or what the value of the paid offering is.
I’ve heard stories from Slack of just showing message limits and how big of an improvement on conversion rate it had. I’ve had it firsthand at SurveyMonkey where just adding consistent EUI across all of the paid triggers that were that Amazon gold color and making sure that each user has been able to see at least three of them. There’s a rule of three that goes into advertising that we need to see things three times in order to remember them that drove monetization awareness and conversion rate up, but that’s basically consumers 80% of your work. The second one is just conversion rate optimization, so your pricing page optimization, your checkout page optimization, your currencies that you offer, the payment methods that you offer to make sure that there’s as little friction as possible in order to actually pay.
Then, the last one is what you’re selling, do people want to buy? This is where you actually go after monetization model change. Which features are in each plan? What are the price points in each plan? How did the upgrade path look like? Do you have add-on strategy? DO you have just pay-to-pay fee monetization plan strategy? That one is like the last one that you should cross because it involves a lot of cross-functional effort and decision-making, but free to paid conversion, upsell potential, and retention. That’s for self-serve AR. For product-led sales, what product should own is PQA, but who defines PQA? That’s the big question.
Who iterates on PQA? Then, how do you actually get people to get to the PQA stage? Just like product often will own engagement metric or maybe even activation target, your own PQA target, so that just becomes one of the goals. Depending on where the biggest effort that needs to be, it can be an activation, it can be engagement in PPPQA, but more and more I see product-led, especially mature companies needing to focus their product teams on PQQ, yet they don’t have a clear definition because sales kind of goes rogue and does their own thing. Product fails to deliver predictable pipeline to sales, which pushes sales into a top-down motion prematurely.
Lenny: A PQA target would be like 1,000 PQAs at this quarter. Is that the way you-
Elena Verna: Yeah, yeah, so you usually actually look at it almost from conversion rate. You look at, “Okay, how many teams do I have in my ICP, so ideal customer profile segment, that are active?” That’s my denominator, and how many of those teams are reaching PQA target-
Lenny: Mm-hmm.
Elena Verna: … this month? It’s like a conversion rate to PQA out of engaged ICP teams.
Lenny: One thing that I love that you’ve touched on is this awareness of monetization.
Elena Verna: Yeah.
Lenny: People knowing that you have more features and that you may get access to more if you pay. How do you track that? Is it just like people seeing it per account or per user, like what percentage of seeing one of these upsells or seeing them three times?
Elena Verna: I track it fairly simple two ways, one, qualitatively. I just run surveys against people and say, “Do you know what we’re selling?” It’s shocking how many just have no idea what’s in our paid plans. Like we have major issue here, or I just track pricing page views per activated account. How many of the activated accounts landed on the pricing page at least once? That’s at least a level of exposure that they hit some sort of trigger that pulled them to explore a pricing page. One of the things that just want to give a hint to anybody who’s listening from a sales top-down companies, one issue you might have is that when your products is developing functionality, especially paid functionality, they just design review it and ship it for paid plans only.
If I’m in the free plan or in the lower tier plan, I don’t even see it. I don’t even know of it existence because it doesn’t exist in the app because it was never designed for me to even see it. Just doing one small change of pushing your design reviews to review functionality from every single state of the customer, free state, lower paid state, and target state that this functionality is actually unlocked can do all of the difference in the world. Then, you’ll actually understand how that [inaudible 01:06:06] functionality is being exposed to a free user, so them to become aware in self-serve manner of its existence.
Lenny: I love, love, love all these little tactical little insights and tips, so thanks for sharing all these little things that end up being the most useful to people. Just a few more questions and then I’ll let you go. One is around pitfalls. What have you found are the most common pitfalls that startups run into as they’re trying to invest in product-led sales? You touched on a few, but what comes to mind when I ask you that?
Elena Verna: Let’s just go through some summary that we’ve mentioned already throughout our conversation. Don’t treat PLS as a traditional top-down sales process. Every single user does not equal. It’s a opportunity for you to co-chase after. You need to understand the right triggers and usage. They can help you automate qualification process, so it’s almost automating some of the SDR efforts to say, “When is the right time for my sales, for my human that I’m paying a lot of money, to intervene into this account and add value?”
Sales interaction has to add value to user journey, not be disruptive or create additional friction because I’ve seen so many, even people posting of like, “Why am I getting a phone call 10 minutes later” It’s annoying. I’m going to stop using the product because of it.” They feel misunderstood. For that profile. Your customers understand whether you have buyers, whether you have users, and they’re in your ICP segment. Know this information upfront so you can serve a best experience possible.
Number two, hold your product accountable. This cannot be just executed through marketing and sales. Product has to have a seat at the table and product and sales relationship has to be one of the closest ones in this motion. That’s really hard to change, especially in the traditional top-down sales company where marketing and sales have closer relationship. Try to create new rituals. Try to create the new ways of communication between the teams for them to be aligned behind the same goals.
Number three, don’t leave marketing out of the equation. Majority of your usage will not have a buyer in it. You will need marketing, your enterprise marketing, your account-based marketing to go and find and hunt that buyer and to bring them and connect them with usage. Lean on your marketing team. Just because you’re doing product-led growth and product-led sales does not mean you don’t need marketing, and strong product marketer can do wonders here in helping you with messaging, with outreach, and sales enablement materials.
Number three, don’t wait on data efficacy too long. You might be using your intuition at the beginning very well, but start thinking about how you will need to scale your data issues because product-led sales is all about leveraging usage for pipeline creation. You need to be able to measure that usage, understand that usage, track it, and evolve it.
Lenny: Amazing. Two more things. One is you shared before we started chatting that you have some benchmarks around some of these metrics that you’ve mentioned of just what is good so that people can understand what their goals might be. What can you share there?
Elena Verna: Yes, so in terms of benchmarks, first of all, it’s time to get from individual usage, when that user comes in to have a single job to be done, to creating an enterprise-level contract. It does not happen in hours. It does not happen in days. It doesn’t even happen in months of usage. A couple of benchmarks for y’all across Netlify, Miro, or Amplitude, which are all of the companies I worked at. It was 12 months plus of usage that had to happen before sales contracts can be created on sustainable way.
Now, that’s not an all-encompassing rule. You will have very high-intent buyers coming in sometimes and you’ll be able to close them within a week, but on average it takes a year of usage to escalate the problem from individual to a company-level solution. It takes time, be patient. This is not the problem of get more sign-ups this quarter and close more pipeline in the same quarter. This says you building for long-term growth and you closing contracts and the sign-ups that happened really last year in the best case scenario.
Number two is don’t confuse user and buyer. Please, please, please profile your users upon sign-up. Do not skip those onboarding questions. No, they do not detract for your onboarding completion rates and people that do drop off in the profiling stage, they were low intent anyways. They were never going to be activating if one extra question deterred them from completing, from continuing with your product. Profile your people, know who you’re talking to. It’s more important than a couple percentage drop-off that will never going to activate in the first place. No, no, no die user please because all of us-
Lenny: I like that.
Elena Verna: … are tired of receiving outbound that is not relevant to us. Then, the third one is conversion. Conversion rates here actually stand from the true PLG companies, so freemium conversion rate is usually around 5%, trial conversions are more closer to 10 to 15%, but your contract value start to go up.
It’s not so much that you increasing conversion rates because a lot of those companies will still go through self-serve monetization flow before they become your sales pipeline prospects. Conversion rates stay the same, but your contract values and your lifetime value of the customer is what starts to increasingly go up and that you can influx into creating a smile revenue curve.
Lenny: Incredible. The question you had about profiling your user, I was going to ask what questions to ask. I’m guessing maybe a better approach is just go to Miro or Amplitude and just go through the sign-in flow and see what they’re asking.
Elena Verna: Yeah, I would give some couple parameters in place. Number one, limited to maybe three to four screens because otherwise it starts to feel too long. Make sure they only ask information that you either going to use in the data segmentation that then you can escalate to personalization and messaging, but at least that you’re going to use on data segmentation and experiment with how deep of an information that you can ask.
You should always be able to ask about company size, about the department, which customers coming from, about their seniority on the team and about their use case. Those four questions are uniform. Everybody’s used to answering them. The rest like phone number or some… maybe if you need to know the address or so on, those experiments, how much you actually want to make them required questions versus optional, but please, please, please experiment on your onboarding questionnaires. All of you.
Lenny: Closing question. Everyone started with sales, sales-led growth. and then product-led growth emerged and now there’s this bridge between the two of sales-led growth. Feels like there’s always this new way of growing a business and approaching go-to-market. Is there something beyond product-led sales? What’s next, if anything?
Elena Verna: Well, I wonder how much a rise in AI is going to automate some of those sales conversations. It’s not going to be truly product-led growth because-
Lenny: No shit.
Elena Verna: … it’s not like just the product’s it’s going to sell itself. What if on the other side of that chat or other side of that email or even a Zoom call because they can do a deep fake of anybody, it’s going to be AI selling to you and giving you very deep and personalized answers? I am curious to see how that’s going to evolve because the plethora of information that AI can surface to you in a very personalized manner in a matter of seconds is far stronger than any human or even content management system can do at the moment.
Lenny: Do you want to coin an acronym right now for what that might be?
Elena Verna: Have to be AI sales.
Lenny: A-I-S-L-
Elena Verna: There I go.
Lenny: … G. Wow, it’s a mouthful. Elena, this was everything I was hoping it would be. I imagine this episode will be even more popular than your first one. Thank you so much for making time and getting into such detail in all the things we talked about. Two final questions. Where can folks find online if they want to reach out, learn more? How can listeners be useful to you?
Elena Verna: I’m on LinkedIn a lot, but I have started my own Substack, so please subscribe to my newsletter if you can.
Lenny: Definitely do.
Elena Verna: I put more short content on LinkedIn and longer form explanations in my Substack, not to compete with your Lenny Newsletter-
Lenny: No, there’s-
Elena Verna: … but these are-
Lenny: … there’s plenty of room for everyone. I recommend yours within Substack and we’re going to link to it, and definitely there’s like no reason not to subscribe if you’re listening to this podcast. It’s only upside.
Elena Verna: Well, thank you. We’re also creating PLG course with Reforge that is going to go into very nitty-gritty details of everything that I’m talking about to help you operationalize these concepts. It’s launching in fall-
Lenny: Oh awesome.
Elena Verna: … 2023-
Lenny: Yeah.
Elena Verna: … so do check that out. Other than that, I’m a really big believer in democratizing knowledge so we don’t have to all make the same mistakes over and over again, so the biggest way that you can help me is to share your insight, share your knowledge, and share your learnings so we can all grow so much faster together.
Lenny: Well, you’re one of the best at doing that, and thank you again for doing this.
Elena Verna: Thank you for having me, Lenny.
Lenny: Bye, everyone. Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at lennyspodcast.com. See you in the next episode.
Reformatted by reformat_english_direct.py
产品驱动销售终极指南 | Elena Verna
访谈文字稿
Elena Verna: 产品驱动销售中最重要的一点是,内部需要一种不同的协作配置方式。在传统销售模式下,市场团队为销售团队创建销售管线(pipeline),销售团队卖产品,产品团队与付费用户互动以推动留存。而在产品驱动销售中,产品获取并激活客户,产品为销售团队创建销售管线,所以关系不再是——有一个由市场和销售组成的上市组织(go-to-market org),产品只是把功能丢过墙让他们去卖。这里的协作发生在产品和销售之间,但这意味着产品必须对销售管线承担责任。你能做的最糟糕的事情就是说”我要做产品驱动增长”,或者说”我要做产品驱动销售,而且我要在市场团队里做”。这是灾难的配方,六个月内就会失败,因为产品必须对产品本身的销售承担责任。
Lenny: 欢迎来到 Lenny’s Podcast,在这里我采访世界级的产品领导者和增长专家,向他们学习在打造和增长当今最成功产品过程中积累的宝贵经验。今天的嘉宾是 Elena Verna。如果这个名字听起来耳熟——Elena 是一位返场嘉宾,你可以自行评判,但我认为这一期甚至比第一期更好,而这个门槛很高,因为第一期至今仍是本播客最受欢迎的节目之一。Elena 曾在 Miro、Amplitude、SurveyMonkey、MongoDB、Netlify 等十余家公司工作或担任顾问。她也是 Reforge 的长期讲师和驻场创业者(EIR),帮助创建了他们的实验化、商业化、增长、领导力课程,以及即将推出的 PLG 课程。
在这次对话中,我们深入探讨了产品驱动销售这一新兴领域。Elena 解释了产品驱动销售到底是什么,它如何与产品驱动增长(PLG)和销售驱动增长相配合,谁以及什么时候应该考虑投入产品驱动销售,产品驱动销售如何改变你的销售和营销方式,你需要什么样的数据、工具和人才才能做好,以及你需要避免哪些常见陷阱。我之前说过现在再说一遍——Elena 可能是世界上最聪明、最有经验的增长专家,尤其是在 B2B 领域,我永远不会厌倦向她学习。短暂赞助商信息之后,请享受这期与 Elena Verna 的对话。
欢迎回来
Lenny: Elena,欢迎回到播客。
Elena Verna: 谢谢你邀请我回来。我以为我会是第一位返场嘉宾,结果被 Casey 抢先了,有点不高兴,你得解释一下这件事。
Lenny: 好吧,解释是这样的。你是我们第一个安排返场的,但后来这期稍微被推迟了一点,Casey 恰好有一个更早的档期,所以从技术上讲你是第一个被安排返场的嘉宾。
Elena Verna: 好吧好吧,我接受这个说法。
Lenny: 好,我解脱了。我想说我真的很激动能邀请你回来。我们大概一年前录的那期节目至今仍然是有史以来最受欢迎的节目之一,我仍然看到有人在推特上讨论和分享它,所以我非常高兴能有你回来做第二期。
Elena Verna: 我也很高兴回来,我们开始吧。
近况更新
Lenny: 在进入正题之前,上次我们见面时你是 Amplitude 的临时增长负责人。你现在在做什么?过去这一年发生了什么?
Elena Verna: 我在二月份刚结束了在 Amplitude 的临时职位,所以至今不过几个月。我正在观望是否要接受下一个临时职位,但在临时角色之间我总会休息六到八个月,因为临时工作强度非常大——你在公司工作的第一年里堆积了大量需要交付的成果。所以我现在在做顾问,为 Veed.io、Sanity、Clockwise 等出色的公司提供顾问服务,同时也在构建下一阶段的框架体系,可能会在一个新的临时职位中去验证它们。
Lenny: 哦,如果有人在听这期节目然后想”我怎么才能和 Elena 合作呢?“——他们应该联系你吗?你已经排满了吗?你有什么建议?
Elena Verna: 我永远不会拒绝一次好的对话机会——了解业务、看看我能怎么帮上忙。但我没有在主动寻找客户,不过这不意味着我没有空闲来安排未来的合作。
Lenny: 好的,所以如果机会足够好的话,你是开放的?
Elena Verna: 当然,一直如此。
Lenny: 好,我们开始吧。
Elena Verna: 我必须随时对新的机会保持开放,是的。
什么是产品驱动销售
Lenny: 我太喜欢这种说法了。我也有同感,FOMO(错失恐惧)总是会冒出来。言归正传,正如你所知,我们这一整期播客将只聚焦一个主题——产品驱动销售(product-led sales)。这种上市方式大概在过去一年左右开始兴起,也许更早一些。我感觉围绕它的兴趣与日俱增,同时困惑也越来越多——它到底是什么、该怎么落地、适合什么样的公司。接下来的一个小时,我们将深入探讨产品驱动销售。
Elena Verna: 开干吧。
Lenny: 走起。好,我们先从一个宏观的问题开始:你怎么定义产品驱动销售?产品驱动销售到底是什么,尤其是跟产品驱动增长相比,它有什么不同?
Elena Verna: 好问题。我们先从产品驱动增长说起。在上一期节目里我们简单聊过,但让我们再回顾一下。产品驱动增长的核心,是产品能够自助激活用户、自助促活用户,并将这种使用转化为变现机会。你把人带进来,让他们到达”顿悟时刻”(aha moment),进入习惯循环,然后你就能从中提取价值。价值的提取可以是直接的——直接从用户身上获取收入;也可以是间接的——他们通过病毒式传播或用户生成内容参与到你的增长模型中,带来更多业务。
说到直接获取价值这一块,有自助变现的方式——我自己使用产品自助服务,去定价页面,找到最适合我的套餐,解锁我想要的功能或用量,然后购买。然而,这并不是变现的唯一方式,你也可以通过销售来变现。为什么?自助变现有一个大约 10,000 美元的天花板。这是因为信用卡刷到这个金额就会被银行标记和拒批,而且作为消费者和专业消费者(prosumer),我们也未必愿意在信用卡上刷那么大的金额——毕竟不是所有信用卡的额度都超过一两万、三四万美元。
自助变现很大程度上是一个专业消费者的使用场景,个人独自试图解决自己的问题。而产品驱动销售,则是将你通过自助服务产生的使用量转化为销售机会,并配备销售人员去促成一份更大的合同——可能是一万五、两万甚至十万美元的合同——从而为企业级的解决方案服务,而这个企业本身已经在以自助方式使用你的产品了。
Lenny: 讲得太好了。你会不会说产品驱动增长在某种意义上一直都是产品驱动销售,因为销售一直参与其中,这只是一种新的描述方式?还是说这确实是一个新趋势、一种新的产品驱动增长的实践方式?
Elena Verna: 产品驱动增长其实一开始更多是围绕个人使用场景——个人遇到了问题,有一个待完成的任务(job to be done),进入产品去解决它。对于很多 B2B 公司来说,这就是产品驱动增长的缩影。然而,如果你要接入销售人员,公司里不会有人愿意为一个个人解决自己的问题而支付一万、一万五、两万美元。产品驱动销售的前提是:从你获取终端用户的个人使用场景,升级为企业级解决方案来解决企业级的问题。让我具体拆解一下,以 Amplitude 为例。
Amplitude,从个人层面来说,个人用 Amplitude 想要什么?我需要触手可及的数据来为我的产品做出更好的决策,所以我把 Amplitude 的 SDK 嵌入我的产品里,它给我提供行为数据,帮我把核心功能做得更好。那公司层面的解决方案是什么?是数据更高程度的自助化,是数据的民主化,是更深层的洞察,是更数据驱动的文化。这才是公司要解决的问题。个人解决的不是数据驱动文化的问题,个人只是为自己解决数据洞察的问题。公司要解决的是数据驱动文化的问题。
在产品驱动增长模式下,一个个体用户对自己的任务需求感到满意就可以了。然而,产品驱动销售的假设是:存在一条通向企业级解决方案的”升级通道”,而这个企业级升级通道值得投入销售资源去跟进,因为产品本身在传达企业级价值主张方面做得很差。产品非常擅长向用户展示”你能做什么”,但在展示”组织实际上能从解决方案中获益什么”方面做得很糟糕。
销售能讲好这个故事。销售能弥合这个鸿沟,然后你可以提升感知价值,从而跨越到一万五、两万、十万美元的合同。我想说,自助变现很大程度上是个人使用场景,而产品驱动销售则是将那个个人使用场景和自助使用转化为一条具有企业级价值的销售管线(pipeline)。
销售在产品驱动销售中的角色
Lenny: 我很喜欢这种思考方式。基本上产品驱动增长有一个天花板,你的消费额只能到——
Elena Verna: 是的。
Lenny: 一定的程度。你能向潜在用户解释的内容也是有限的,然后销售介入,解决了其中很多问题。产品驱动销售本质上就是这样。我想你甚至有一个可视化模型,我现在想起来了——
Elena Verna: 是一座桥。
Lenny: 对,就是连接两者之间的桥梁。那么在产品驱动销售的世界里,销售作为一个职能,对外销售(outbound sales)还会继续存在吗?这是第一个问题。第二,在产品驱动销售的世界里,销售的方式是否发生了根本性的变化?
Elena Verna: 是的,要理解在这种情况下销售应该如何发挥作用,你需要理解终端用户的动机(motivation)、能力(ability)和权限(permission)。简单来说——比如终端用户很有动机,完全有能力解决问题,也拥有组织给予的全部权限——或者甚至不需要权限,而是组织的事后追认——去探索和引入新的解决方案。这种情况下,它可以是沿着升级通道自然向上推进的有机过程。然而,情况并不总是如此。很多时候终端用户缺乏解决企业级问题的权限。利益相关者众多,决策需要委员会来做。问题的影响范围超出了他们的职权,甚至他们可能也缺乏能力。也许他们能完成自己的小任务,但做不了整个企业级的集成。
拿我刚才的 Amplitude 例子来说,没错,我可以在自己负责的产品区域嵌入一个 SDK,但我怎么说服整个产品团队都采用 Amplitude,在整个应用的每一个交互点上都嵌入 SDK?这是完全不同层级的问题。这就是为什么产品驱动销售既可以是一个真正的有机过程——人们主动举手、提交销售表单,已经有需求、有意愿、有认知;也可能是终端用户遇到了摩擦点,产品驱动销售需要去弥合这些摩擦——要么吸引合适的决策者参与进来,从而找到企业买家;要么弄清楚谁是内部拥护者(champion),他们的能力和权限到什么程度;或者促成组建一个决策委员会。
企业级问题的典型案例
Elena Verna: 他们几乎像是在给”人们无法或不愿自行解决问题”贴上创可贴。这种做法可以非常有效,营销也是如此——我们不能忘记营销的作用,它可以教育人们如何弥合那个鸿沟,如何在内部推动购买决策。
Lenny: 你提到了企业级问题这个概念。能不能举一两个例子,说明哪些问题属于企业级问题?另外,有哪些公司在做企业级销售或产品驱动销售方面做得好?这样大家在听的时候能有一个更具体的认知框架。
Elena Verna: 好的,我们来举几个例子。先看 Miro。Miro 是一个在线白板平台。用户来 Miro 解决的个人层面的问题是什么?他们有一个工作坊需要主持,也许他们需要一个白板来做脑力写作,他们用 Miro 来完成个人的待完成的任务(job to be done)。然而,Miro 的设计目标是解决团队层面的问题。我进来,把你拉进来,我们一起协作,现在涉及两三个、四个人了。但即便如此,这仍然停留在项目层面、团队层面。没有人会花十万美金去解决一个团队层面的小问题。那企业级的问题是什么?是提升创新能力,是提升整个团队的生产力——因为我们现在有了这个新的协作渠道。
Miro 能不能通过产品本身清晰地展示使用后全组织生产力的提升?做不到。销售能不能讲好这个故事?可以。Miro 带领用户从个人到团队,然后销售再架起通往企业的桥梁。再举一个例子,Figma。在 Figma 里,我作为设计师进来,我只是需要一种更好的方式来收集利益相关者的反馈,一种更可扩展的收集方式,这样我可以迭代出完美的设计。那团队层面是什么?现在有一个团队可以更开放地与我协作,我可以更快地从更多利益相关者那里收集反馈,更快地完成项目。
那企业层面呢?在企业层面,我们的设计更贴合业务需求,周转时间更快,产品表现更好。这就是企业级的价值主张。而且我认为,在产品开发领域,我们在通过产品本身展示企业价值这件事上,已经变得有些懈怠了。我们依赖销售团队的卓越能力来讲这个故事。顺便说一下,我希望这种情况未来能有所改变,我希望我们给产品施加更多压力,让它一路把用户送上自动扶梯的顶端,这样就不必百分百依赖销售团队去展示那个故事,产品本身就能真正赋能从起点到终点的整个过程。
从有机需求到产品驱动销售
Lenny: 我确实想深入聊聊这个话题。我知道你最近在 LinkedIn 上分享过这方面的内容,我觉得非常有趣。不过在我们进入那个话题之前,让我们再聊聊这个桥梁。有些听众可能来自产品驱动增长的公司,他们可能会觉得,“等等,我们已经在做这个了。我们有产品驱动增长的飞轮,我们有销售团队,他们知道该找谁谈。” 那么产品驱动销售中,这个桥梁到底有什么特别之处?我猜可能是帮助识别该跟进谁,帮助用户一步步深入并自行升级。你怎么看待产品与销售之间的这座桥梁?
Elena Verna: 我们来聊聊产品驱动增长公司是如何开始做产品驱动销售的。通常始于用户群体的有机需求——他们通过支持渠道主动联系,或者直接找到公司里的人说,“嘿,我想为我们整个公司购买这个产品。“这是你从产品驱动增长模式中开始感受到的、涌向企业销售世界的有机需求池。顺便说一句,在你感受到这个需求池之前,你不应该招聘任何销售人员,因为如果没有人要求购买,你不能只是雇一个 SDR 就让购买发生。你需要看到那些主动举手的人,你需要看到那些真正要求企业级采用的人。然后,你开始招聘销售人员来满足这些需求,这很好,你开始做销售,开始真正应对产品内部的有机需求。
然而,如果你依赖内部拥护者(champion)的主动举手,这种有机需求很快就会枯竭。如果你依赖用户群体中已经有企业买家主动要求签字成交,那么你的增长天花板会非常有限,因为大多数使用行为转化出来的实际情况是——通过产品中的使用信号,产品完成了资格认证,表明可能存在一场有意义的销售对话,但买家缺席了。产品驱动销售 90% 的工作是将使用行为转化为机会——在外部找到买家,在外部找到决策者。这就是营销和销售在这个过程中如此关键的原因:将决策者与使用行为连接起来,然后通过销售漏斗推动机会,一直到签单成交。
当你开始拥有销售团队、开始挖掘这种有机需求时,这很好,恭喜你。只是它不会持续太久,因为终端用户从根本上不等于企业买家,这种有机需求很快就会触及天花板,因为你不能指望从用户中凭空变出企业买家。
何时投入产品驱动销售
Lenny: 如果有创始人正在听这段话,心想,“好吧,我有产品驱动增长的部分,用户可以自助服务,也许我有销售团队,也许没有”,那么什么样的信号说明你的产品适合投资产品驱动销售?是不是每个以产品驱动增长为导向的公司最终都应该投资这个领域?还是说有些公司可以不用操心,一直保持产品驱动增长,或者一直保持销售驱动增长?
Elena Verna: 做产品驱动销售意味着你要向上拓展市场——
Lenny: 嗯。
Elena Verna: ——就这样。这意味着你要追求的合同金额可能超过了你的销售底价,也就是销售愿意介入并成交的最低金额,传统上大约在一万五千美金左右。如果你追求一万五千美金的合同金额,那意味着你可能也在尝试签下十万、二十万美金的合同。谁能消化十万、二十万美金的合同?不会是一个小初创公司,也不会是中小企业。更可能是中端市场的较高端——两百人以上规模的公司。更有可能是企业级市场——一千人以上的规模。
如果你还没有准备好向上拓展市场,我建议在产品驱动销售上先保持谨慎,因为销售意味着配额,销售意味着大额合同,销售意味着无论你愿不愿意,你都在向上走。而有些产品就应该留在专业消费者(prosumer)和个人市场。也许它们面向的是自由职业者、独立承包商,或者 squarely 面向初创公司。这些人根本不想和销售交谈,他们的消费意愿要低得多,价格敏感度也更高。他们更倾向于全程自助服务。所以你真的需要清楚认识到,这会对你的上市组织(go-to-market org)产生什么影响,因为它确实会改变你的方向,把你往上拉。
从自助服务到产品驱动销售的路径
Lenny: 明白了,所以我听到的是,如果你最初是一个以自助服务为导向的产品,现在开始考虑招聘销售人员,那么正确的方式应该是从产品驱动销售的路径切入,而不是另起炉灶,组建一个独立运作的销售团队,各干各的?
Elena Verna: 对,通往产品驱动销售有两条路径。第一种情况是我们刚才聊过的——我从产品驱动增长公司起步,一开始聚焦的是个人使用场景,然后逐步升级到公司层面的价值主张,这时候就需要产品驱动销售来承接。另一方面,我也可能是从自上而下的传统销售组织起步的,也就是说我的产品只通过销售来卖。这类产品通常从一开始就锚定较大的客户群体。要搭建自上而下的销售引擎,你最可能瞄准的是千人以上规模的企业级市场,或者是五百人以上的中端市场较高端。
进入产品驱动销售的原因无非两种:要么是你现有的自上而下的销售模式不奏效了,因为客户需要在签合同之前先看到价值——他们希望看到实际使用情况,至少看到一些初步的价值感知,然后才愿意签字画押。要么是你正在向下拓展市场,而传统销售模式带来的固定销售成本无法随规模递减——它基本保持不变,但你往下走时合同金额却在不断下降,所以你希望在销售过程中引入更多自动化,尽可能减少人工介入。
两条路径都可以走:在产品驱动增长之上叠加 PLS,或者在现有的销售驱动增长之上叠加 PLS。对于 PLG 来说,叠加 PLS 是为了向上拓展市场;对于 SLG(销售驱动增长)来说,叠加 PLS 是为了向下拓展市场。
销售驱动增长公司必须加入产品驱动元素
Lenny: 很好,我们稍后会聊到具体怎么搭建这套基础设施以及需要什么条件,但这让我想起了我们第一次播客中最大的收获之一,也是我后来多次引用的一个观点——你断言每一家销售驱动增长的公司都需要加入产品驱动增长的元素,否则就会被那些加入了的公司颠覆。你现在还是这个观点吗?
Elena Verna: 绝对的。不过我认为加入产品驱动增长元素有不同阶段,具体意味着什么需要分情况看。我认为每一家销售驱动型公司都应该向产品团队施加压力,让他们协助销售流程。这不意味着一定要做产品驱动增长,但至少在现有的销售驱动模式中要有产品辅助(product assist),而如果你真正解决了自助服务激活、自助服务参与,并让产品能够自我销售,那这种产品辅助就有可能演变为产品驱动增长。
这里开始出现一个最大的区别,而且在每家公司都显而易见——在 B2B 领域,不幸的是,我们已经放弃了对产品承担商业化模式责任的要求。我们陷入了一种螺旋:产品只管做产品,做完了扔给市场和销售去卖。
过去二三十年间,市场和销售在吸引企业买家、推销产品方面做得非常出色,构建了精密的故事和复杂的销售手册(playbook)。而产品团队几乎只在合同签订之后才开始介入——合同签了,使用数据才开始逐步浮现。在 B2B 中,我们把产品管理从商业化职责中解放了出来。当一家 SLG 公司真正开始引入产品辅助策略或产品驱动增长时,最大的痛点其实是教育产品团队:怎么才能让产品自我销售?这涉及到商业化意识的建立、付费转化过程中的商业化摩擦设计,以及让客户在自助服务环境下就能理解的正确定价指标(value metric)。
我的意思是,是的,我同意你的说法。每一家……好吧,我同意我自己的说法——每一家销售驱动型公司至少都应该加入一些产品辅助策略。但我甚至想更进一步:每一家销售驱动型公司都应该开始教育产品团队,并施加压力,让产品团队承担起商业化的职责。
产品团队如何承担收入责任
Lenny: 让我们顺着这条线再深入一下。这在实际中是什么样子?是产品负责人或者某个特定的组长级 PM(group PM)背收入指标、负责 P&L(损益)之类的东西吗?还是说当他们开始承担收入责任时,一般是什么样子?
Elena Verna: 承担收入责任有两种方式。第一块收入来源是你的自助服务收入,如果有自助服务收入,那就意味着产品在 literally 自己卖自己,所以产品团队里必须有人背自助服务收入指标。
Lenny: 嗯。
Elena Verna: 不过很多时候这个指标不会落在核心产品经理身上,而是落在增长团队身上。原因是核心产品管理主要聚焦于功能交付和核心使用场景的渐进式扩展,而增长产品管理负责的是产品分发策略。在 PLG 的情况下,它就是真正的自助服务商业化模式。而在 PLS 的情况下,我认为你不需要背收入指标,但你需要承担的是由产品创建的、需要与销售团队交接的销售管线。
具体来说,这体现为产品合格账户(product qualified account)——它是一个产品参与度阈值,不同于激活,也不同于核心参与度。它是由账户所展现出的使用量、增速、功能覆盖面或行为信号所构成的,这些信号在告诉你:“嘿,现在是时候让销售介入了。” 这就是通向商业化的桥梁,产品团队应当把它作为自己的职责来推进——即使是核心团队也应当如此——从而为销售团队输送健康、可预测、可持续的销售管线。
PQA、PQL 及相关术语辨析
Lenny: 好的,这是一个非常重要的话题。你刚才描述的这个概念,产品合格账户。也许现在是时候把其他几个缩写也定义一下,做个比较。有 PQA,有 PQL(product-qualified lead),还有 MQL(marketing-qualified lead)。你能把这些缩写系列梳理一下吗?然后我想就 PQA 继续深入,因为它看起来真的很重要。
Elena Verna: 我就从 PQA 开始讲,因为我们刚刚带过了它。PQA 是 product-qualified account 的缩写,也就是产品合格账户。它以账户为单位,是对该账户下多个用户使用行为的聚合。它可以是整体公司层面的——假设你吸引了一家公司,那么你根据整个公司的使用情况来认定 PQA;也可以是某个特定团队或工作区层面的,取决于哪种粒度对你来说是更好的预测指标,以及销售团队将要与谁对接。
产品资格认定所依据的完全是产品指标:使用量、增速变化。比如昨天我每天只新增一个用户,今天一下子加了十五个用户到账户里——这就是你需要关注的增速变化。又或者存在某些功能使用行为与企业级兴趣高度相关,产品应该推动每个账户都达到这些行为标准,从而将它们转化为合格的销售对话对象。
Elena Verna: 在 PQA 内部,可能有也可能没有 PQL,所以 PQL 就是产品合格线索。Lead 意味着账户里有一个我可以去销售的具体的人。这些 lead 就是那些购买者,是账户中的决策者。如果你的客群规模较小,比如在中小企业或中端市场的低端区间,你很可能在里面就有 PQL,因为用户本身可能就等于购买者——用户可以做那些购买决策。然而,越往高端市场走,终端用户与购买者之间的距离就越远,所以你可能看到非常健康的使用数据,PQA 指标非常亮眼,但里面就是找不到 PQL。
如果你直接让销售去找那个账户对接,情况会非常糟糕,用户体验也会很差——用户会说:“为什么销售要来找我?我在公司里根本没有决策权。我喜欢这个产品,但请别来烦我。“这就是为什么你会看到大量冷冰冰的对外销售邮件石沉大海、无人回复。你需要非常清楚地了解你的购买画像是谁,以及他们是否在你的用户群体里。如果在,你就有 PQL——直接对接就好。但如果不在,就得去外面找到他们。这时 MQL 的概念就真正派上用场了——市场团队仍然需要认定一个线索,将它与 PQA 关联起来。PQA 可以有一个已经是用户的 PQL,或者你可能需要一个由市场或销售带来的 MQL,把他们与已有的使用数据对接起来。
三条线索归因路径
Lenny: 太棒了。我们会分享一个链接,你有一张很棒的示意图,展示了 PQA 和 PQL 如何像漏斗一样进入销售流程,同时还有营销合格线索也在流入。基本来说,从原来只有一条通往销售的路径、知道该找谁聊,到现在变成了两条路径:产品在向你输送合格的潜在客户,市场也在向你输送合格的潜在客户。
Elena Verna: 还有第三条路径。市场也可能输送完全没有使用记录的线索,那就是纯粹的自上而下的 lead。所以实际上有三类线索归因渠道:第一,我有使用数据,而且其中一个用户就是我的 lead;第二,我有使用数据,但账户里没有 lead,需要市场把 lead 带过来,我要把使用数据与这个 lead 对接起来;第三,有 lead 进来了但没有任何使用数据,我还得从头向他们销售整个产品,无法利用已有使用数据作为上下文。这三个渠道非常重要,必须识别清楚。它们的转化率各不相同,销售手册也完全不同,而且说实话,往往需要不同的销售团队去跟进,因为所需要的销售支持方式差异很大。
不要把产品驱动销售塞进传统销售手册
Lenny: 你让我想起……你在 LinkedIn 上分享了很多非常搞笑的梗图。顺便说一下,所有听众都应该去 LinkedIn 关注 Elena,并订阅她的 newsletter,既搞笑又有料,简直是神奇的组合。我最喜欢你的一张梗图是《闪灵》那个——就是有人刚用了产品五分钟,然后一个销售人员就拿着斧头冲过来:“嘿,你想聊聊吗?”
Elena Verna: 那个……确实太真实了。那是我发过的互动量最高的梗图之一。我还有一张小便池的——一个男的正在用小便池,然后一个销售人员走过来说:“您想了解一下我们的企业版方案吗?”
Lenny: 对,就像一排十个小便池,他偏偏站到你旁边那个。
Elena Verna: 没错。所以这里很多公司忽略的一个关键点是,它们把产品驱动销售硬塞进了传统的自上而下销售手册里。这意味着什么?在传统自上而下的销售手册中,你获得的 MQL 或 lead 已经进入了企业级产品的考量周期。然而在产品驱动销售中,一个刚注册的新用户离企业级的考虑还差得远呢。他们只是在完成一个个人的待完成的任务,不是在为公司解决问题。你可以想象这是一个非常大的漏斗:最顶部是那些只想解决个人问题的用户,然后逐步过渡到团队层面问题的认知、考量和意向阶段,再进一步上升到企业层面问题的认知、考量和意向阶段。
自上而下的销售流程针对的是漏斗底部——那里已经有了要解决公司层面问题的意向;而产品驱动增长则从漏斗最顶部的个人层面问题开始。这是完全不同的时间线。如果一个用户刚注册账号,你十分钟后就去找他问”您的预算是多少?准备好购买了吗?“——这跟他们所处的是考量旅程的阶段完全不匹配。你不能把一个刚注册的新用户当作传统意义上的 MQL 来对待。他们还没到那个阶段。他们只是遇到了企业级问题中的一个小片段,还没有准备好购买。
Lenny: 这尤其让人烦,因为现在 SaaS 产品太多了,每个人都来找到你,尤其是当你在一家很棒的公司工作时,所有销售都想来推销——
Elena Verna: 是的,我记得一年前我刚加入 Amplitude 的时候,收件箱里塞满了各种”你现在在做这个,现在在做那个,买吧买吧买吧”。说实话,除非有人基于我已有的使用数据发来真正有诚意的内容,否则那些对外销售的邮件我根本不会留意,全部忽略。
Lenny: 等基于 GPT 的冷邮件再普及一下,情况只会更糟。天哪。
Elena Verna: 绝对的。
构建产品驱动销售的数据基础
Lenny: 好的,那我们转到实际上——你到底该怎么做?怎么搭建一套产品驱动销售的体系?我觉得大概有三个板块:你需要什么数据?你需要搭建什么基础设施和系统?然后是你需要什么样的人、怎么配置资源?也许我们从数据开始。要想做好这件事,你需要什么样的数据?
Elena Verna: 解决这个问题有不同的层级和规模。首先,从自上而下的直觉出发。你观察到的那些账户信号中,哪些跟销售团队非常兴奋——
Lenny: 嗯。
Elena Vernal: 对某个主动举手的人、或者通过使用行为提交销售表单的用户高度相关?你从这个开始就行了。就这么简单:还有多少其他账户在展现这些信号?当你线索量还很低的时候,一开始不想搞得太复杂。你要非常透明,就去理解销售团队看到了什么、他们对什么感到兴奋,然后把尽可能多的符合那个模式的账户喂给他们。唯一不能做的就是开始把每一个用户都发给销售,因为那是让销售团队最快说出”这个产品渠道是垃圾,我再也不想看到来自它的线索”的方式。他们的赢单率就摆在那里,他们的配额、工资取决于成交能力,所以他们会直接把这个渠道当作不靠谱的渠道无视掉。
第二个升级层次是:好,现在你有了直觉,但让我们实际看看在产品里到底是谁在举手。你去观察那些看起来像举手者、闻起来像举手者、行为像举手者,但并没有举手的人。这也许是一个非常简单的回归模型,也可能只是做一个简单的直方图分析,看区分举手的人和不举手的人的特征是什么,还有谁基于这些差异看起来也符合举手者的标准。
这应该就是你的第一个 PQA 模型。它应该非常简单——如果你能对注意到的一些最高系数跑一个线性回归,你就知道哪个对预测性的权重最大,然后就用那个。这里的关键是要非常早地让销售团队参与进来,这样你是跟他们合作,而不是把东西扔给他们就完了。同时你要有非常强的来自销售的反馈循环,确认你识别的东西到底对不对,因为 PQA 的定义不应该是静态的。它们在不断演进。现在正确不代表下个季度还正确,所以你必须跟销售团队建立很多反馈收集的仪式。
Lenny: 补充一点,Amplitude 和 Mixpanel 都有一个回归工具,可以帮助你识别指标之间的相关性和因果关系的连接,所以值得一提。Amplitude 的好像叫 Compass——
Elena Verna: 对。
Lenny: 然后 Mixpanel 的好像叫 Signal。
Elena Verna: 对。说实话,公平地讲,大多数时候我一开始是手动做的,因为这需要对数据有非常深入的理解——数据是否正确、我看到的到底是什么。因为你不想把太多相关变量一起丢进模型,那样就会出现变量之间相互描述的问题。即使它们在触发,可能并没有真正的预测力。这是跟分析团队的合作,也是跟销售团队的直觉的合作。然后,你才可以开始把它放进回归模型里,开始自动化,思考规模化的问题。目前市面上有很多 PLS 平台正在涌现、寻找产品市场契合点,可以帮你做这些。
我不确定是否应该从一开始就用这些工具,除非你真正理解了数据,因为买一个平台并不能帮你弥合”理解数据中什么真正重要”这个鸿沟。购买平台或使用第三方解决方案能帮你扩大努力规模——前提是你已经达到了第一个”数据销售契合”,然后可以据此扩展和增加分发。
Lenny: 数据销售契合。哇,这是个新词。有了。我之前没听过。数据销售契合。我喜欢。所以你的意思基本上就是先手动做,确保你完全理解到底在发生什么?
Elena Verna: 这是我的看法。是的。
我就是……我不太接受在没完全理解的情况下去规模化一个东西,因为数据可以对你撒谎,你可以把任何你想讲的故事塞进数据里。我需要真正理解它、理解它如何契合、你观察到的是什么、这一切是否说得通,然后才能开始用自动化。
关键指标与属性
Lenny: 好。关于你刚说的,最后一个问题——就是找到使用行为和用户之间的相关性和因果关系,理解该把谁发给销售。你发现过哪些常见的指标和属性,能预示他们应该被转给销售?
Elena Verna: 最重要的事情之一是在公司内部、团队内部创建网络效应,让账户中每新增一个团队成员都能从其他人那里获益。这不意味着你必须要有平台网络效应。你不是在试图成为 LinkedIn,不是在试图成为 Instagram——那些是平台网络效应。你要创建的是每个新增用户对账户的增量价值。这意味着——我稍微偏个题——不应该只有拉机制,也就是我把你拉进我的账户;还应该有推机制。任何来自已经在你系统中有账户的公司的新注册,都应该被展示加入该账户的选项,而不仅仅是创建一个全新的账户。
你要避免的是创建几百个互不相知的散兵式个人账户。我们人类是社群性的生物,我们喜欢被人群围绕、被人群认可,至少你要在公司内部营造那种从众心理,把人推和拉进账户里。最大的 PQA 指标之一就是公司内使用你产品的用户数量。顺便说一句,神奇数字通常是七。公司内有七个或更多用户——这里有某种奇怪的巧合,跟 Facebook 的七个好友、LinkedIn 的七个 collection 平行——但七这个数字我确实经常看到作为一个标记线。“嘿,这里有足够的价值在公司内多个人之间分布,可能值得谈一笔企业级交易了。”
第二重要的通常是某种量级阈值。比如对 Amplitude 来说是发送的事件数量,意味着你真正开始用分析覆盖你的整个应用了,而不仅仅是其中一小部分。对 Miro 来说是账户中的 board 数量。对 Figma 来说大概是任何设计中 revision 的数量。最后一个我想说的是速度(velocity)。速度是最棘手的,因为我们在交易数据中没有非常便捷的方式来衡量速度,但它实际上是最能触发正确介入时机的强大指标之一。因为速度的变化——不管是新增用户数、发送事件数还是存储使用量的变化——通常是一个非常出色的预测信号。
PQA 的简单模型
Lenny: 太棒了。好的,所以判断一个账户是否进入 PQA 状态的最简单模型,基本上就是用户数、使用量和速度。
Elena Verna: 对——
Lenny: 很好。
Elena Verna: ——而且用户数顺便说一下,也可以是某个使用量或速度指标。就是说,如果你只做一件事,那就看哪些账户拥有最多的用户。这就像是一个二八法则——用 20% 的努力,你大概能获得 80% 的价值。
Lenny: 喜欢这个。好的,我刚才把话题带偏了,你之前在讲需要搭建哪些数据基础。这方面还有什么要补充的吗?
行为信号
Elena Verna: 我想说要识别行为信号也非常重要,我举个例子。在 Miro,我们有一个非常强的行为信号:如果账户中发生了管理员变更,说明某种评估正在进行。管理员转移、新管理员被指定——这应该叮叮叮,所有警报都该响起来,你也许应该主动联系那个人,看看发生了什么。另一个很有意思的信号是你的使用条款页面、隐私政策页面。没人会去看这些东西,除非他们在考虑企业级交易。如果你看到某个账户的人访问了你的使用条款页面,去联系那个人。大概率你已经钓到了一个买家,你可以帮助他们提升对产品价值的认知。
Lenny: 哇,这太有意思了。这种东西只有亲身做过才能学到。
Elena Verna: 做过很多很多次才行,是的,不过这些——
Lenny: 噢。
Elena Verna: ——信号其实是通用的。我们在 MongoDB 也验证过,确实如此。所以当你在思考:产品中什么行为构成了评估流程?企业买家在寻找什么?我不会说观看一个网络研讨会或着陆到一个企业落地页是一个好的行为信号,因为那可能很烦人——我可能只是不小心着陆到某个页面,然后就被对外销售 SDR 的邮件序列轰炸了。那些在用户旅程中更深层、更有意义的行为,才是非常出色的预测信号。
销售骚扰的代价
Lenny: 你又提到了销售骚扰的话题,这让我想到……我甚至不知道该不该问这个,但你是否见过销售人员持续向潜在用户轰炸带来负面效果?这是否真的有害?我几乎不想知道答案,因为我感觉答案可能是否定的,但你怎么看?
Elena Verna: 我认为你必须审视渠道的有效性。你能用来与客户沟通的渠道是有限的。邮件是最显而易见的。你可以在应用内与他们沟通,可以用某种聊天机器人,也许可以投放一些付费营销,比如社交媒体或重定向展示广告,但这些成本很高。退一步想想:什么时候是联系的正确时机?我怎样才能抓住他们的注意力?如果你高度饱和地使用了你触达用户的主要渠道,即便到了对他们来说更合适的时机,他们也不会再做出反应了。
会不会造成伤害?我觉得你不会立刻察觉,但随着时间推移,我认为人们会对与自己无关的渠道沟通变得视而不见,因为”骗我一次,是你的错。好吧,你骗我打开了这封邮件。“骗我两次,就是我的错了,我会更加谨慎地决定打开哪些邮件、响应哪些通知。我认为你必须把用户旅程放在第一位,真正为用户和 PQA 考虑正确的时机。
PQA 的本质就是在正确的时间与客户接触,然后在所有沟通渠道上全力出击——但同时也要知道,账户会反复进出 PQA 状态。今天我可能处于 PQA,下周可能就不是了,所以如果你没有联系上客户,就需要暂停这些触达动作,等待下一个 PQA 时刻。如果你的产品在持续实现其目标,并且致力于让越来越多的账户达到 PQA 阈值,那个时刻一定会再次出现。
Lenny: 哇,这真的很有意思。我也很高兴听到这个答案。太好了。好的,那我们继续沿着这个话题聊——实施产品驱动销售流程需要什么。刚才讲了数据部分,那系统和基础设施、工具方面呢?你建议从哪里开始?
从现有系统出发
Elena Verna: 我对这个问题的态度始终是渐进演化,而非颠覆革命,所以尽可能从你现有的系统起步。我认为要避免的最大错误是:如果你的销售团队已经深度嵌入 Salesforce,不要试图让他们切换到别的解决方案。那是行不通的。你需要想办法把你需要的数据嵌入 Salesforce,而不是让他们去使用某个第三方工具。另外,在我真正验证产品驱动销售流程的可行性之前,我不会急于做出任何大的投入,也不会先去自动化任何环节。我更倾向于尽可能长时间地用”绿野仙踪”式的方式——也就是人工模拟——来快速获得初步的牵引力,这样我们就能验证是否值得投入资源去规模化,是否真的有商业价值。
Lenny: 在那个阶段你用的工具是什么?比如 Google Sheets?还是别的什么?
Elena Verna: Google Sheets,Looker、Tableau 的仪表盘,Amplitude 的图表和报告,也可以是 Salesforce 内部的组件,或者是通过 ETL 管道将数据导入 HubSpot 和 Marketo 再流入 Salesforce,还可以用专门针对 PLG 的 CRM 解决方案——甚至直接用 Excel 表格交付给销售团队来模拟不同的外呼方式。
Lenny: 你有没有分享过这种 MVP 级别的产品驱动销售技术栈推荐?如果没有的话,我觉得你应该分享,这看起来非常实用。
Elena Verna: 是的,我确实应该写。
Lenny: 好了,这不就来了嘛。
Elena Verna: 我的下一篇博客文章的主题有了。搞定。
Lenny: 就这样。好,如果这次聊天有什么收获的话,这就是一个。好的,在人员方面——我们谈了数据,谈了工具和基础设施——你建议在人员配置和资源投入方面一开始怎么安排?随着发展又该怎么演变?
PLS 需要的四类人员
Elena Verna: 对于 PLS,你需要的产品经理要能够推动账户达到 PQA 阶段。你需要销售人员,他们要能理解是哪些使用行为触发了 PQA,以及如何利用这些信息找到买家、赋能买家并将其转化为商机。你需要市场团队来教育终端用户和企业买家,让他们理解为什么这个企业级解决方案对他们有价值。你还需要分析团队——一个数据分析师,持续挖掘数据中的相关性信号,然后你们可以去验证因果关系。这就是你需要的四类人:产品、分析、市场、销售。我应该也提一下工程团队,当然,但我倾向于把他们和产品放在一起。
从销售驱动起步 vs 从产品驱动起步
Elena Verna: 这是一个渐进过程,不是一场革命。所以如果你是从销售驱动增长起步的,我强烈建议你去找销售团队,请一个人和你一起做一个试点。不要直接把这些 lead 丢进自上而下的销售流程,然后以为一切都会顺理成章。给自己配一个试点 AE(Account Executive,客户经理),或者一个 SDR,看看效果如何。你要把自己从销售机器的大本营中分离出来,在一个相对独立的环境中做原型验证,而不是在自上而下配额压力之下。如果你是在一个产品驱动增长的公司,那我建议你自己做销售。这有点像创始人驱动增长——你想想看,你可能需要先亲自成交前几笔交易,这样你才能真正理解整个过程。不要等到首批主动举手表达兴趣的客户出现就说:“我们没有销售人员就成交不了。”
不对,完全可以请某个人来辅助完成。让财务的人来做。你自己来做。我自己就很多次在聊天窗口里试着成交客户,只为理解客户的销售流程是什么样的。之后,你再决定实际需要招聘谁、如何扩展团队。但从 PLG 起步的 PLS,你实际上可以从一个 SDR 和 AE 合一的混合角色开始,因为你不需要把这两个职能分开。同一个人可以既对外触达客户,又同时完成成交,之后再走向角色专业化。从小处着手,保持灵活,验证可行,逐步扩展,但整个过程中都要有市场和分析团队的支持。
Lenny: 这个思路很简洁。我听到的是你不一定需要招新人,你大概率已经有了这些资源,问题只在于如何分配这个团队的时间来开始投入和试点。
Elena Verna: 对,我的哲学是,我想在发出招聘需求之前就先证明这个新岗位有 ROI。要创造 ROI,我需要自己先验证潜在的可行性。我几乎可以用我们从这条渠道最初产生的收入来为这个招聘提供资金。当然,这意味着你要做大量的个人贡献者级别的工作,可能要在自己不太舒适的领域摸索,但这也是你职业生涯中最快的成长方式,所以我认为这是成功执行的必要步骤。
产品驱动增长下的”零销售”奇迹
Lenny: 你想听一个关于产品驱动增长和不招销售的疯狂数据吗?
Elena Verna: 当然。
Lenny: 好。我正在做的一个系列访谈中,和 Notion 的创始人聊了聊,Notion 直到年经常性收入(ARR)超过一千万美元之后才招了第一个销售人员。
Elena Verna: 我完全相信。Miro 在 ARR 达到大约五百万到七百万美元之前也没有招第一个销售人员。他们就是通过支持团队来签合同,完全没问题。
Lenny: Notion 也一样,是他们客户成功和支持团队在做这件事。
Elena Verna: 是的。
Lenny: 这才是真正的产品驱动增长。
Elena Verna: 没错。
PLS 的内部协作模式变革
Lenny: 太棒了。好,我们已经聊了数据、工具和人员。你觉得要成功推行产品驱动销售这个衔接模式,还有什么是特别重要的?
Elena Verna: 产品驱动销售中最重要的一点是,内部需要一种不同的协作配置。在传统销售世界里,市场为销售创建销售管线,销售卖出产品,产品与付费用户互动以驱动留存。而在产品驱动销售中,产品获取并激活客户,同时产品为销售创建销售管线。关系不再是上市组织中市场加销售在一边,产品只是隔着栅栏扔功能过去让他们卖。
这里的协作是在产品与销售之间进行的,但这意味着产品必须承担起对销售管线的责任。最糟糕的做法是说”我要做产品驱动增长”或者”我要做产品驱动销售,但我要把它放在市场团队里做”。这是灾难的配方,六个月之内就会失败,因为产品必须对产品本身的销售承担责任。这不能掉以轻心,因为很多产品团队对承担变现目标感到非常、非常不舒服。我现在不是说产品应该只盯着收入,因为那是一个非常短视的结果导向。必须要有对长期目标和长期规划以及收入归属的清晰界定。
说到收入归属,我不是说每个产品经理个人也应该背上收入目标。我的意思是产品领导层应该对收入目标负责,而产品人员应该更多地对 KPI 负责——免费转付费转化率、套餐组合比例、PQA、也许还有 PQL——但这些都是通向收入的 KPI。对我来说最重要的关键是让产品团队承担起责任。你不能把产品驱动销售放在市场和销售团队里启动,然后以为公司内部可以保持原来的配置还能成功。产品必须有一席之地,产品必须感到自己对这件事负有责任。
产品团队必须承担营收责任
Lenny: 你说”承担起责任”,具体是什么样的?是他们的 OKR 里包含一些类似”你要驱动多少 PQA”这样的目标吗?是一个数字吗?“承担起责任”在这个语境下意味着什么?
Elena Verna: 我认为是这样的。每个产品团队都有某种目标,他们确实应该有保持健康、活跃用户群的目标。他们也应该有关于功能利用率或客户满意度方面的目标,但我要说的是,还要加上某种变现目标。这个目标具体是什么,对每家公司来说我认为各不相同,取决于他们的舒适程度以及他们离收入获取机制有多近。比如说在 Miro,我们的增长产品负责人背上有一个自助服务收入目标。她推动了这件事。她在产品端有一个必须达成的收入目标,同时她也和市场团队共享目标——因为当时我在那家公司负责市场。我们共享销售管线创建的目标,因为销售管线不可能没有市场团队就能创建出来。
市场团队需要做用户教育,需要找到买家,需要做基于账户的市场营销来吸引买家并将其与使用行为关联起来。产品和市场现在要携手创建销售管线并交给销售团队,但产品不能再像一座孤岛那样做一个功能工厂了。功能工厂的模式只在自上而下的销售组织中才行得通,而正如我所说,我认为这种组织在未来十年将被以价值为先的产品驱动增长严重颠覆。
Lenny: 这让我想到你在 LinkedIn 上分享的另一张搞笑迷因,再次提醒大家去看看 Elena 的 LinkedIn,那张迷因是产品团队被告知”你们要承担一些收入目标”时的反应——“哦不。” 对,就是这样。
Elena Verna: 其实这真的很有意思,因为很多增长负责人都会回避收入目标。获客目标,没问题。留存目标、活跃度目标,没问题。但涉及收入目标,“哦不,我怎么可能承担收入目标?“我觉得我们整个科技行业,我特别要指出 B2B 行业,在产品端承担收入责任这件事上确实变得有些懈怠了。我认为如果这个问题不解决,长期来看对我们是灾难性的。
收入目标的定义
Lenny: 我很喜欢这个。我真想专门做一整期播客来聊聊你的迷因策略和你的那些恶搞作品,但我们还是回到正题。关于收入目标,这个目标具体是什么样的?是”本季度 X 百万美元收入”这样的绝对值?还是季度环比增长率?你觉得人们实际上是怎么定义收入目标的?
Elena Verna: 对,自助服务收入和产品驱动销售收入会有不同的目标。自助服务收入的 KPI 应该完全是免费转付费转化率或试用转付费转化率,还有套餐组合、每用户平均收入(ARPU)。也可能是留存率——首期留存率、二期留存率——以确保你维持健康的收入。这些就是驱动自助服务收入的输出指标,应该是这些组成部分。我在获取新付费用户并最大化其价值方面是否存在摩擦问题?还是在留存这些付费用户上?这是流入自助服务 ARR 目标的三个输入,你应该了解团队最大的发力机会在哪里。
在任何情况下,大多数时候免费转付费转化是任何团队最大的关注点,因为我们要更好地转化并充实用户基数——假设我们有良好的产品市场契合度,有稳定的留存。在免费转付费转化中,有三个支柱需要持续投入,其中一个支柱压倒其他所有——那就是变现感知。就这么简单。如果你有一个免费增值产品,我保证你 75% 的免费增值用户不知道你在卖什么。仅仅专注于变现感知就能在推动变现上给你带来惊人的产出,而它本质上是产品通过功能墙、使用量墙、试用等方式传达付费产品价值的能力。
我听过 Slack 的故事——仅仅展示消息上限就对转化率产生了巨大的提升。我在 SurveyMonkey 也有亲身体验——只要在所有付费触发点加上一致的 EUI,用那种亚马逊金色,并确保每个用户至少看到三个。广告学里有一个”三次法则”——我们需要看到三次才能记住——这就推动了变现感知和转化率的提升,但这基本上占了你 80% 的工作。第二个支柱就是转化率优化——定价页优化、结账页优化、支持的币种、支持的支付方式,确保实际付费时尽可能少的摩擦。
自助服务 ARR 与 PQA 目标
最后一个支柱是:你卖的东西,人们想买吗?这是你真正去改变变现模型的地方。每个计划包含哪些功能?每个计划的价位是什么?升级路径是什么样的?你有附加策略吗?你有纯付费模式的变现策略吗?这是你最后才应该碰的,因为它涉及大量的跨职能协作和决策。但总结来说就是免费转付费转化、向上销售潜力和留存——这是自助服务 ARR。对于产品驱动销售,产品应该负责的是 PQA,但谁来定义 PQA?这是个大问题。
谁来迭代 PQA?然后,你如何让人们真正达到 PQA 阶段?就像产品团队通常负责参与度指标或激活目标一样,你也负责 PQA 目标,所以它就成了目标之一。根据最大的发力点在哪里,可以是激活、参与度或 PQA,但我越来越多地看到,产品驱动型——尤其是成熟公司——需要让产品团队聚焦在 PQA 上,但他们没有一个清晰的定义,因为销售团队往往各自为政、自行其是。产品无法向销售交付可预测的销售管线,这迫使销售过早进入自上而下的销售模式。
Lenny: PQA 目标可能像是”本季度 1000 个 PQA”这样?是这样的吗——
Elena Verna: 对对,所以你通常实际上几乎是看转化率。你看,“好的,我的 ICP——理想客户画像——细分市场中有多少团队是活跃的?“这是分母,然后这些团队中有多少在本月达到了 PQA 目标——
Lenny: 嗯嗯。
Elena Verna: ——这就像是从已参与的 ICP 团队到 PQA 的转化率。
变现感知的追踪方法
Lenny: 我特别喜欢你提到的这个变现感知的概念。
Elena Verna: 对。
Lenny: 让人们知道你有更多功能、付费后可以获得更多。你怎么追踪这个?是看每个账户或每个用户是否看到了这些向上销售的提示,还是看看了三次以上的比例?
Elena Verna: 我追踪的方式比较简单,两种方式。一个是定性方式,我就对用户跑调查,问”你知道我们在卖什么吗?“令人震惊的是有多少人完全不知道我们的付费计划里有什么——这就说明我们有重大问题了。或者我就追踪每个已激活账户的定价页浏览量:有多少已激活账户至少浏览过一次定价页?这至少是一个曝光程度的指标——他们触发了某种引导他们去探索定价页的触发器。有一点想给所有来自自上而下销售公司的听众提个醒——你可能会遇到的一个问题是,当你的产品团队在开发功能,尤其是付费功能时,他们只在付费计划中做设计评审并发布。
如果我在免费计划或低层级计划中,我根本看不到它。我甚至不知道它的存在,因为它在应用中不存在,因为它从来不是为我设计的,甚至连看都看不到。只要做一个小改动——推动设计评审去从客户的每一个状态来审视功能:免费状态、低付费状态、以及该功能实际解锁的目标状态——就能产生天壤之别。然后你就会理解那个功能是如何暴露给免费用户的,从而让他们以自助的方式意识到它的存在。
Lenny: 我太喜欢了,太喜欢了,所有这些具体的小洞察和技巧。谢谢你分享这些最终对人们最有用的小东西。还有几个问题然后就放你走。一个是关于陷阱。你觉得初创企业在尝试投入产品驱动销售时最容易掉入的陷阱是什么?你已经提到了一些,但当我问这个问题时你脑海中浮现的是什么?
产品驱动销售的常见陷阱
Elena Verna: 让我们把整个对话中已经提到的一些要点梳理一下。不要把 PLS 当作传统的自上而下销售流程来对待。每一个用户并不等于一个你可以去追逐的机会。你需要理解正确的触发条件和用户行为,它们可以帮助你自动化资质认定流程,所以这几乎是在自动化一部分 SDR 的工作——“什么时候是我的销售人员,我付了高薪的那个人,介入这个账户并创造价值的正确时机?”
销售互动必须为用户旅程增加价值,而不是打断它或制造额外摩擦,因为我见过太多——甚至有人发帖说”为什么十分钟后就接到电话?太烦人了,我会因为这个停止使用这个产品。“他们感到被误解了。要了解你的客户——你面对的是买家还是用户,他们是否在你的 ICP 细分市场中。预先掌握这些信息,这样你才能提供尽可能好的体验。
第二,让产品团队承担责任。这不能仅仅通过市场营销和销售来执行。产品团队必须在桌上有席位,而且在这种模式中,产品和销售的关系必须是最紧密的合作关系之一。这真的很难改变,尤其是在传统的自上而下销售的公司里,市场和销售的关系更近。尝试创造新的仪式,尝试在团队之间建立新的沟通方式,使他们对齐到相同的目标后面。
第三,不要把市场营销排除在外。你的大多数使用行为中不会包含买家。你需要市场营销,你的企业级市场营销、你的基于账户的市场营销去寻找并追踪那个买家,把他们和产品使用连接起来。依靠你的市场营销团队。仅仅因为你在做产品驱动增长和产品驱动销售,并不意味着你不需要市场营销,一个强的产品市场经理在帮助你做好信息传递、对外触达和销售支持材料方面可以创造奇迹。
第四,不要在数据效能上等太久。你可能在开始阶段很好地利用直觉,但要开始思考你将如何扩展数据方面的问题,因为产品驱动销售的核心就是利用产品使用行为来创建销售管线。你需要能够衡量使用行为,理解使用行为,追踪它,并不断演进它。
关键指标的行业基准
Lenny: 太棒了。还有两件事。一个是你在我们开始聊天之前分享过,你对提到的这些指标有一些行业基准,让人了解什么是好的水平,这样人们可以知道自己的目标可能是什么。你能分享些什么?
Elena Verna: 好的,关于基准,首先,是从个人用户使用——当那个用户进来完成一个待完成的任务——到创建企业级合同所需的时间。这不是几小时能完成的,不是几天能完成的,甚至不是几个月的使用就能完成的。我在 Netlify、Miro 和 Amplitude 这几家公司工作过,给各位一个基准:需要 12 个月以上的使用时间,才能以可持续的方式创建销售合同。
这当然不是一条放之四海而皆准的规则。有时会有高意图买家进来,你可能在一周内就完成签约,但平均而言,需要一年的使用时间才能把问题从个人层面升级到公司级解决方案。这需要时间,要有耐心。这不是”本季度获得更多注册,同一季度关闭更多销售管线”的问题。这说的是你在为长期增长做建设,而你关闭的合同和注册实际上是去年发生的,这才是最好的情况。
第二,不要混淆用户和买家。请、请、请在注册时对用户做画像,不要跳过那些引导问题。不,它们不会降低你的引导完成率,而在画像阶段就流失的那些人,本来意图就低。如果多一个问题就让他们放弃继续使用你的产品,那他们本来就不会激活。给你的用户做画像,了解你在和谁对话。这比几个百分点的流失率重要得多——那些人本来就不会激活。请不要再忽视用户画像了,因为我们所有人——
Lenny: 我喜欢这个说法。
Elena Verna: ——都厌倦了收到与自己无关的对外销售触达。然后,第三个是转化率。这里的转化率数据实际上来自真正的 PLG 公司,免费增值转化率通常在 5% 左右,试用转化率更接近 10% 到 15%,但你的合同金额会开始上升。
关键不在于你提高了转化率,因为很多公司仍然会先通过自助服务的变现流程,然后才会成为你的销售管线潜在客户。转化率保持不变,但你的合同金额和客户终身价值会开始不断上升,而这可以帮你创造一条微笑收入曲线。
用户画像的具体建议
Lenny: 太精彩了。你刚才提到的用户画像问题,我本来想问应该问什么问题。我猜可能更好的方法就是直接去 Miro 或 Amplitude,走一遍注册流程,看看他们问了什么。
Elena Verna: 对,我会给几个参数建议。第一,限制在三到四个屏幕,否则就会感觉太长了。确保每个问题收集的信息你要么会用在数据分群中——然后可以升级到个性化和信息传递——但至少要用在数据分群中,然后实验一下你能问到多深的信息。
你应该总是可以问到公司规模、所属部门、客户来源、在团队中的职级以及使用场景。这四个问题是通用的,每个人都习惯回答它们。其余的比如电话号码或者……也许你需要知道地址之类的,这些需要实验,看你想把多少设为必答题而不是选答题,但请、请、请一定要在你的引导问卷上做实验。你们所有人。
产品驱动销售之后是什么
Lenny: 最后一个问题。所有人都从销售开始,从销售驱动增长起步,然后产品驱动增长出现了,现在两者之间又有了桥梁——产品驱动销售。感觉总有新的增长业务和推进上市的方式。在产品驱动销售之后还有什么吗?如果有的话,下一步是什么?
Elena Verna: 嗯,我很好奇 AI 的崛起会在多大程度上自动化一些销售对话。它不会是纯粹的产品驱动增长,因为——
Lenny: 这不废话嘛。
Elena Verna: ——它不像单纯的产品自己就能卖出去。如果在聊天的另一端、邮件的另一端、甚至 Zoom 通话的另一端——因为他们可以对任何人做深度伪造——是 AI 在向你推销,给你非常深入和个性化的回答呢?我很好奇这将如何演变,因为 AI 能在几秒钟内以高度个性化的方式向你呈现海量信息,这比任何人类甚至内容管理系统目前能做的都要强大得多。
Lenny: 你想现在就为那个造个缩写词吗?
Elena Verna: 应该叫 AI sales 吧。
Lenny: A-I-S-L-
Elena Verna: 就这么定了。
Lenny: -G。哇,真拗口。Elena,这次对话完全是我期望的样子。我猜这期甚至会比你的第一期更受欢迎。非常感谢你抽出时间,在我们讨论的所有话题上都讲得这么深入。最后两个问题。大家如果想要联系你、了解更多,在网上哪里可以找到你?听众怎样才能帮到你?
Elena Verna: 我经常活跃在 LinkedIn 上,但我已经开始写自己的 Substack 了,所以如果可以的话,请订阅我的 newsletter。
Lenny: 一定要订阅。
Elena Verna: 我在 LinkedIn 上放更多短内容,在 Substack 上写更长的深度解释,不是为了和你的 Lenny Newsletter 竞争——
Lenny: 不会——
Elena Verna: ——而是——
Lenny: ——空间足够大,容得下所有人。我在 Substack 内部推荐了你的,我们会放上链接,正在听这个播客的人绝对没有理由不订阅。只有好处。
Elena Verna: 谢谢。我们还在和 Reforge 合作创建 PLG 课程,会深入到我谈论的所有这些概念的最细节层面,帮助你把这些概念落地实操。课程将在秋季上线——
Lenny: 太棒了。
Elena Verna: ——2023 年——
Lenny: 嗯。
Elena Verna: ——所以请务必关注。除此之外,我非常信奉知识的民主化,这样我们就不用一遍又一遍地犯同样的错误。你能帮我的最大方式就是分享你的洞察、分享你的知识、分享你的学习心得,这样我们就能一起成长得更快。
Lenny: 你是这方面最优秀的人之一,再次感谢你来做这期节目。
Elena Verna: 谢谢你的邀请,Lenny。
Lenny: 大家再见。非常感谢收听。如果你觉得这期节目有价值,可以在 Apple Podcasts、Spotify 或你最喜欢的播客应用上订阅本节目。也请考虑给我们评分或留下评论,这真的能帮助其他听众发现这个播客。你可以在 lennyspodcast.com 找到往期所有节目或了解更多关于本节目的信息。下期见。
术语表
| 原文 | 中文 |
|---|---|
| account-based marketing | 基于账户的市场营销 |
| AE (Account Executive) | AE(客户经理) |
| aha moment | 顿悟时刻 |
| ARPU (Average Revenue Per User) | ARPU(每用户平均收入) |
| ARR (Annual Recurring Revenue) | ARR(年经常性收入) |
| champion | 内部拥护者 |
| cold outbound | 冷对外销售 / 冷邮件 |
| Compass | Compass(Amplitude 回归分析工具) |
| consideration journey | 考量旅程 |
| content management system | CMS(内容管理系统) |
| contract value | 合同金额 |
| data sales fit | 数据销售契合 |
| data segmentation | 数据分群 |
| deep fake | 深度伪造 |
| design review | 设计评审 |
| downmarket | 向下拓展市场 |
| EIR (Entrepreneur in Residence) | 驻场创业者 |
| EUI | EUI(付费功能界面标识元素) |
| feature factory | 功能工厂 |
| feature walls | 功能墙 |
| freemium | 免费增值 |
| freemium conversion rate | 免费增值转化率 |
| go-to-market org | 上市组织 |
| group PM | 组长级 PM |
| ICP (Ideal Customer Profile) | ICP(理想客户画像) |
| individual contributor | 个人贡献者 |
| interim position | 临时职位 |
| job rec (job requisition) | 招聘需求 |
| job to be done | 待完成的任务 |
| lead attribution | 线索归因 |
| lifetime value | 终身价值 |
| marketing-qualified lead / MQL | 营销合格线索 |
| mid-market | 中端市场 |
| monetization awareness | 变现感知 |
| MQL (marketing-qualified lead) | MQL(营销合格线索) |
| network effects | 网络效应 |
| newsletter | newsletter(邮件通讯) |
| onboarding completion rate | 引导完成率 |
| outbound sales | 对外销售 |
| P&L (Profit and Loss) | P&L(损益) |
| pipeline | 销售管线 |
| platform network effects | 平台网络效应 |
| playbooks | 销售手册 |
| PLG (product-led growth) | 产品驱动增长 |
| price sensitivity | 价格敏感度 |
| product assist | 产品辅助 |
| product qualified account / PQA | 产品合格账户 |
| product-led sales | 产品驱动销售 |
| product-qualified lead / PQL | 产品合格线索 |
| prosumer | 专业消费者 |
| sales enablement | 销售支持 |
| sales floor | 销售底价 |
| sales-led growth | 销售驱动增长 |
| SDR (Sales Development Representative) | SDR(销售开发代表) |
| self-serve | 自助服务 |
| Signal | Signal(Mixpanel 回归分析工具) |
| SMB (Small and Medium Business) | 中小企业 |
| smile revenue curve | 微笑收入曲线 |
| top-down lead | 自上而下的 lead |
| trial conversion | 试用转化 |
| upmarket | 向上拓展市场 |
| usage walls | 使用量墙 |
| value metric | 定价指标 |
| velocity | 速度 |
| Wizard of Oz | 绿野仙踪式(人工模拟自动化流程) |
此文档由 AI 分片翻译(translate_long_document)