Skip to Content
ToolsBuild Checklist

Build Checklist

This checklist belongs to Make the Product, the second step of The Launch Path. It follows the build in the order that step describes, from the outline to the moment you would take money for the file. Tick each item only when it is done, not when it is planned.

How to use it

Print it or copy it into your own notes and check items off as you finish them. Every number you write is your own: sections, pages, test readers, days. Any number set by law, an agency, or a platform lives on this year’s figures, and this page links to it where one comes up.

Outline

The outline is the promise, expanded. Every section serves one of its three parts, and anything else goes on a later list.

  • Copy the tested promise to the top of the outline.
  • List the sections in the order the buyer meets the problem.
  • Mark which part of the promise each section serves.
  • Move every section that serves none of them to a later-products list.
  • Set a finish date that fits your hours, and cut the outline until it does.

Example: Priya’s outline is the paperwork in the order a supervisor meets it, with one form; the section on a first month goes on the later list.

Drafts

  • Build in tools you already use rather than learning new software.
  • Write a full rough draft before polishing any section.
  • Start a rights list, and add every piece that is not yours as you add it: an image, a font, a quote, a diagram, an adapted form.
  • Write beside each entry where it came from and what right you hold to use it.
  • Remove any piece whose right you cannot name, while replacing it is cheap.
  • Decide what a buyer may do with the product: use it, share it with a team, or resell it.

Example: Priya’s rights list has two entries, a form layout adapted from a public agency template and the icon set that came with her word processor.

Review pass

  • Give the draft to two or three people who said the promise described their problem.
  • Ask them to note where they stopped, or watch them use it.
  • Fix what stopped them from getting the result the promise names.
  • Put every other suggestion on the later list.
  • Check the finished draft against the promise, part by part.
  • Write a short plain description of what is inside.

Example: Both of Priya’s test readers stall at an approval that needs a signature, so she adds one line naming who signs.

File formats

The deliverable is the thing that changes hands. A buyer must be able to open it without buying anything else.

  • Export the final file in a type a buyer can open with free or common software.
  • Name the file plainly, with a version number.
  • Open the exported file on a phone and on a computer you did not build it on.
  • Put the license sentence, what the buyer may and may not do, inside the file.
  • For a course or membership, finish the first complete set of material and write the schedule for what follows.

Example: Priya’s file is a single document named with its version, and its last page says a buyer may use the checklist for their own team and may not resell it.

Test download or access

  • Send the final file to yourself and open it from the email, not from your working folder.
  • For an access product, log in as a new member and reach the first lesson or post.
  • Confirm the version number inside the file matches the file name.
  • Ask whether you would take money for this today, and stop building when the answer is yes.

Business Side

  • Copyright and Licensing: The rights list and the license decision are made while the product is built, and a piece with no right behind it comes out now.
  • Terms, Refunds, and Privacy: What the buyer may do with the product is settled here and becomes a term of sale later.
  • Marketing Claims and Disclosures: The description you write at the finish becomes the sales page, so it must match what the buyer receives.