Recurring Revenue Can Still Be Owner-Dependent

It is one of the first things buyers look for in a SaaS business. Customers pay every month, revenue is predictable, and the business appears to run while you sleep. At least, that is the dream. The problem is that recurring revenue is not automatically SaaS revenue. A customer can pay every month for software. They can also pay every month for consulting, SEO work, design, account management, or another service that requires the owner to stay involved. Both show up as monthly revenue. Only one might keep coming in while the owner is sitting on a beach pretending not to check Slack. I ran into this while reviewing a small SEO software business. At first glance, it looked like a recurring-revenue SaaS opportunity. Once I asked a few questions, the picture changed.

The business owned an SEO tool, but almost all current revenue came from done-for-you clients. The owner used the software to complete SEO work for customers. The customers were not mainly paying to log in and use the platform themselves. They were paying the owner to do the work for them. There were only a few older software users left from a previous promotion. The seller had shifted toward services because they produced more revenue, faster. That decision made sense. Selling a $500 monthly service can bring in cash much faster than trying to convince 50 people to buy a $10 subscription. The seller was not doing anything wrong. But the shift changed the type of business being sold. This was no longer primarily a self-serve SaaS business. It was closer to a software-enabled service business. The software helped deliver the work. The service clients paid the bills.

This is an easy trap for first-time buyers. A listing might use phrases like SaaS platform, subscription revenue, recurring income, proprietary technology, or automated software. All of those statements could technically be true. They can also hide the fact that the owner is still doing most of the work. A business can own software without making most of its money from software subscriptions. The real question is not whether software exists. The real question is what customers are paying for. Are they paying to use the product? Or are they paying the owner to use the product for them? That one detail can completely change the deal.

The difference affects valuation, workload, scalability, and transfer risk. Basically, all the fun stuff you are supposed to figure out before wiring someone your money.

SaaS businesses usually receive better valuations because subscription revenue can be predictable, scalable, and less dependent on the owner. Service businesses are often valued differently because the revenue may depend on labor, expertise, client relationships, and continued selling. A customer paying $100 per month for software access is not the same as a customer paying $100 per month for the owner to perform SEO work. The payment is recurring in both cases. The workload is not. A buyer should not pay a SaaS multiple for service revenue just because Stripe charges the customer every month. Stripe does not care whether you are selling software or personally writing 40-page reports at midnight.

The seller said client delivery only required a few hours per week. That sounded attractive. But fulfillment time is not the same as total owner involvement. You still need to ask how much time goes into finding new clients, following up with leads, closing sales, onboarding customers, answering questions, preparing reports, preventing cancellations, and maintaining the software. If delivery takes four hours, but selling takes another ten, you did not buy a four-hour-per-week business. You bought a fourteen-hour-per-week business with excellent marketing.

Software can often add more users without adding much extra work. Services usually do not work that way. More clients often mean more emails, more reports, more meetings, and more opportunities for someone to send “just one quick question” at 4:57 p.m. The software may make delivery more efficient, but each customer can still create additional labor. A buyer needs to understand what happens when the client count doubles. Does profit double? Or does the owner’s calendar simply catch fire?

Service clients may also be attached to the seller personally. They may trust the seller’s experience, communication style, or specific way of doing the work. That relationship may not transfer automatically. This becomes a major risk when there are only a few clients. If five customers produce most of the revenue, losing one after the sale can hurt quickly. The buyer needs to know whether clients are loyal to the company, the software, or the person currently answering their emails.

Whenever a seller mentions recurring revenue, start with the customer. Is it a self-serve software user? An agency? A consulting client? A business paying for managed services? Also ask how many paying customers exist and how much each one contributes. Ten subscribers paying $50 per month are different from one client paying $500. The total revenue may be identical. The risk is not.

Do not accept vague answers like “SEO,” “access,” or “monthly support.” Ask what the customer receives every month. Are they paying for software access, reports, strategy calls, keyword research, manual campaign work, custom recommendations, or ongoing consulting? This tells you whether the revenue comes from the product, the service, or a mix of both.

Ask the seller to walk through the entire process. That includes sales, onboarding, delivery, communication, renewals, and support. One of my favorite questions is: “What would stop happening if the owner disappeared for 30 days?” If client work stops, communication stops, and no new customers arrive, the revenue is still heavily owner-dependent. The business may be profitable. It just is not passive.

A software-enabled service business can still be valuable. The service clients may pay more than normal software subscribers. They may also provide useful feedback and dependable cash flow. A buyer could potentially improve the model by hiring someone to handle fulfillment, standardizing the service, automating repeated tasks, turning service features into self-serve software, licensing the tool to other agencies, or converting clients into subscriptions. There may be a real opportunity there. The mistake is not buying a service business. The mistake is thinking you bought SaaS.

I would separate the opportunity into three parts. First, I would value the software itself. That includes the code, brand, features, domain, documentation, and existing software users. Second, I would evaluate the client base. I would review contracts, payment history, workload per customer, retention, and customer concentration. Third, I would study the customer acquisition process. Where do new clients come from? If every customer requires the owner to personally prospect, pitch, and close, then the buyer is purchasing a sales role along with the business. That may still be acceptable. It just needs to be reflected in the price.

First-time buyers often focus too much on labels. They see “SaaS,” “subscription,” or “recurring revenue” and assume the business is automated and scalable. A better approach is to ignore the label for a minute and ask: “Who pays, what are they paying for, and how much work is required to keep them paying?” Those three questions usually reveal what the business really is. Recurring revenue can still be valuable. It can also be owner-dependent, labor-heavy, and difficult to transfer. So before paying a SaaS price, make sure you are actually buying SaaS. Not a freelance job wearing a software hat.