How to Turn a Service Into a Recurring-Revenue Product

Service businesses discover product the same way: somebody realizes the last four engagements were 80 percent identical. The deliverables had different logos and different names, but the sequence, the artifacts, and the judgment calls were the same.Service businesses discover product the same way: somebody realizes the last four engagements were 80 percent identical. The deliverables had different logos and different names, but the sequence, the artifacts, and the judgment calls were the same.

That repetition is an asset, and most firms leave it on the floor. They keep selling hours, keep rebuilding the same spreadsheet, and keep pricing every engagement as though it were the first one. The revenue stays linear with headcount, and every good month has to be earned again.That repetition is an asset, and most firms leave it on the floor. They keep selling hours, keep rebuilding the same spreadsheet, and keep pricing every engagement as though it were the first one. The revenue stays linear with headcount, and every good month has to be earned again.

Turning that repetition into a product is not about writing software. It is about deciding, deliberately, which part of your service will stop being negotiable.Turning that repetition into a product is not about writing software. It is about deciding, deliberately, which part of your service will stop being negotiable.

Write out your last five engagements step by step. Then mark each step as one of two things: work that was essentially the same every time, or work that required real judgment about this specific client.Write out your last five engagements step by step. Then mark each step as one of two things: work that was essentially the same every time, or work that required real judgment about this specific client.

The repeatable core is your product candidate. Intake, data cleanup, standard reporting, recurring communications, compliance checklists, and scheduling almost always land here. The judgment layer — strategy, interpretation, hard conversations — stays a service, and it is usually the part clients value most anyway.The repeatable core is your product candidate. Intake, data cleanup, standard reporting, recurring communications, compliance checklists, and scheduling almost always land here. The judgment layer — strategy, interpretation, hard conversations — stays a service, and it is usually the part clients value most anyway.

This split matters because most failed productization attempts try to automate the judgment layer. That produces a tool that gives confidently wrong answers, and clients stop trusting it after the second one. Automate the core; sell the judgment.This split matters because most failed productization attempts try to automate the judgment layer. That produces a tool that gives confidently wrong answers, and clients stop trusting it after the second one. Automate the core; sell the judgment.

The wedge is the single piece of the core you can deliver as a product first. Good wedges share three traits: they are painful enough that someone would pay for that piece alone, they generate an artifact the client can see, and they produce data you keep.The wedge is the single piece of the core you can deliver as a product first. Good wedges share three traits: they are painful enough that someone would pay for that piece alone, they generate an artifact the client can see, and they produce data you keep.

That last trait is the one people skip. A wedge that leaves you holding structured data about the client's operation compounds. The next feature is cheaper because the data is already there, and the client's switching cost rises honestly, because leaving means leaving their own history behind.That last trait is the one people skip. A wedge that leaves you holding structured data about the client's operation compounds. The next feature is cheaper because the data is already there, and the client's switching cost rises honestly, because leaving means leaving their own history behind.

Ship the wedge to your existing clients before you sell it to strangers. They will tell you which parts are wrong, and they are not evaluating your marketing while they do it.Ship the wedge to your existing clients before you sell it to strangers. They will tell you which parts are wrong, and they are not evaluating your marketing while they do it.

The most common productization failure we see is a good tool priced like a service invoice. If the price is a one-time number, you have built a deliverable, not a product.The most common productization failure we see is a good tool priced like a service invoice. If the price is a one-time number, you have built a deliverable, not a product.

Recurring pricing has to attach to something the client keeps receiving. Access to their data, ongoing updates, monitoring, support, or continuing execution all qualify. A dashboard nobody opens does not, no matter how good it looked at launch.Recurring pricing has to attach to something the client keeps receiving. Access to their data, ongoing updates, monitoring, support, or continuing execution all qualify. A dashboard nobody opens does not, no matter how good it looked at launch.

Also decide early what the price scales on: seats, records, locations, volume, or programs. Pick the axis that grows when the client's benefit grows. Getting this wrong is survivable, but re-pricing an installed base is genuinely unpleasant, so spend an afternoon on it.Also decide early what the price scales on: seats, records, locations, volume, or programs. Pick the axis that grows when the client's benefit grows. Getting this wrong is survivable, but re-pricing an installed base is genuinely unpleasant, so spend an afternoon on it.

A product changes your company, not just your invoice. Support becomes a standing function instead of an occasional favor. Releases have to be communicated. Bugs have an audience. Onboarding has to work without your best person in the room.A product changes your company, not just your invoice. Support becomes a standing function instead of an occasional favor. Releases have to be communicated. Bugs have an audience. Onboarding has to work without your best person in the room.

Plan for three roles you may not currently staff: someone who owns the roadmap, someone who owns support, and someone who owns the data. In a small firm one person may hold all three, but the responsibilities should be named rather than assumed.Plan for three roles you may not currently staff: someone who owns the roadmap, someone who owns support, and someone who owns the data. In a small firm one person may hold all three, but the responsibilities should be named rather than assumed.

The service side changes too. Once part of delivery is productized, your team has to resist the pull of re-customizing it for the client who asks nicely. Every exception you grant moves revenue back to linear. Say yes to exceptions in the judgment layer and no in the core.The service side changes too. Once part of delivery is productized, your team has to resist the pull of re-customizing it for the client who asks nicely. Every exception you grant moves revenue back to linear. Say yes to exceptions in the judgment layer and no in the core.

In our own work this runs in three moves. Build: define the core, model the data, and ship the wedge to a handful of real users. Launch: put it into live conditions with migration, training, and pricing attached. Multiply: extend it to more clients, more markets, or more segments once the shape holds.In our own work this runs in three moves. Build: define the core, model the data, and ship the wedge to a handful of real users. Launch: put it into live conditions with migration, training, and pricing attached. Multiply: extend it to more clients, more markets, or more segments once the shape holds.

Some of our own ventures started exactly this way — a repeatable piece of campaign work that made more sense as a platform than as a service. That is the origin of how Local Campaign Pros and CA Slates operate today.

The sequencing point is simple: productize one slice while continuing to deliver the service. Companies that stop the service to build the product usually run out of runway before the product is credible.The sequencing point is simple: productize one slice while continuing to deliver the service. Companies that stop the service to build the product usually run out of runway before the product is credible.