How to productize a service when you are the only one doing the work

The nineteenth time you build the same thing

It is a Tuesday in March. You are building a menu you have built nineteen times before.

New client, new logo, a slightly different blue. But the work underneath is the same. The header. The mobile menu. The contact form that emails you when someone fills it in.

You could do it in your sleep. That is the cruel part. Because the money only shows up when you are awake at the keyboard doing it.

You have gotten faster over the years. It bought you nothing. Faster just means the next identical job shows up sooner.

Why "make something people want" is the wrong first question

Most advice on products starts with "what should I make?" That points you at invention. You start dreaming up something new and clever.

And that is how most first products die. They get built from the maker's excitement, not the customer's request. You launch, and you hear silence.

The other half of the usual advice is the beach. Build it once, sell it forever, sleep while it earns. I want to be plain about this. The sleeping part is real. The passive part is not.

A product earns without you at the moment of sale. It does not get built without you. It does not get sold without you either. The first one often takes more work than the service it replaces.

Slide one step, do not leap

Here is the real shift from the book. Service and product are not two boxes. They are two ends of one line, and you move along it one notch at a time.

Pure service is on the left. Every job is custom and you are there for every hour.

Productized service is in the middle. Same skill, but the offer is fixed. One set of pages, one flat price, one two-week delivery, one intake form instead of a fresh quote. You still do the work. But the deciding, quoting and explaining happen once.

Template or digital product is on the right. You built it once, and it sells without you in the room.

The book's example is a web designer. He froze his standard small-business site into a package: five named pages, one round of changes, two weeks. He swapped the discovery emails for one form with the eight questions he always asked anyway. None of it was new work. Within a month, the hours of quoting and scope talk were gone.

Then, and only then, he built the right-hand rung. He took the parts he had built by hand nineteen times and made them into one clean starter template, written up well enough that a buyer could install it without asking him a thing. It took two focused weeks. The first month it sold a handful of copies. Modest. But every one arrived without him at the keyboard.

What goes into the package

Most guides on productizing say the same thing: a fixed scope, a fixed price, and a clear line around what is and is not included. The book agrees, and adds the parts that make it buyable without a call. Here is the checklist, built from the book's examples.

In the book, the package ended up sold from a page instead of a sales call. That only works once every row above is written down.

Set the price by what the result is worth, not by counting the hours inside it. If you build the flat price as hours times your rate, it is still hourly with a round number on top. See value-based pricing vs hourly.

Pick the right thing with three tests

So what goes first? Run each idea through three tests. It must pass all three.

You already repeat it. A thing done once is a guess. A thing done nineteen times is a pattern.

Clients already ask for it. If three different clients asked for roughly the same thing, you do not have an idea. You have an order queue.

It works without your live explanation. If it falls apart the second you stop talking someone through it, it is still a service.

The winner is almost never your most impressive work. It is your most repeated work. Leave the parts that need your judgment as the service they honestly are.

Keep your hopes honest too. Goldman Sachs estimates the creator market at about 250 billion dollars, heading toward 480 billion by 2027. Inside it, the income is steeply skewed. A small product that earns a quarter of your income on a tenth of your time is still a real gain. Once orders grow, AI can carry much of the delivery. The NBER study on AI in support work found the biggest gains, around 34%, went to the least experienced workers.

Where the book picks this up

This is the problem The One-Person Million was written for.

Chapter 3, The Product: Make Money While You Sleep, covers the line from service to product, the three tests, and the four ways people get it wrong, like building a product nobody asked for. It ends with Tool 3, the Product Ladder: one pass that lays your work out from most of you to least of you, and marks what moves where.

Chapter 1, The Offer: Sell the Outcome, Not the Hour, matters here too. Time does not package. A service still defined as your hours cannot become a product until you name the result it sells.

The Product Ladder is in the free workbook. Once a product sells, the next worry is often too many orders to deliver alone.