Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise Software Sales Needs a Pricing Architect
Transcript
- Lucas: If these conversations are useful for what you're building or running, a quick note before we dive in. This is a business and technology show, and we keep it ad-free by design. Luna: Yeah, it's something we hear about from listeners a lot — that they appreciate not having to skip through sponsored segments. Lucas: Exactly. So if that's valuable to you and you want to support keeping it that way, the link is buy me a coffee dot com slash fexingo. No pressure, no perks — just a way to help. Luna: Alright, let's get into it. Lucas: So I want to talk about something that's been bubbling up in enterprise software sales conversations — the role of a dedicated 'pricing architect'. Not a sales rep who sets a price, not a product manager who defines a tier. An actual specialist whose job is to design the pricing model for each deal. Luna: I've seen this title pop up in a few job boards. It sounds almost like a blend of finance and sales strategy. Lucas: That's exactly what it is. And I think it's a response to a specific problem: enterprise software pricing has gotten too complex for the average rep to handle on their own. Think about it — you've got multi-year contracts, usage-based components, professional services attached, maybe a co-term clause. The pricing decisions made in a single deal can affect revenue recognition, customer lifetime value, and even product roadmap. Luna: Right, so the rep is incentivized to close the deal, not necessarily to optimize the pricing structure for the long term. Lucas: Exactly. And that's where a pricing architect comes in. They sit between the sales team, the finance team, and sometimes product. Their job is to design a pricing proposal that maximizes value capture while still getting the deal done. I was talking to a VP of Sales at a mid-market CRM company last week — about five hundred employees — and they hired a pricing architect about eighteen months ago. The results were pretty stark. Luna: What kind of results? I'm guessing we're not talking about just a minor bump in average deal size. Lucas: No, this was significant. Before the pricing architect, their sales reps had a lot of discretion on discounting. Typical deal had maybe forty percent discount off list price. After the pricing architect came in, they created a structured discounting framework based on deal size, customer segment, and contract term. The average discount dropped to around twenty-five percent. But here's the key — win rates actually went up by about five points. Luna: So they were discounting less but closing more? That seems counterintuitive. Lucas: It does, unless you consider that the pricing architect also changed how the company positioned value. Instead of 'we'll give you thirty percent off if you sign today', the reps started leading with a value-based proposal. The architect helped them build a business case for each deal — showing the customer exactly how much they'd save or earn by using the software. When the customer sees that the software delivers, say, two million dollars in value over three years for a seven hundred thousand dollar contract, they don't demand a forty percent discount. Luna: So the pricing architect is essentially enabling a shift from discount-led selling to value-led selling. Lucas: Exactly. And it's not just about discounting. The architect also rethought the packaging. Before they came in, the CRM company had three standard tiers — basic, professional, enterprise. But the architect realized that many mid-market deals needed a hybrid approach. So they introduced a 'growth' tier that combined features from professional and enterprise, but with a consumption-based overage for storage. That alone lifted average contract value by about fifteen percent in the segment. Luna: Interesting. I've heard that consumption-based pricing is getting more common in enterprise software, but it's tricky to implement because it shifts revenue from upfront to variable. Lucas: That's a great point. And that's exactly why a pricing architect is valuable — they understand the trade-offs between upfront revenue and long-term expansion. In this case, they designed the consumption component so that the base subscription covered a generous baseline, and then the overage kicked in at a higher margin. So the company still got a solid upfront commitment, but the customers who used more storage ended up paying more per unit, which actually improved gross margins on that segment. Luna: So the pricing architect is not just a deal-level resource. They're also impacting product strategy — what features go into which tier, how to meter usage. Lucas: Absolutely. And that's the part that a lot of sales leaders miss. They think pricing is a negotiation tactic. But really, it's a product decision. If you price a feature too high, you'll get resistance. If you bundle it into a tier that's too expensive, customers might not buy it. The pricing architect works with product managers to set feature pricing based on adoption data and willingness to pay studies. In that CRM company, they surveyed customers and found that a reporting dashboard feature was highly valued but underused because it was locked in the enterprise tier. So they moved it to the professional tier and increased the price of enterprise by ten percent, justifying it with other advanced features. Net result: professional tier adoption went up, enterprise revenue didn't drop. Luna: Sounds like they did a classic feature-value optimization. But is the pricing architect role scalable for smaller companies? I imagine a startup with fifty employees can't justify a full-time person for this. Lucas: Fair question. At smaller companies, the CEO or a senior product person often plays this role. But I think as soon as you're dealing with multiple segments, custom contracts, and a sales team of more than, say, ten reps, it starts to make sense to have someone dedicated. Even if it's not a full-time role initially — it could be a senior IC on the revenue operations team who spends half their time on pricing. Luna: And what about the skills needed? This isn't just a finance person or a salesperson. It's a hybrid. Lucas: Exactly. The best pricing architects I've met have a mix of analytical rigor — they're comfortable with data, modeling, and financial statements — and strategic thinking. They need to understand buyer psychology, competitive dynamics, and product value. Some come from management consulting, some from product management, some from corporate development. But they all share one trait: they're comfortable saying 'no' to a rep who wants to give a seventy percent discount to close a deal. Luna: I imagine that creates some friction. The rep wants to close, the architect wants to maintain pricing integrity. Lucas: There's definitely tension. But the better companies frame the pricing architect as a partner, not a gatekeeper. They're there to help the rep build a better deal, not to block it. At that CRM company, the architect would sit in on deal reviews and help reps craft proposals that met the customer's budget without sacrificing margin. Over time, the reps actually started seeking out the architect's input because they saw that deals with pricing architect involvement closed faster and had higher renewal rates. Luna: Faster close? That's an interesting outcome. I would have thought that adding a reviewer would slow things down. Lucas: You'd think so, but the data showed the opposite. Before the architect, deals often got stuck in internal approval loops because reps would propose discounts that exceeded their authority, then have to go to the VP for sign-off. That could take days. With the architect, there was a clear framework — if a deal fits within certain parameters, it can be approved quickly. And because the architect had already analyzed the deal structure, the approval was faster. The average sales cycle dropped by about two weeks. Luna: So it's a win-win: better margins, faster sales, and presumably happier customers since they're getting a package that's more tailored to their needs. Lucas: Exactly. And that's really the core of the pricing architect's value. It's not just about extracting more money from customers. It's about aligning price with value so that both sides feel good about the deal. When a customer realizes they're paying for features they don't use, or that they could get a better price with a different contract structure, that breeds churn. The architect helps prevent that. Luna: I'm wondering — is this role more common in certain types of software? Like, does it make more sense for platforms with usage-based components than for pure SaaS? Lucas: It's definitely more critical when you have complexity — multiple pricing dimensions, consumption elements, or a product that spans different use cases. But I'd argue that even a simple SaaS product with a single price point can benefit from a pricing architect. Because even a simple price is not just a number — it's a signal. Is it penetration pricing to capture market share? Is it premium pricing to signal quality? A pricing architect helps the company be intentional about that signal. Luna: But in a simple SaaS scenario, the decisions might be infrequent. Maybe once a year you review pricing. So the role might not be full-time. Lucas: Right, but even then, you can have someone on the revenue ops team who owns pricing as part of their remit. The key is that someone is thinking about it systematically — not just reacting to competitive moves or rep requests. Luna: Let's talk about a practical implementation. Say I'm a VP of Sales at a company that's considering hiring a pricing architect. What's the first thing I should do? Lucas: First, do an audit of your current pricing process. Look at every deal over the past six months. How often were discounts more than thirty percent? How many deals had custom pricing that didn't follow a tier? How many had multiple renegotiations? That data will tell you if you have a pricing problem. If you see a lot of variance, you probably need someone to create structure. Luna: And where do you find this person? It's not a common job title yet. Lucas: I'd look for candidates with experience in revenue operations, product management, or corporate strategy. Some consulting firms have pricing practices — you can poach from there. Also, look internally. Your best sales ops person might have the analytical chops and the sales acumen to step into this role. The most important thing is that they have credibility with both the sales team and the finance team. Luna: Credibility is key. If the reps don't trust the architect, they'll just go around them. Lucas: Exactly. And that's why the architect needs to be a facilitator, not a dictator. At that CRM company, the architect spent the first three months just listening to sales calls, attending deal reviews, and understanding the customer's pain points. Then they built the framework collaboratively with input from top performers. By the time it launched, the reps felt ownership of it. Luna: So it's as much about change management as it is about pricing science. Lucas: It really is. And that's a point that doesn't get enough attention. You can have the perfect pricing model on paper, but if your sales team doesn't believe in it, they'll undermine it. The pricing architect has to be a translator — turning data into stories that reps can use. Luna: I'm curious about the impact on customer relationships. Does a more structured pricing approach ever feel too rigid from the buyer's perspective? Lucas: It can, if you're not careful. But a good pricing architect builds in flexibility for legitimate exceptions — like a strategic partnership or a non-profit discount. The key is that exceptions are documented and intentional, not arbitrary. Buyers actually appreciate consistency. If they know that the price is based on a clear framework, they trust the vendor more. Luna: That's a good point. So the role seems to be a natural evolution as enterprise software matures. I'm thinking of the early days of SaaS, where pricing was simple — per user per month. Now we see consumption, outcome-based, hybrid models. It's getting complex. Lucas: Exactly. And with complexity comes the need for specialization. I don't think every company needs a full-time pricing architect today, but within five years, I'd bet it becomes as common as a dedicated sales operations role. Luna: So for our listeners — whether they're in sales leadership, product, or running their own company — what's one action they can take this week to start moving in that direction? Lucas: Pull your last quarter's deals. Look at the distribution of discount percentages. If you see a long tail of outliers — some deals at ten percent off, some at sixty percent — that's a sign that you're leaving money on the table or giving too much away. Start by asking why. Then consider whether you need someone to own that question full-time. Luna: It's a small diagnostic that can lead to a big change. Lucas: Exactly. And often, the first step is just recognizing that pricing is not a one-time decision or a negotiation tactic — it's a strategic function that deserves dedicated attention.