Make the Product
This step is the build. You take the one-sentence promise from the last step and turn it into a finished product: a file a buyer can open, or, for a course or membership, the first complete set of material.
Why it matters
Every step after this one needs a real thing to point at. The price is set against what the product does, not what you planned. The shop delivers a specific file or opens a specific space. None of that can be set up against a draft.
Skip the discipline, and the cost is a product that is never quite done. The most common failure is scope: the outline grows with every evening until the finish line moves out of reach. The next is ownership discovered late: a borrowed image or a form from work that has to come out after the product is built around it.
What actually happens
Outline from the promise
Start with the sentence you tested. Its three parts, who it is for, what it fixes, and what they get, are the whole scope. Write an outline in which every section serves one of them. Anything that does not is cut, or saved on a separate list for a later product.
Priya’s promise was a checklist and form set that gets a first hire’s paperwork right the first time. Her outline is the paperwork, in the order a supervisor meets it, with one form. The section on managing a first month is useful, and it goes on the later list.
Build with what you already use
A first product needs no new tools. A word processor, a spreadsheet, a slide tool, and a phone camera cover ebooks, workbooks, templates, and most course material. New software adds weeks to a build that should take a few.
The deliverable is the thing that changes hands. For a downloadable product, it is a file type a buyer can open without buying anything else: a PDF, a spreadsheet, a document. For a course or membership, it is the first complete set of material plus a written schedule for what follows.
Keep the rights list as you go
Every piece that is not yours goes on a list as you add it: an image, a font, a quote, a diagram, a form you adapted from work. For each one, write where it came from and what right you have to use it. If you cannot name the right, the piece comes out now, while replacing it is cheap. The law behind the list lives in Copyright and Licensing; at this step you only keep the list.
Priya’s list has two entries: a form layout adapted from a public agency template, and the icon set that came with her word processor. Her employer’s onboarding packet is not on the list, because none of it went in.
Test it on two or three people
Give the draft to two or three of the people who said the promise described their problem. Watch them use it, or ask them to note where they stopped. Where they stalled is what you fix. Do not fix everything they mention; fix what stopped them from getting the result the promise names, and leave the rest for a later version.
Priya sends her checklist to two supervisors. Both stall at the same item, an approval that needs a signature nobody told them about. She adds one line naming who signs. One asks for more on a form the list already covers; that goes on the later list.
Finish it
A finished product has four things. A final file with a plain name and a version number, so a buyer can tell it from what comes next. A short plain description of what is inside. A decision about what a buyer may do with it: use it themselves, share it with their team, resell it. And a check against the promise, part by part.
That third decision is the license you sell under. What a license is belongs to Copyright and Licensing. Where it is written down for the buyer belongs to Terms, Refunds, and Privacy. Priya decides a buyer may use the checklist for their own team and may not resell it, and she puts that sentence on the last page.
Finished does not mean perfect. It means you would be willing to take money for it today.
Questions to ask yourself
- Does every section of the outline serve the promise, and where did the rest go?
- Can the buyer open the deliverable with nothing they have to buy first?
- Is there a list of every borrowed piece, with its source and the right you hold?
- Would you take money for this file today?
Common mistakes
- Building the flagship instead of the first product; the outline grows and the finish line moves.
- Learning new software for a first product; weeks go to tooling instead of the work.
- Leaving the rights list for later; a borrowed piece is cheap to replace now and costly after launch.
- Fixing everything the test readers mention; the product drifts from its promise toward their wish lists.
Which business areas apply
- Copyright and Licensing: The rights list and the license decision are made here, while the product is being built.
- Terms, Refunds, and Privacy: What the buyer may do with the product is decided here and written into the terms later.
- Marketing Claims and Disclosures: The description you write at the finish is the first draft of the sales page, so it has to match what is inside.
For practitioners
A refresh is a build with a starting point. Give the new file a version number and keep a short note of what changed, so a support question can be matched to what the buyer holds. If you made products before you kept a rights list, build one now for each; a borrowed piece is easier to replace on your schedule than on a rights holder’s. Then read the sales page as it stands today and check the product against it, because the promise on the page can drift from what the file delivers.
Next step
Set the Price: Put a number on the product, and learn what part of that number reaches you.