Chapter 3
Create the instruction layer
Turn create the instruction layer into a buyer-ready workflow asset in 45–60 minutes, with a concrete output and a testable completion condition—without making a blank asset that transfers the difficult decisions back to the buyer.
What you’ll get
- Primary decision: Build a start-here page.
- Working asset: Include one full worked example.
- Quality check: State permissions and limitations.
Before you begin
Bring the current workflow, the inputs a buyer has at the start, and one finished example. Set a 45–60 minutes timer. Every field and instruction must help the buyer decide, do, check, or finish something.
| Workflow decision | Buyer input | Completion signal | Next action |
|---|---|---|---|
| Create the instruction layer | The real information available at the moment of use | A finished output the buyer can recognize | Test from a fresh copy |
Conversion checkpoint
Templates sell when the buyer can see the finished result, the time or risk saved, and the level of support included. Show the product in use; do not rely on screenshots of empty grids or folders.
Build a start-here page
Explain:
- What the product helps complete
- Who it is and is not for
- What software or account is required
- How to copy, download, or open the files
- Which asset to use first
- What a finished output looks like
- Where to get support
Include one full worked example
Use fictional or permissioned information. Complete the product exactly as a buyer should, then annotate key decisions. An example should teach adaptation, not encourage blind copying.
State permissions and limitations
Define whether the buyer can edit, duplicate, use in client work, or share within a team. State restrictions on resale, redistribution, or sublicensing. Make software compatibility and third-party requirements explicit.
Write instructions around failure points
Build the instruction layer in the order a buyer encounters risk. Start with the finished outcome, required inputs, software or access requirements, and the first action. Then show one completed example beside the blank asset so the buyer can compare work in progress with “done.” Add troubleshooting only for failures observed in testing: missing data, wrong format, permissions, formulas, or unclear field definitions. State what the buyer may copy, edit, or share. The instruction layer should prevent predictable mistakes without becoming a second product. If a note does not change an action or recover from a failure, move it out of the quick-start path.
Finish line
- The job and starting inputs are explicit.
- Hidden decisions are represented by fields, checks, or examples.
- A completed version shows what good looks like.
- Compatibility, permissions, and limitations are visible.
