Latest / SaaS Business with Fexingo: Software-as-a-Service Companies, ARR, and Recurring Revenue / How SaaS Companies Profit From Implementation Friction
Transcript
- Lucas: The biggest misconception about software as a service is that the product itself does all the heavy lifting. It doesn't. The real money, the sticky retention, and the high-margin expansion often happen in the messy, unscalable middle: the implementation phase. Luna: Right, because you can sell a license overnight, but getting it to actually work for a complex enterprise takes months of sweat equity. Lucas: Exactly. And we're seeing a structural shift where top-tier SaaS companies are no longer treating implementation as a cost center to be minimized. They are treating it as a primary revenue driver and a defensive moat against churn. Take ServiceNow or Salesforce, for instance. Their professional services divisions aren't just side gigs; they are engineered profit pools that anchor the customer relationship. Luna: It makes sense when you think about it—if I'm paying two hundred thousand dollars a year for software, I need someone to make sure my data flows correctly between systems, or I'll just cancel out of frustration. Lucas: Precisely. This is the implementation economy in action. When a vendor handles your onboarding, they aren't just installing code; they are embedding their processes into your daily operations. That creates switching costs that are almost impossible to undo later. You don't just leave the software; you leave the workflow, the data architecture, and the internal training. Luna: So the 'product' is really the outcome, not just the login screen. Lucas: That's the core insight. If you look at the balance sheets of the most resilient B2B software firms, you see a deliberate blurring of lines between product and service. They hire consultants, they build partner ecosystems, and they charge premium fees for this bespoke attention. It’s counterintuitive for a scalable tech company to rely on human labor, but it works because labor scales with complexity, not just user count. Luna: But doesn't that hurt the gross margins? Human services usually have much lower margins than pure software licensing. Lucas: It does hurt the blended gross margin on paper, but it boosts net revenue retention significantly. Churn drops because the customer is invested. And here is the kicker: once the initial heavy lifting is done, those same service teams transition into ongoing advisory roles, which command higher hourly rates than basic support. It turns a one-time sale into a multi-year consulting engagement. Luna: Yeah, I've seen startups try to do this too—charging for setup—and it always feels like a nickel and dime game unless the value is obvious. Lucas: There is a difference between a setup fee and strategic implementation. A setup fee is transactional. Strategic implementation is transformative. When a vendor helps you redesign your entire procurement process using their tool, they haven't just sold you software; they've sold you efficiency gains that justify a price increase every single renewal cycle. Luna: So the risk shifts from the buyer adopting the tool to the seller ensuring the buyer succeeds with it. Lucas: And that alignment changes the entire sales motion. Salespeople stop pitching features and start pitching outcomes. They aren't selling a dashboard; they are selling a faster quarterly close or a more accurate forecast. That language resonates with CFOs and COOs far more than it does with IT managers. Luna: Which means the buyer's internal champion changes, too. It's less about the power user and more about the executive sponsor. Lucas: Spot on. The implementation team becomes the bridge between the technical users and the executive decision-makers. They translate software capabilities into business value. Without that bridge, you get what we call shelf-ware: expensive software that sits there, unused, until the contract expires and nobody renews it. Luna: Shelf-ware is the silent killer of SaaS valuations. Investors hate seeing low activation rates. Lucas: They do. And companies that master implementation see their activation rates skyrocket because they are actively guiding the user. But let's talk about the downside, because this model isn't free. It requires massive operational discipline. Luna: You mean managing thousands of different client projects without going bankrupt on overhead? Lucas: Exactly. If every implementation is totally unique, you scale linearly with headcount, which kills profitability. The smartest players are building frameworks. They create modular implementation playbooks that can be customized but not reinvented from scratch. It's like an assembly line for consulting. Luna: Standardizing the non-standard. That sounds incredibly difficult to pull off without making the solution feel generic. Lucas: It is difficult, but necessary. Look at how Microsoft Dynamics or Oracle handle large enterprise deployments. They have certified partners who deliver the work, but they enforce strict methodology standards. The vendor controls the IP, the partner provides the labor, and the customer gets a predictable timeline. It’s a tripartite structure that balances scale with customization. Luna: So the vendor stays asset-light by outsourcing the delivery while keeping the margin upside through certification and fees. Lucas: Right. And they capture data from those implementations. Every time a partner struggles with a specific module, that feedback loops back into the product roadmap. The implementation team becomes a research and development engine for the core software. Luna: That’s a closed loop. Product informs services, services inform product. It’s hard to compete with that kind of internal flywheel. Lucas: It’s very hard to compete with. Smaller rivals might have better technology, but if they can’t guarantee successful deployment, enterprises won’t touch them. Risk aversion is a huge factor in B2B buying. No one wants to be the manager who bought a cool tool that failed to launch. Luna: Safe bets win. Even if the safe bet is slightly more expensive or less feature-rich. Lucas: Always. Which brings us back to the pricing model. These companies are increasingly bundling implementation into the annual contract, hiding the cost inside the ARR number. It looks cleaner on the income statement, but it also locks the customer in for three years instead of one. Luna: Multi-year deals with built-in services are basically golden handcuffs for the client. Lucas: Golden handcuffs is the perfect description. Once you sign that three-year agreement and spend six months implementing, walking away means writing off a massive amount of sunk cost and disrupting your own operations. The retention math becomes almost automatic. Luna: It’s interesting how much of SaaS growth is actually driven by project management skills rather than coding skills. Lucas: We underestimate the importance of soft skills in tech. The ability to navigate a client’s politics, manage expectations, and deliver tangible results is what separates good software companies from great ones. Code is commoditized. Trust is scarce. Luna: And trust is built in the trenches of implementation, not in a marketing brochure. Lucas: Exactly. So if you’re investing in SaaS, look at the service ratio. How much of their revenue comes from professional services? Is it growing? If yes, they are likely building a durable competitive advantage based on customer success, not just feature parity. Luna: A quick note for our listeners: if these conversations are useful for what you're building or running, a couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Lucas: Thanks for supporting independent analysis. Let's circle back to the margin trap. Because while services drive retention, they can also dilute overall profitability if not managed tightly. Luna: Right, because if your service team is burning cash on every new client, you’re subsidizing growth instead of profiting from it. Lucas: Precisely. The goal is to make the implementation efficient enough that it pays for itself within the first quarter. Any longer, and you’re essentially giving away your software to prove its worth. That’s a dangerous game for public markets right now, especially with October twenty sixth approaching and investors scrutinizing unit economics closely. Luna: Investors want to see that the path to profitability is clear, even in the messy parts of the business. Lucas: They do. And the companies that show they can standardize their implementation curve—where each new client costs less to onboard than the last—are the ones that command the highest multiples. It signals that they’ve cracked the code on scaling success. Luna: Scaling success. That’s the ultimate metric, isn't it? Not just scaling revenue, but scaling positive outcomes. Lucas: Absolutely. Revenue is vanity, profit is sanity, but customer success is survival. In the implementation economy, those three things finally align. Luna: It makes you wonder which SaaS stocks are actually just consulting firms in disguise, waiting to pivot. Lucas: That’s a question worth asking before you write a check. If the software is secondary to the service, you’re buying a consultancy. And consultancies trade at much lower multiples than pure-play software platforms. Luna: So the key is distinguishing between a platform supported by services and a service wrapped in software. Lucas: Exactly. One is scalable by design; the other is scalable by effort. Knowing the difference saves you from overpaying for legacy models. Luna: Good distinction. It changes how you read the whole financial statement. Lucas: It does. And as we move deeper into Q four, watch which companies are doubling down on implementation teams versus cutting them. The market will reward the former. Luna: I’ll keep an eye on that. Thanks, Lucas.