One-Person Business

Productize Consulting Expertise: From 80 Clients to 22 Playbooks

How to turn repeated consulting work into operating manuals, templates, and a knowledge product without removing the judgment clients still need.

Updated 2026-11-22

To productize consulting expertise, identify questions that recur across real engagements, convert proven decisions into specific actions and templates, let clients use them, and revise the material from observed friction. Standardize the repeated layer while keeping context-specific judgment in the advisory service.

Evidence note: client counts, document counts, sales, and project outcomes are Iris Wei's first-party, self-reported account. They are not universal benchmarks, and third-party outcomes cannot be attributed to one playbook alone. Client-identifying details are omitted.

Productize Consulting Expertise: From 80 Clients to 22 Playbooks

A woman I had added on WeChat six or seven years earlier suddenly contacted me. She studies astrophysics and was trying to turn that expertise into an industry product. After reading my posts for a long time, she wanted a paid consultation.

The message made me pause. We had barely spoken when we first connected. A dormant relationship had become relevant years later because the work I published made it clear what I could now help with.

This is not an article about acquisition tactics. It is about the layer underneath: once you have delivered enough one-to-one work, how do you turn the repeated parts into something other people can use without you in the room?

One-to-one work comes first

After leaving AFFiNE in May 2024, I spent months talking with companies. Some conversations began as job exploration and became requests for advisory help. Later, I ran both ongoing company advisory work and individual sessions.

By October 2026, I had worked with more than 80 companies in some capacity. That number is self-reported and covers different depths of work. It does not mean every company received the same engagement or result.

The useful pattern was repetition. Clients kept asking how to launch an open-source product, plan Product Hunt, find early users, evaluate competitors, negotiate creators, and package a service.

By the fifth explanation I still enjoyed the conversation. By the thirtieth, I understood that refusing to document it would keep the business trapped in one-to-one repetition.

The three stages of productizing experience

Stage one: internal notes. Record the question, context, answer, action, and what happened. These notes can be messy. Their purpose is evidence, not publication.

Stage two: client execution tools. Turn repeated decisions into checklists, timelines, worksheets, and templates that a client can use during delivery. If a step cannot be acted on, it is still advice—not an operating manual.

Stage three: an independent knowledge product. Consolidate the material, add missing context, define who it is for, remove client-confidential detail, and make the package usable without a live explanation.

My own library eventually reached 22 guides. That inventory grew through repeated projects; it was not designed in one sitting.

LayerPrimary userOutputValidation
Internal notesConsultantDecisions and outcomesCan I find the evidence later?
Delivery toolsCurrent clientChecklist, template, timelineCan the client execute it?
Knowledge productIndependent buyerStructured manual and examplesCan they use it without a call?
Advisory serviceContext-specific clientJudgment and adaptationDoes it fit this situation?

Three mistakes I made

The first was trying to cover everything. The result was a large collection of half-finished documents. I improved the system by completing the five questions clients asked most often before expanding.

The second was writing abstract advice. “Find the right channel and create high-converting content” sounds reasonable but cannot be executed. An operating manual needs the next observable action, the required input, and a way to tell whether the step is complete.

The third was treating pricing as a one-time theoretical decision. I started with a small material pack and raised the price as the scope, evidence, and usability changed. Those sales are my own history, not a pricing benchmark for another consultant.

The guide on consulting pricing strategy explains how I think about that decision without pretending one formula fits everyone.

The product and the service strengthen each other

A manual can answer the repeated question. Advisory work handles the exception: “This step does not fit our buyer, team, or product—what should we do instead?”

The knowledge product creates shared language before the call. The call produces new edge cases. Those cases improve the manual after permission and evidence checks. That is the real flywheel.

Productizing expertise does not mean making consulting generic. It means documenting the stable layer so human judgment can be spent where it is actually needed. If you want to design that boundary for your own service, review Gingiris advisory services.

Frequently asked questions

When should a consultant create a knowledge product?

When several real clients ask the same question and you have tested actions, templates, and boundaries from delivery—not merely an idea for a course.

Should a consultant build the complete system first?

No. Start with three to five frequent, well-supported problems, deliver the material, collect friction, and expand from evidence.

How is an operating manual different from a course?

An operating manual emphasizes inputs, steps, templates, acceptance checks, and limits. A course may teach concepts without being directly usable in delivery.

Will a knowledge product reduce consulting demand?

Not necessarily. It can remove repetitive explanation and create shared language, while complex situations still require judgment. Verify the effect with actual source and conversion data.