Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / How Customer Journey Maps Miss the Product-Led Growth Funnel
Transcript
- Lucas: At some point in the last three years, pretty much every B2B SaaS company I talk to has built a customer journey map. And most of them still start with a landing page, move to a demo request, hand off to sales. That works if you're selling a fifty-thousand-dollar contract with a six-month sales cycle. Luna: But a lot of SaaS today doesn't sell that way anymore. Product-led growth flips the whole thing — the product itself is the main acquisition channel. Lucas: Exactly. And the journey maps I see just don't reflect that. They map the marketing touchpoints to demo pipeline, but they miss the entire in-product experience that actually converts users. So for episode 47, I want to look at one specific gap: how customer journey maps miss the product-led growth funnel. Luna: Let's use a concrete example. Say a company called CloudBoard — it's a collaboration platform for remote teams. They offer a free tier and a paid pro plan. Their journey map probably starts with a Google ad or a blog post. Lucas: Right. And it shows the user signing up for the free trial, maybe sending a few messages. Then the map usually jumps straight to 'request a demo' or 'talk to sales'. But in a PLG model, the conversion happens inside the product. The user adds integrations, invites teammates, hits a usage limit — that's when they upgrade. The journey map doesn't capture any of that behavioral sequence. Luna: So the map is essentially blind to the most important touchpoints. The moment they add their fifth teammate, or the first time they use the search feature. Those are micro-conversions. Lucas: And the map treats them as invisible. I talked to a product manager at a decent-sized SaaS company last month. She showed me their journey map — beautiful, five swimlanes, all the typical marketing stages. But when I asked where 'time to value' was tracked, she said they don't have that on the map. time to value is the single strongest predictor of PLG conversion. If a user reaches their 'aha moment' within the first session, they're three times more likely to become a paying customer. Luna: Three times. I've seen similar numbers from a few PLG benchmarks. So the fix isn't to throw out the journey map — it's to add a product experience layer. Lucas: Exactly. You keep the marketing and sales touchpoints, but you overlay a second track that maps in-product behaviors. Which features they adopt, in what sequence, how long between signup and the first key action. And you measure drop-off at each step inside the product, not just at the demo form. Luna: Let's walk through what that looks like for CloudBoard. A new user signs up, completes onboarding, and then what? The map should track whether they create their first project within 24 hours. Lucas: If they don't, that's a drop-off point. The map should flag it. Then the next node: do they invite a teammate? That's the viral loop. PLG companies like Dropbox and Slack grew primarily through that loop — user invites colleague, colleague signs up, invites another. A traditional journey map wouldn't even have a node for 'invites teammate' because it's not a marketing touchpoint, but it's arguably the most important conversion event in the entire funnel. Luna: And what about the upgrade trigger? CloudBoard might have a limit on storage or number of projects. The user hits the limit, sees a prompt to upgrade. That's a touchpoint, but it's not a page visit — it's an in-app modal. Lucas: Right. And most journey maps are built from web analytics — pageviews, form submissions, email clicks. They don't pull data from the product analytics tool, so the in-app modal is invisible. That's the fundamental blind spot. The map reflects what marketing owns, not what the product owns. In a PLG company, the product owns the majority of the conversion path. Luna: So what's the concrete fix for a marketing team that wants to build a plg aware journey map? Where do they start? Lucas: First, pull your product analytics alongside your web analytics. Identify the top five in-product actions that correlate with retention or upgrade. For CloudBoard, that might be: create a project, invite a teammate, use the search feature, set a due date, integrate with Slack. Then map those as discrete touchpoints on a second swimlane below the marketing one. Luna: And then you can see where users drop off. Maybe ninety percent of users create a project in the first week, but only thirty percent invite a teammate. That tells you where to focus. Lucas: Exactly. The product team might build an in-app prompt at the right moment. The marketing team might send a triggered email after the first project is created, encouraging collaboration. But you only see that opportunity if the map includes the product behavior. Luna: It also changes how you think about the top of the funnel. In a PLG map, the acquisition channel isn't just ads and SEO — it's also the viral loop from existing users. Lucas: Right. So you need a node for 'referred by teammate' and a node for 'signed up after receiving a shared document'. Those are distinct entry points with different conversion behaviors. A person who joins because their entire team is already on CloudBoard converts at a much higher rate than someone who clicks a Google ad. Luna: And they churn less, too. Network effects create stickiness. Lucas: So the journey map has to account for that. Otherwise you're making decisions based on an incomplete picture. I think this is one of the most common gaps I see in practice — marketing teams that have invested heavily in journey mapping but haven't updated their framework to reflect a product-led reality. Luna: It's a practical evolution. The map should be a living tool, not a static document. Lucas: And that's really the theme of this whole show — your map is only as good as the data you put into it. If you're ignoring the product experience, you're flying blind on the part of the journey that matters most for conversion and retention. If these marketing conversations have sparked something you've actually used — maybe a new way of looking at your funnel, or a tweak to how you track a touchpoint — that's exactly why we keep this show free of ads. Luna: We've never run a sponsor spot, and we want to keep it that way. The whole idea is to share what we're actually seeing and learning, without any pressure to sell something in between. Lucas: So if that model works for you, and you'd like to support it, the link is buy me a coffee dot com slash fexingo. No perks, no tiers — just knowing the show stays exactly as it is. And regardless, we'll keep doing this. Luna: Alright, back to the map. So once you have that product layer, how do you decide which behaviors to track? Not every click is a milestone. Lucas: Good question. You want behaviors that are predictive of long-term retention. One framework is to look at what the most successful users — the ones who stay for six months or more — did in their first week. That's your 'aha moment' bundle. For CloudBoard, maybe it's creating three projects and inviting at least two teammates. That becomes a target behavior on the map. Luna: And then you measure the percentage of new users who achieve that bundle. If it's low, you have a product adoption problem, not a marketing problem. Lucas: Exactly. And the journey map should highlight that gap. I've seen companies redesign their onboarding flow based on this insight and lift trial to paid conversion by fifteen to twenty percent. But again — you only discover that gap if your map includes the product layer. Luna: What about the sales handoff? Even in PLG, some accounts eventually talk to a salesperson. Does the map need to capture that transition? Lucas: Absolutely. In a PLG model, sales typically engages when a user hits a certain usage threshold — say, fifty active users or a enterprise feature request. The journey map should show that trigger point. And it should track what happens after the handoff — does the sales call accelerate conversion, or does it create friction? Without that node, you can't optimize the handoff. Luna: So really, the PLG journey map is a hybrid. It blends product, marketing, and sales touchpoints into one integrated view. Lucas: Exactly. And it changes how you think about success metrics. Instead of just 'demo requests' or 'MQLs', you're tracking 'users who reached the aha moment' and 'teams with three or more active members'. Those are your leading indicators of revenue. If you're mapping the customer journey and ignoring those, you're missing the real story. Luna: Alright, I'm going to look at my own map differently now. I think a lot of listeners will too.