Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / Why Journey Maps Miss the B2B Procurement Portal
Transcript
- Lucas: There's a moment in almost every B2B sale where the deal goes dark. The champion loves your product, the demo was flawless, and then — crickets. And a lot of journey maps completely miss why. Luna: Because the champion isn't the only buyer. And the journey map probably stops at 'demo booked' or 'proposal sent.' Lucas: Exactly. I want to talk about one specific blind spot today: the procurement portal. This is the system that enterprise buyers — especially in regulated industries — are forced to use once they decide to move forward. And it's a black box that most marketing teams never map. Luna: I've seen this firsthand. A former client of mine — a mid-market SaaS company selling compliance software — lost a $200,000 contract because they never accounted for the procurement team's compliance checklist. Lucas: That's the perfect example. Their journey map probably showed a nice linear flow: awareness, consideration, demo, proposal, close. But somewhere between 'proposal' and 'close' there's this invisible gate — the vendor portal — where a completely different set of people with completely different priorities take over. Luna: And those people don't care about your product's UX or your founder story. They care about SOC 2 reports, data residency, insurance certificates, and whether your W-9 is in the right format. Lucas: Right. So the question for this episode is: how do you build a journey map that actually includes the procurement portal? And what's the one change that can cut procurement friction by maybe 40 percent? Luna: Let's start with the mapping part. I think most marketers don't even know the portal exists. Lucas: They don't. Because the champion doesn't talk about it — it's boring, it's back-office, it's not part of their buying experience. But for the procurement officer, that portal is the entire experience. So step one is to add a 'procurement lane' to your journey map — a horizontal swimlane that runs parallel to your main customer journey, starting the moment a deal hits legal review or compliance. Luna: And that lane has its own stages. Maybe it's: portal login, document upload, review cycle, negotiation, signature. Each stage has its own friction points. Lucas: Exactly. And you can populate that lane using data you already have. Closed-lost analysis is the easiest place to start — just look at deals that got stalled or lost after the proposal stage. What was the last action recorded in your CRM? For a lot of companies, it's 'sent proposal' and then 'deal lost — no decision.' But if you dig into the notes, you'll find phrases like 'procurement requested additional security docs' or 'vendor portal rejected our insurance certificate.' Luna: That's the smoking gun. I've seen companies where the procurement lane accounted for three-quarters of their stalled deals, but nobody had ever visualized it. Lucas: And once you visualize it, you can start fixing the bottlenecks. Which brings me to the one change that makes a huge difference: pre-fill the security questionnaire. Luna: The security questionnaire — that's the dreaded multi-page PDF or online form where you have to answer 100 questions about encryption, access controls, incident response, and so on. Lucas: Exactly. Every enterprise vendor has one. And every time you send a new proposal, the procurement team sends back the same questionnaire. If you haven't pre-populated it with your standard answers — ideally in a format that matches their portal — you're adding days or weeks to the cycle. One company I worked with cut their average procurement time from six weeks to three and a half just by creating a master answer document that the sales team could upload instantly. Luna: And they probably also reduced the number of deals that died in silence. Lucas: Massively. But here's the thing — the master document only works if you update it regularly. If your SOC 2 report is from 2023 and the portal wants the 2025 version, you're back to square one. Luna: So there's a maintenance component. Who owns that? Marketing? Sales? Revenue operations? Lucas: Great question. In most orgs, nobody owns it, which is the problem. I'd argue it should live under revenue operations, but marketing needs to surface it in the journey map. If marketing is responsible for understanding the customer experience end to end, they can't stop at 'purchase' — they have to include the procurement experience, because that's part of the customer's reality. Luna: And for companies selling to regulated industries — healthcare, financial services, government — the procurement portal is often more complex than the product evaluation itself. Lucas: Absolutely. Let me give you a concrete example from a logistics software company I worked with. They sold to mid-market manufacturers. Their journey map was beautiful — top of funnel content, webinars, demos, case studies. But when I looked at their CRM data, I found that 60 percent of deals that reached 'proposal sent' never closed. And the notes on those lost deals consistently mentioned 'vendor portal requirements not met.' Luna: So what did they do? Lucas: They added a procurement lane to their map. They listed every portal requirement: insurance minimums, data processing agreement, business continuity plan, diversity certification. Then they asked the sales team to start collecting those documents before the deal even reached procurement. The result? Their close rate on enterprise deals went from 30 percent to 48 percent within six months. Luna: That's a huge lift. And it came from a touchpoint they weren't even tracking. Lucas: Exactly. And that's the core insight: if you're not mapping the procurement portal, you're not mapping the real customer journey. The champion doesn't go on the journey alone — they bring procurement along, and procurement has its own map. Luna: I want to push on one thing, though. For smaller companies — say, a startup selling to its first enterprise customer — the procurement portal can feel overwhelming. They might not have a SOC 2 report or a diversified insurance portfolio. How should they approach this? Lucas: Honestly, they need to be transparent about what they have and what they don't. Procurement teams are used to working with small vendors. The key is to not ignore the portal. Show up, fill in what you can, and communicate the gaps. I've seen startups lose deals not because they lacked certification, but because they never responded to the portal request at all. Luna: So the map still helps — it just reveals that the bottleneck is documentation readiness rather than portal complexity. Lucas: Right. And that's actionable. You can prioritize getting your SOC 2, or you can negotiate a timeline with the first few customers. But you can't fix what you haven't mapped. Luna: Let's talk about how to gather data for this lane. You mentioned closed-lost analysis. What else? Lucas: Interviews with procurement officers, if you can get them. Or even your own sales team — they know what questions procurement asks. Also, look at the actual portal. If your customers use something like Ariba or Coupa, log in and see what the workflow looks like. What fields are required? What documents are needed? Map that step by step. Luna: And what about the emotional experience? Journey maps usually include customer feelings — excited, confused, frustrated. What's the emotional arc of procurement? Lucas: I'd say it starts with neutral efficiency — procurement just wants to get this done. Then frustration when documents are missing or wrong. Then relief when everything checks out. And finally, satisfaction when the contract is signed. But if you miss a requirement, it goes from neutral to angry pretty fast. Luna: So the emotional stakes are real. And that matters for retention, too — a bad procurement experience can sour the relationship before the product is even implemented. Lucas: Exactly. The procurement portal isn't just a transactional step. It's the first operational interaction your customer has with your company. If it's clunky, they assume your product will be clunky. If it's smooth, they trust you more. Luna: That reminds me of something we talked about a few episodes ago — the post-delivery unboxing experience. Procurement is like the unboxing for B2B. It sets expectations. Lucas: Great parallel. And just like unboxing, it's often overlooked because it happens after the purchase decision. But in B2B, the purchase decision isn't final until procurement signs off. Luna: So if you're listening and you're responsible for a journey map, what's the one thing you should do this week? Lucas: Pull your last ten closed-lost deals from your CRM. Read the notes. If you see any mention of procurement, vendor portal, security questionnaire, or compliance — you've found your blind spot. Start mapping that lane. Luna: And if you don't see any mentions, it might mean your sales team isn't writing them down. So talk to them directly. Lucas: Right. The data is there — you just have to look. And once you see it, you can't unsee it. The procurement portal becomes an obvious part of the journey. Luna: Before we wrap, I want to mention something. If these marketing conversations have sparked something you've actually used — maybe you added a procurement lane to your map this week, or you started pre-filling security questionnaires — and you find value in the show, listener support is what keeps it ad-free. It's a small way to keep conversations like this going. Lucas: Yeah, absolutely. It's at buy me a coffee dot com slash fexingo. No pressure, but if it's made a difference, that's where you can find it. Luna: Okay — back to procurement. Lucas, you mentioned the emotional arc. I think there's one more stage: the procurement officer's satisfaction after a smooth process. That's a retention touchpoint, too. Lucas: Good point. If procurement has a good experience, they're more likely to approve future expansions or renewals. So map that, too. The post-signature experience includes things like onboarding with the portal, invoice setup, and compliance renewals. Luna: So the procurement lane doesn't end at signature. It extends into the customer lifecycle. Lucas: Exactly. And that's what makes it a real journey, not just a transaction. So the takeaway: if your journey map stops at 'deal won,' you're missing half the story. Add a procurement lane, pre-fill the documents, and watch your close rates improve. Luna: And if you've got a story about a procurement portal that made or broke a deal, we'd love to hear it. Reach out to us. Lucas: That's all for this episode. Thanks for listening, and we'll see you next time.