Course resource
Productization Roadmap
Moving from selling your hours to selling something that does not require them.
The spectrum
Hours -> Packaged service -> Productised service -> Product
| Stage | You sell | Income scales with | Risk |
|---|---|---|---|
| Hours | Your time | Hours worked | Income stops when you do |
| Packaged service | A fixed-scope outcome | Efficiency | Scope creep |
| Productised service | A repeatable process others can deliver | Team | Quality control |
| Product | A thing people buy without you | Distribution | Building the wrong thing |
Move one step at a time. People try to jump from hours to product, build something nobody wants, and conclude products do not work. The intermediate steps are where you learn what to build.
Step 1: hours to packaged
The move: stop quoting time, start quoting outcomes.
You are ready when you have delivered the same kind of work three times and know roughly how long it takes.
Here is work I have delivered three times: [DESCRIBE EACH]
1. What is the same across all three?
2. What varied, and did the variation matter to the client?
3. What could be a fixed scope with a fixed price?
4. What should be explicitly excluded to make that safe?
5. What is the outcome, stated in the client's terms?
Price on the value of the outcome, not on your hours. If you get faster, you keep the difference — which is the entire point of the move.
Step 2: packaged to productised
The move: make it deliverable by someone who is not you.
You are ready when you have delivered the packaged version five or more times and the process is stable.
What this requires:
- A written process, step by step
- Templates for every deliverable
- A defined intake — what you need from the client before starting
- Quality checks that do not depend on your judgement
- A price that works when someone else does the work
The bottleneck is almost always quality checks that do not depend on your judgement. Making your taste explicit is genuinely hard, and it is the real work of this step.
Step 3: productised to product
The move: remove yourself from delivery entirely.
Shapes that work, easiest first:
| Shape | Effort | Notes |
|---|---|---|
| Templates / prompt packs | Low | Low price, needs an audience |
| A course | High | Recurring revenue, high maintenance |
| A tool or template system | Medium | If you built it for clients, others want it |
| Software | Very high | A different business; do not drift into it accidentally |
The honest warning: products need distribution. A good product with no audience earns nothing. If you do not have an audience, the product is not your next step — the audience is.
The prioritisation matrix
When you have several ideas:
| Idea | Demand evidence | Build effort | I can deliver it | Recurring? | Score |
|---|---|---|---|---|---|
Score each 1–5. Demand evidence carries double weight — it is the factor that decides, and it is the one people fudge.
"Demand evidence" means: people have asked you for this, or paid for something similar, or you have a waiting list. Not "I think people would want this".
The validation test
Before building anything:
- At least five people have asked me for this unprompted
- At least one has paid for a bespoke version
- I can describe the buyer specifically, not as a category
- I know what they currently do instead
- I can reach them without paid advertising
- I would use it myself
If fewer than four are true, do not build it yet. Sell the bespoke version once more and learn something instead.
The order that works
- Deliver it bespoke, several times
- Package it — fixed scope, fixed price
- Document it so someone else could deliver it
- Sell the documentation, or hire someone to deliver it
- Only then consider a product
Each step is funded by the one before, and each teaches you what the next should be.
Your roadmap
| Current stage | |
| Next step | |
| Evidence I am ready | |
| What I need to build | |
| Timeline | |
| How I will know it worked |
The trap
Productising feels like progress because it is building rather than selling. It is very easy to spend three months making something repeatable that nobody was asking for repeatedly.
The test: am I doing this because clients keep asking for the same thing, or because I would rather build than sell?
Be honest. The second answer is extremely common and it is how most of these projects end.