---
title: "Productizing a Service: From Hours to Licenses"
description: "Learn how to identify which parts of your consulting work can become products and which can't. A practical guide to transitioning from billing hours to building scalable products, including pricing strategy, managing the revenue gap, and knowing when to automate versus when to stay hands-on."
image: "https://cdn.sethserver.com/blog-images/productizing-a-service-from-hours-to-licenses-social.webp"
---

# Productizing a Service: From Hours to Licenses

Not everything we do for clients is a product ready to be unleashed upon the universe. A lot of what we do is make sane judgment calls based on our own experiences.

The mundane, repeatable parts are what we can productize. The things you do the same way for every client, no matter what they're building or who they're selling to. For me, that was the SEO and AI-search audit. Every startup with a content problem got the same crawl, the same inventory, the same questions about positioning. I was assembling the same report manually, client by client, when I could have automated the whole thing.

My books on the other hand came from a different place. I've watched startups make the same mistakes - hiring too early, prioritizing new tech, ignoring their actual customers, building features nobody asked for. That pattern recognition had nowhere to go except in writing - my blog, article, and books. Books in particular are weird products. They don't scale the way software does, but they do scale better than a conversation but not as impactful.

My rule: if you've done it manually more than 4 times and the output looks the exact same each time, build a product. If the output depends on what you learn in the first two weeks with the client, you're still selling consulting.

## The awkward middle

If you're find yourself taking on consulting work because the product isn't generating real revenue yet, but the consulting work is eating the time you need to finish the product, you'll end up doing both badly. The product gets pushed because a client needs something urgent. The client work feels like a distraction because you're spending brain power on the product.

I've run both simultaneously for many times. The product keeps getting pushed. The client work stops being interesting. Stuck in the mud.

My stopping point hasn't really ever been clean. I set a revenue floor - the minimum monthly consulting revenue I needed to cover my fixed costs - and commit to throwing everything above that threshold to product work. Not on more clients. On the product. It's painful and slow, but it can work.

The revenue dip is legit. When you start pulling back on client hours to build the product, the consulting income drops before the product income shows up. There's a gap. Plan for it. If you don't have a few months of runway saved, you'll panic and scramble to take on more clients instead of finishing the product. I'm guilty of this, and have scrapped multiple products doing this exact thing.

## Pricing against yourself

If I charge $150 for consulting, and my product does 60% of what I'd do manually, what do I charge for the product?

The instinct is to price it at a fraction of your hourly rate - like a discount version of you. That's the wrong way to think about it. Your hourly rate includes your judgment, your availability, your ability to handle the weird edge case, your ability to see through ambiguity. The product handles the repeatable part, reliably, without you. Price it like a different thing.

Anchor it on the value of the output, not on what you'd charge to produce it manually. The SEO audit I was billing out at a few hundred dollars per client - the product version isn't priced at half that. It's priced based on what fixing those problems is worth to the buyer.

Some prospects could hire me directly or buy the product. I've had clients do both - buy the product first, then hire me when they hit the edge cases. When that happens on purpose, it makes decent funnel.

## Build the manual version first

The AI-search audit started as a Google Doc with a crawl report attached. The books started as blog posts and consulting advice I kept repeating. None of it started as code. I'm a programmer at heart, but still pragmatic.

I ran the audit manually for years before I wrote a line of automation. By the time I started building the tool, I already knew what the output needed to look like, which fields mattered, and which parts clients actually read. That's hard to figure out by guessing.

I've built things before I knew what I was building. Most founders do. You write code because it feels productive, even when you haven't proven anyone wants the thing. Running [the manual version](https://www.sethserver.com/startups/the-mvp-that-is-not-a-product.html) forces you to find out, because clients will tell you pretty fast if the output isn't worth their time. Ouch.

Consulting gives you an edge here. You're already in front of buyers. You're already getting feedback. The product is what you build after you've done it manually enough times to know what works.

## What doesn't productize

Strategy doesn't productize. Anything that depends on understanding the people first, or having a conversation you haven't had yet, or getting the client's buy-in as part of the deliverable.

People try to productize strategy. I've tried. It doesn't work. You can productize the research that feeds strategy. You can productize the audit that surfaces the problems. But the "here's what you should do about it" part - the part where you're looking someone in the eye and telling them their pricing model is broken - that's still a service. Probably always will be.

The goal isn't to replace the consulting. It's to stop billing hours for the parts that don't need you anymore.

-Sethers


```json
{"@context": "https://schema.org", "@type": "BlogPosting", "headline": "Productizing a Service: From Hours to Licenses", "datePublished": "2026-07-26T16:15:03", "dateModified": "2026-09-17T19:48:59", "image": {"@type": "ImageObject", "url": "https://cdn.sethserver.com/blog-images/productizing-a-service-from-hours-to-licenses-social.webp", "width": 400, "height": 400}, "url": "https://www.sethserver.com/startups/productizing-a-service-from-hours-to-licenses.html", "author": {"@type": "Person", "name": "Seth Black", "url": "https://www.linkedin.com/in/seth-black-tx"}, "publisher": {"@type": "Organization", "name": "Sethserver", "logo": {"@type": "ImageObject", "url": "https://www.sethserver.com/static/images/PaperAirplane512.png"}}, "description": "Learn how to identify which parts of your consulting work can become products and which can't. A practical guide to transitioning from billing hours to building scalable products, including pricing strategy, managing the revenue gap, and knowing when to automate versus when to stay hands-on.", "articleSection": "Business"}
{"@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [{"@type": "ListItem", "position": 1, "name": "sethserver", "item": "https://www.sethserver.com/"}, {"@type": "ListItem", "position": 2, "name": "Startups", "item": "https://www.sethserver.com/startups/"}, {"@type": "ListItem", "position": 3, "name": "Productizing a Service: From Hours to Licenses", "item": "https://www.sethserver.com/startups/productizing-a-service-from-hours-to-licenses.html"}]}
```
