Chapter 7
Deliver control changes and invite the next step
Finish this chapter with a kickoff change-request and closeout playbook you can use immediately to deliver, control changes, and invite the next step, while avoiding accepting undefined work that destroys margin and delivery quality.
What you’ll get
- A completed kickoff change-request and closeout playbook, not a list of abstract ideas.
- One explicit decision rule for deliver, control changes, and invite the next step.
- 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 kickoff change-request and closeout playbook 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. |
Run a kickoff against the agreed scope
Confirm deliverables, roles, deadlines, review method, and communication channel. Resolve contradictions before production starts.
Use a change process
When a request falls outside scope:
- acknowledge the request;
- explain the scope difference;
- state impact on price and timing;
- obtain written approval;
- update the plan before starting.
Close the project clearly
Deliver the files, usage instructions, access transfer, and remaining responsibilities. Ask for focused feedback after the client can assess the work. Offer the next service only when it matches the next job—maintenance, another batch, implementation, or a retainer.
Decision gates
| Evidence state | What it means | What to do next |
|---|---|---|
| The input is specific, current, and tied to a real buyer action | The kickoff change-request and closeout playbook 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 kickoff change-request and closeout playbook 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.
