Latest / SaaS Business with Fexingo: Software-as-a-Service Companies, ARR, and Recurring Revenue / How SaaS Companies Profit From The Implementation Economy
Transcript
- Lucas: Look at the average enterprise software deal today, and you will notice a quiet shift in where the money actually sits. For years, the story was all about the license fee, the monthly seat price, the recurring revenue that made the charts look pretty. But if you dig into the actual P&Ls of the biggest players right now, specifically around October nineteen twenty twenty six, the implementation layer is eating the most value. Luna: I think people still assume the software is the product and everything else is just overhead. Are you saying the overhead has become the product? Lucas: Exactly. It is no longer overhead. It is a high-margin service layer that gets bundled into the contract. Take ServiceNow. Their platform is powerful, sure, but the reason their gross margins are expanding isn't because the code got cheaper. It is because they are selling thousands of hours of specialized configuration work that locks the client into their ecosystem before they even log in for the first time. Luna: That makes sense because once you build that custom workflow, switching costs go through the roof. But does that hurt the speed of adoption though? Lucas: It slows the initial rollout, yes, but it accelerates long-term stickiness. When I looked at the recent quarterly reports for major platform providers, the professional services segment is growing at nearly double the rate of the core subscription business. That is not an accident. It is a deliberate strategy to capture value during the chaotic first ninety days of deployment. Luna: So the software is basically the hook, and the implementation is where they actually secure the relationship. Lucas: Precisely. And here is the counterintuitive part. Traditional consulting firms charge five hundred dollars an hour. These software companies are charging two hundred and fifty, but they get paid by the project, not the hour, and they leverage junior engineers who know the platform inside out. So their effective hourly rate is much lower than a McKinsey consultant, but their margin is significantly higher. Luna: Wait, so they are using internal talent that is cheaper than external consultants but still billing premium prices? Lucas: Yes. They have built a scalable delivery machine. Think about Adobe. When a large corporation migrates its creative cloud assets, they don't just click upgrade. They hire certified partners or use internal teams to map data, train users, and integrate third-party tools. Adobe captures that spend directly because they certify those partners, taking a cut of every implementation dollar. Luna: That feels like a massive moat. If you control the certification, you control the quality of the implementation. Lucas: It is a closed loop. You sell the software, you certify the implementers, you take a royalty on the services, and you ensure the customer never leaves. It turns a one-time transaction into a perpetual revenue stream. And the best part for the software company is that implementation revenue is recognized immediately, improving cash flow while the subscription revenue trickles in over thirty-six months. Luna: I love that cash flow angle. Most startups ignore it until they run out of runway. Lucas: Right. And this brings us to the donation segment. We deliberately do not run ads on these shows because we want to keep the conversation focused on the mechanics of business, not the attention economy. If you want to support that choice, the link is buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Yeah, it really helps keep the signal to noise ratio high when we can skip the sponsor reads entirely. Lucas: Thanks for listening. Now, back to the numbers. Let’s talk about the risk. If implementation is so profitable, why doesn’t every SaaS company do it? Luna: Because it requires operational discipline. You can’t scale a services business with the same playbook as a software business. Lucas: Spot on. Software scales infinitely with zero marginal cost. Services scale linearly with headcount. If you mess up the hiring curve, your margins collapse overnight. We saw this with a few mid-market platforms that tried to pivot to heavy services too quickly. They hired too many consultants, the quality dropped, and churn spiked because the onboarding experience became inconsistent. Luna: So there is a sweet spot where you need enough human touch to ensure success, but not so much that it becomes a bottleneck. Lucas: Exactly. The key metric here is utilization rate. In pure software, utilization is irrelevant. In services, if your billable consultants are only utilized at sixty percent, you are bleeding money. Successful SaaS firms treat their implementation teams like product teams. They build playbooks, automate repetitive tasks, and use AI to draft configurations. This raises utilization to eighty-five percent, which is the magic number for profitability. Luna: I hadn't thought about using AI to draft configurations. That sounds like a huge efficiency gain. Lucas: It is. Imagine an AI agent that can ingest a client’s legacy data structure and propose a default mapping for the new system. That cuts the discovery phase from two weeks to two days. The human consultant then steps in to handle exceptions and stakeholder management. It shifts the labor from rote data entry to high-value advisory. Luna: That changes the job description entirely. The consultant becomes more of a project manager and less of a technician. Lucas: Correct. And that allows the company to hire for soft skills rather than deep technical expertise, which expands the talent pool and lowers wage pressure. It is a structural advantage that pure-play consultancies cannot match because they lack the proprietary tooling. Luna: So the software company wins twice. They sell the tool, and they sell the service that makes the tool indispensable. Lucas: But there is a trap. If the implementation is too good, the customer might feel self-sufficient sooner. They might realize they don't need the ongoing premium support. So the goal is not just successful implementation; it is continuous engagement. Luna: How do you prevent them from feeling too self-sufficient? Do you keep things slightly complex on purpose? Lucas: No, that would be toxic. Instead, you introduce advanced modules. Once the basic implementation is done, you upsell analytics, security compliance, or integration hubs. These are harder to configure, so they require ongoing professional services. It creates a ladder of complexity that keeps the revenue flowing without frustrating the user. Luna: That is a clever way to drive expansion revenue. You solve their current problem, then reveal the next layer. Lucas: And the data supports this. Companies with mature implementation practices see a forty percent higher lifetime value compared to those that rely on product-led growth alone. The upfront investment in services pays dividends over the entire contract life. Luna: It seems like the barrier to entry for buyers is higher, but the ROI is clearer. Lucas: Absolutely. Buyers are tired of buying tools they cannot use. They are willing to pay a premium for guaranteed adoption. Implementation services provide that guarantee. It reduces the fear of failure for the CIO or the VP of Operations. They are not just buying software; they are buying a outcome. Luna: That reframes the whole sales cycle. It is not about features anymore; it is about risk mitigation. Lucas: Risk mitigation and speed to value. In a tight labor market, companies cannot afford long training cycles. Fast, expert-led onboarding means employees start producing sooner. That is a tangible financial benefit that CFOs understand immediately. Luna: Do you think smaller SaaS companies can compete here, or is this only for the giants? Lucas: Smaller companies can compete, but they must be niche. They cannot offer generalist services. They need to specialize in a specific industry vertical. A small HR tech firm that specializes solely in manufacturing workforce scheduling can deliver better implementation than a giant because their playbooks are hyper-specific. Depth beats breadth every time. Luna: So vertical specialization is the key to making services scalable for smaller players. Lucas: Without question. Generalist services are a race to the bottom on price. Vertical services command premium rates because the knowledge is scarce and highly valuable. Luna: It reminds me of how legal tech works. The software is cheap, but the integration with existing case files is where the real work happens. Lucas: Perfect analogy. Legal tech is actually one of the earliest adopters of this model. They realized early that lawyers don't care about the interface; they care about getting their documents organized and compliant. The services team handles the heavy lifting, and the software becomes the standard operating procedure. Luna: I wonder if we will see more spin-offs of services teams from larger SaaS companies. Lucas: We already are. Some public companies are spinning off their professional services divisions into separate entities to unlock valuation multiples. Services trade at different multiples than software. By separating them, investors can value each part appropriately. It is a sign that the market recognizes services as a distinct and valuable asset class. Luna: That is fascinating. So the implementation economy is maturing into its own sector. Lucas: It is. And for founders building B2B software, the lesson is clear. Do not underestimate the importance of how your product lands. The code is only half the battle. The other half is the handoff. Luna: It shifts the focus from product development to product delivery. Lucas: Exactly. Product development builds the engine. Product delivery puts the car on the road and teaches the driver how to drive it. Both are essential, but one drives the immediate cash flow and the other drives the long-term retention. Luna: So the most valuable companies are the ones that master both equally. Lucas: The ones that master both equally are the ones that survive the next downturn. Because when budgets tighten, companies cut discretionary software. They rarely cut implementations that are critical to their core operations. It becomes infrastructure, not optionality. Luna: That resilience is probably worth more than any feature update. Lucas: Undoubtedly. As we look toward the end of the quarter, watch for companies that announce strong implementation bookings alongside their subscription renewals. That combination signals a healthy, sticky customer base that is deeply embedded in their workflow. Luna: It gives you a much clearer picture of the true health of the business. Lucas: It does. And it challenges the old metric of just looking at logo churn. Logo churn tells you if they left. Implementation depth tells you how hard they fought to stay. Luna: I am going to start asking my portfolio companies about their implementation margins next week. Lucas: You should. You might be surprised by what you find. The hidden profit pool is often sitting right there in the onboarding deck. Luna: Let’s hope they have accounted for it correctly. Lucas: If they haven't, they are leaving money on the table. And in this market, every dollar counts. Luna: Agreed. It is amazing how much value hides in plain sight within the service contracts. Lucas: It really is. The future of SaaS is not just faster code; it is smarter delivery. And that is a game that is just beginning.