Chapter 2
Define scope as a product
Finish this chapter with a productized scope table you can use immediately to define scope as a product, while avoiding accepting undefined work that destroys margin and delivery quality.
What you’ll get
- A completed productized scope table, not a list of abstract ideas.
- One explicit decision rule for define scope as a product.
- A 45-minute execution sequence you can repeat yourself or hand to a teammate.
- A quality gate that tells you whether to move forward, run one small test, or revise the input.
Use this chapter as a working session
Open the document, spreadsheet, or Tapmy workspace where this decision will live. Replace sample language with the exact offer, buyer, channel, price, and evidence you have today. If a fact is missing, label it as an assumption and assign the smallest test that can resolve it.
| Time | Work | Concrete output |
|---|---|---|
| 0–10 min | Collect buyer words, traffic data, sales conversations, support questions, and current page copy. | A short evidence list with source and date. |
| 10–20 min | Make the single decision this chapter is designed to resolve. | A one-sentence decision and reason. |
| 20–35 min | Build the productized scope table with real names, numbers, links, and owners. | A usable operating asset. |
| 35–45 min | Review it from the buyer’s point of view and run the quality gate. | A keep, test, or revise decision. |
Specify what the client receives
Include quantities, formats, dimensions, platforms, revision rounds, usage rights or licensing terms where applicable, delivery method, and handoff documentation.
Specify what the client provides
List required copy, brand assets, account access, examples, approvals, and deadlines. Explain what happens when inputs are late or incomplete.
Define exclusions
Common exclusions include strategy, copywriting, source files, extra formats, posting, paid media management, stock/licensing costs, rush delivery, and ongoing support—unless included.
Create a scope table
| Scope item | Included | Optional add-on | Not included |
|---|---|---|---|
| Strategy kickoff | 45-minute session | Additional stakeholder session | Full brand strategy |
| Deliverables | 5 edited short-form videos | Additional video pack | Long-form editing |
| Revisions | 1 consolidated round | Extra revision round | Unlimited revisions |
| Delivery | Final MP4 files | Caption-file package | Publishing to client accounts |
| Timeline | 10 business days after inputs | Approved rush option | Work before required assets arrive |
Exact terms belong in the agreement too; the sales page should make the commercial shape understandable.
Decision gates
| Evidence state | What it means | What to do next |
|---|---|---|
| The input is specific, current, and tied to a real buyer action | The productized scope table is ready to use. | Put it into the Tapmy journey and measure the next observable behavior. |
| One important input is assumed | The direction is testable, not yet proven. | Run the smallest test that can confirm or reject that assumption. |
| The asset serves several audiences, offers, or goals | The scope is too broad. | Narrow to one buyer, one job, one offer, and one reporting window. |
| The result depends on a claim you cannot show or deliver | Trust and delivery risk are higher than the upside. | Rewrite the promise around a supportable outcome. |
Quality standard
- The productized scope table names one buyer and one job.
- Every number has a timeframe, currency, or denominator where needed.
- Every link and handoff has an owner.
- The next action is visible without rereading the chapter.
- The decision can be measured through customer behavior.
- No claim is stronger than the evidence.
