Day 20: Package Your Knowledge Into a Productised Service or Digital Asset
The Concept
Every freelancer who has worked with multiple clients in the same field has built something that belongs to them and would be useful to others. A framework for structuring a particular type of project. A template that organises information clients always need but never know how to gather. A process for solving a problem that comes up in every engagement. A guide that answers the question clients ask repeatedly, each time requiring the same explanation delivered slightly differently.
This knowledge is not abstract. It is embedded in the actual work — in the documents produced, the systems built, the processes designed, and the hard-won judgment that comes from solving the same category of problem across many different contexts. Most freelancers never extract this knowledge into a form others can use independently. They deliver it as part of a client engagement, close the project, and carry it forward only as personal experience. The knowledge is not lost — but neither is it working.
Productising knowledge means extracting it from the one-to-one service context and repackaging it in a form that can be delivered without your direct time — a template, a guide, a course, a productised service with a fixed scope and fixed price, or a toolkit. The result is a new income stream that is not constrained by the number of hours in your week.
Why freelancers overestimate what a product needs to be
The most common reason freelancers never build a product is a gap between what they imagine a product should be and what actually sells. The product they imagine requires months of development, professional design, a full marketing campaign, and a large audience to launch to. They compare it to polished products they have purchased from established creators and conclude that the gap between where they are and where they need to be is too large to bridge without significant investment.
This comparison is a category error. The products that established creators sell today are the tenth version of something that started as a rough Google Doc shared with a handful of clients who found it useful. The minimum viable product — the simplest version of an idea that delivers real value to a specific buyer — is almost always smaller, simpler, and faster to create than the version that exists in the creator's imagination. A four-page PDF guide with a clear framework, well-structured and honestly priced, delivers more value to its buyer than a forty-page document padded with content included to justify a higher price.
The extraction question: what have you already built?
The most useful question when evaluating product opportunities is not "what could I create?" but "what have I already created for a client that another client needed independently?" If you have built a project management setup for three different clients, that setup is not just a client deliverable — it is a product that three separate buyers have already validated by paying you to build it for them. Packaging it for independent use requires cleaning up the implementation notes, writing brief guidance on how to use it, and deciding what to charge. It does not require inventing something new.
The product opportunity audit in today's output is designed to surface this already-existing material rather than generate new ideas from scratch. The most commercially credible first product is almost always something you have built before, not something you think the market might want.
Pricing a product when you have no reference point
Pricing a digital product is genuinely difficult the first time, because there is no billable hours framework to fall back on and no client negotiation to calibrate against. The most useful frame is buyer comparison: what is the buyer comparing this to when they decide whether it is worth the price? A template that saves a creative agency founder four hours of work is not compared to other templates — it is compared to four hours of a consultant's time. A guide that helps a freelancer write better proposals is not compared to other guides — it is compared to the revenue lost on proposals that did not convert.
Pricing from the buyer's alternative rather than from your production cost almost always produces a higher and more defensible number than pricing based on how long it took to make.
The small audience problem
Most freelancers who want to sell digital products do not have a large audience, and most advice about product launches assumes one. The five-step launch strategy in today's output is designed specifically for the freelancer with a small but warm professional network — past clients, former colleagues, referral partners, and professional contacts who already know the quality of your work. These people do not need to be convinced that you know what you are talking about. They need to be told that the thing exists and invited to buy it or share it with someone who would find it useful.
Ten buyers from a warm network is enough to validate a product idea, generate the first testimonials, and fund the small amount of further development the next version requires. That is the only threshold that matters at the start — not a launch event, not a marketing campaign, not a social media following. Ten people who found it useful and said so.
The knowledge you have accumulated across your freelance career is more commercially valuable than most freelancers recognise. Today is the day you begin to find out what it is worth to someone who is not yet a client.
Prompt of the day
Copy this into your AI tool and replace any bracketed placeholders.
Prompt
You are a product strategist who specialises in helping freelancers identify the knowledge embedded in their client work and package it into productised services, templates, guides, or digital assets that generate income beyond one-to-one client engagements. My situation: - My freelance specialism: [e.g. operations consulting for creative agencies] - The most common problems I solve for clients: [e.g. chaotic project management, unclear role responsibilities, poor utilisation tracking, and no onboarding process for new hires] - Questions clients ask me repeatedly that I answer the same way every time: [e.g. 'how should we structure our project management system?', 'what does a good creative brief look like?', 'how do we track utilisation without micromanaging?'] - Things I have built for one client that I could see being useful to many: [e.g. a project management setup in Notion, a role responsibility matrix, a utilisation tracking spreadsheet, and an agency onboarding guide] - My honest hesitation about creating a product: [e.g. I do not know what to charge, I am not sure anyone would buy it, and I worry it would take months to build something good enough to sell] Produce the following: 1. Product opportunity audit — based on what I have described, identify three viable product or productised service ideas, ranked by: ease of creation, likely demand from people like my clients, and potential price point. For each, describe what it is, who would buy it, what problem it solves, and one sentence on why it is commercially credible. 2. Minimum viable product design — for the highest-ranked opportunity, design the simplest version I could build and sell within two weeks. List exactly what it contains, what format it takes, and what it does not include in this first version. 3. Pricing rationale — suggest a price for the minimum viable product and explain the reasoning, including what the buyer is comparing it to when they decide whether it is worth it. 4. A sales page outline — the key sections of a simple sales page or Gumroad listing for this product: headline, the problem it solves, what is inside, who it is for, who it is not for, and the call to action. 5. A launch strategy for someone with a small audience — a realistic sequence of five steps to get the first ten buyers without needing a large following, a marketing budget, or a launch event.
Your 15-minute task
Fill in all five fields honestly — particularly the 'honest hesitation' field. The hesitation you describe is what separates the freelancers who build products from the ones who think about it for years. Run the prompt. Read the product opportunity audit and identify which of the three ideas you have already, in some form, built for a client. That is your starting point — not a new idea, but an existing piece of work that needs packaging, not inventing. Read the minimum viable product design and ask yourself: could I build this in two weekends? If yes, that is the version to start with. Save the sales page outline to a new document titled with the product name.
Expected win
A ranked audit of three viable product ideas rooted in your existing client work, a minimum viable product design you could build within two weeks, a pricing rationale, a sales page outline, and a five-step launch plan that does not require a large audience — so productising your knowledge moves from a vague aspiration to a specific, scoped, executable project with a starting point you already have.
Power user tip
The fastest path to a first product sale is not building the product first — it is validating the idea before you build anything. After completing today's exercise, send this prompt: 'Write me a short validation message I can send to five past clients or professional contacts who match the buyer profile for my product idea. The message should: describe the problem the product solves in one sentence, ask whether they have experienced that problem, and offer them early access at a reduced price in exchange for honest feedback. Keep it under 100 words and make it feel like a genuine question, not a sales pitch.' Five validation messages sent today will tell you more about whether your product idea is commercially viable than six months of building in private — and the first person who says yes has already paid for a portion of your development time.