Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / How Customer Journey Maps Miss the Exit Intent Blind Spot
Transcript
- Lucas: You spend months perfecting a customer journey map. You've got the awareness stage, the consideration stage, the purchase stage — every touchpoint polished and pretty. But there's a whole section of the journey you probably left blank. Luna: The exit. Lucas: Exactly. We map how people enter, how they convert, how they advocate. But the moment they start pulling away — the exit intent phase — that's often missing. And it's where some of the most valuable behavioral data lives. Luna: So we're not talking about the cancellation form itself. We're talking about the weeks or months before the customer even clicks cancel. Lucas: Right. The pre-churn micro-behaviors. There's a company called FieldSync — mid-size B2B SaaS, they make field-service management software for contractors. Think scheduling, dispatching, invoicing. About three years ago, they noticed their churn rate was hovering around six percent monthly, which for that vertical is not terrible but not great either. Luna: And their journey map didn't show why people were leaving? Lucas: It showed the exit — they had a 'cancel' step with a survey attached. But the map didn't capture the trail of breadcrumbs customers left before they quit. So they started overlaying product usage data onto their journey map. They created what they called a 'pre-lapse lane' — a parallel path that tracks signals of disengagement. Luna: What kind of signals? Lucas: Three big ones. First, ticket backlog growth. FieldSync's customers are contractors who log service tickets. When a customer's open tickets started piling up — unresolved issues stacking higher than usual — that correlated strongly with churn within the next sixty days. Second, login frequency decline. If a power user who logged in daily dropped to once a week, that was a yellow flag. Third, muted feature usage — specifically, they stopped using the dispatching tool but kept using invoicing. That suggested they were winding down operations with FieldSync. Luna: So they mapped these behaviors onto the journey map at specific time points? Lucas: Yes. They took their linear journey map — awareness, trial, onboarding, active use, renewal — and added a horizontal lane underneath called 'at-risk indicators.' At each stage, they plotted which behavioral thresholds should trigger a proactive outreach. For example, during the active-use stage, if a customer's ticket backlog exceeded ten open tickets for more than two weeks, the map flagged it. That triggered a call from a customer success manager — not a sales pitch, just a diagnostic conversation. Luna: And did it work? Lucas: Within six months, they reduced monthly churn from six percent to four point two percent. They captured about thirty percent more at-risk accounts before cancellation. And the interesting thing — they found that many customers who triggered the pre-lapse signals actually didn't need a discount or a feature they didn't have. They just needed someone to help them clear the backlog or retrain a new employee. Luna: So the journey map itself was fine — it was the data layer that was missing. Lucas: Exactly. The map is a framework. It shows you where to look. But if you're not feeding it behavioral data in real time, you're flying blind past the exit. Most journey maps are static — they're PowerPoint slides from a quarterly workshop. FieldSync made theirs dynamic, updating weekly based on product signals. Luna: But here's my pushback — if you add a pre-lapse lane, aren't you just adding complexity? Journey maps are already hard to socialize across the organization. Adding another row of signals might make it too dense for actual decision-making. Lucas: That's a fair point. And FieldSync's first attempt was a mess — they had thirty different signals in the pre-lapse lane, and nobody knew which one to act on. So they simplified down to the three I mentioned. The key is to pick signals that are leading indicators, not lagging. A drop in login frequency is a leading indicator. A cancelled subscription is lagging. If you can find two or three leading signals that predict churn with seventy percent accuracy or better, that's enough. Luna: So it's about precision, not volume. Lucas: Right. And this applies beyond B2B SaaS. Think about an e-commerce brand. The pre-lapse signals might be: the customer stops opening emails, stops visiting the site, stops buying but also stops returning items. Or a subscription box service — if someone pauses their subscription twice in three months, that's a pre-lapse signal. Map that on the journey. Luna: I want to push back again though — isn't this just churn analysis with a different label? Journey mapping is supposed to be about the customer's experience, not just the company's metrics. Lucas: That's the beauty of it — the pre-lapse lane actually helps you understand the customer's experience during a painful time. When a customer's ticket backlog grows, their experience is getting worse. They're frustrated. By mapping that, you're acknowledging that the journey includes moments of friction, not just moments of delight. Traditional maps gloss over that because they're designed to show an ideal path. Luna: So you're arguing that a journey map should include the bad parts, not just the good. Lucas: Exactly. The exit intent blind spot is that we treat churn as a binary event — either they're a customer or they're not. But the exit is a process. It has its own journey. And if you map that journey, you can intervene earlier and more humanely. Luna: I want to talk about the tools. What did FieldSync actually use to build this? Did they need a fancy platform? Lucas: They used a combination of their existing CRM — Salesforce — and a product analytics tool called Pendo. They created a dashboard that showed each customer's pre-lapse score based on the three signals. That score fed into the CRM, so the success team got alerts. The journey map itself was still a Miro board, but they updated it monthly with actual data. It's not about the tool — it's about the discipline of connecting behavior to the map. Luna: So any team could do this with the tools they already have? Lucas: Pretty much. If you have a CRM and a product analytics tool, you can build a pre-lapse lane. The hard part is deciding which signals matter and getting the team to act on them consistently. FieldSync's biggest hurdle was training the success team to trust the signals over a customer's verbal reassurance. A customer might say 'everything's fine' while their ticket backlog is through the roof. The data doesn't lie. Luna: That's a cultural shift, not a technical one. Lucas: Exactly. And it's worth it. FieldSync calculated that reducing churn by thirty percent added about one point two million dollars in annual recurring revenue. That's not trivial for a company their size. Luna: That is really concrete. So let's talk about how a listener could start. What's the first step? Lucas: Pull your churn data and look for patterns in the thirty to sixty days before cancellation. What do customers do — or stop doing? You might find that a lot of them reduce their login frequency, or stop using a key feature, or start contacting support more often with complaints. Those are your candidate signals. Then go to your journey map and add a lane called 'pre-lapse indicators.' For each stage of the map, define what a healthy versus an at-risk customer looks like. That's your starting point. Luna: One thing I'd add — don't just look at the customers who churned. Look at the ones who stayed, too. What did they do differently? That'll help you identify the signals that really matter. Lucas: Great point. The control group is essential. If you only study churners, you might mistake normal behavior for warning signs. FieldSync initially thought that a drop in feature usage was always bad, but they found that some customers cycled in and out of features seasonally. The key was the combination of signals — backlog growth plus login decline together was much more predictive than either alone. Luna: So the pre-lapse lane should capture combinations, not just individual metrics. Lucas: Exactly. And you need to revisit the signals periodically. Customer behavior evolves. What predicted churn two years ago might not work today. FieldSync reviews their pre-lapse signals every quarter and adjusts them based on the latest data. Luna: Alright, I'm convinced. But let me play devil's advocate one more time. Isn't there a risk that you over-optimize for retention and end up keeping customers who are actually unprofitable? The ones who churn might be the ones you should let go. Lucas: That's a really important caveat. Not all churn is bad churn. FieldSync actually identified a segment of customers who triggered all the pre-lapse signals but had very low lifetime value — they were costing more in support than they brought in revenue. For those, they chose not to intervene. The journey map should include a decision point: 'Is this customer worth saving?' That's a lane most maps don't have. Luna: So the pre-lapse lane needs a filter for customer value. Lucas: Right. You map the exit intent, but you also map which exits you should actively try to prevent. That's a strategic choice. And honestly, that's where journey mapping becomes a cross-functional tool — it forces marketing, sales, product, and finance to agree on what a 'good' customer looks like. Luna: That's a bigger conversation. Let's zoom back out. What's the one thing you want listeners to take away from this episode? Lucas: Your customer journey map is incomplete if it doesn't show the exit. Add a pre-lapse lane. Pick two or three leading behavioral signals. Update it with real data. And then act on it. The exit isn't a moment — it's a process. Map it. Luna: I think that's a really practical challenge. If these marketing conversations have sparked something you've actually used — or if you've ever added a lane to a journey map after listening — we'd love to know. We keep these episodes ad-free because we believe the best marketing content doesn't need to be interrupted. If you want to support that, the link is buy me a coffee dot com slash fexingo. No pressure, just a way to keep the conversations going. Lucas: Yeah, we're grateful for everyone who listens. And on that note — next episode, we're going to look at a different blind spot: how journey maps miss the customer's emotional state during the decision phase. Not just what they click, but how they feel. Luna: Looking forward to it. Thanks, Lucas. Lucas: Thanks, Luna. Talk soon.