Offer Kill Switch Playbook — 24 Decision Rules for Retiring or Reworking Digital Products

The quiet cost of keeping every offer

Most tiny shops keep weak offers alive because deleting them feels like waste. The real waste is attention leak: every stale product asks for support, screenshots, descriptions, price decisions, and emotional defence. This playbook gives you a repeatable way to decide whether an offer should stay live, be repaired, be bundled, be archived, or be replaced. Use it once a month or whenever the catalog starts feeling noisy.

The five possible decisions

Every offer leaves the review with one of five outcomes: Keep, Improve, Bundle, Park, or Kill. Keep means the page is clear and the product still earns its shelf space. Improve means one focused change could unlock sales or reduce confusion. Bundle means the product is useful but too narrow alone. Park means it is not a priority now but has strategic evidence. Kill means remove it from promotion, archive the files, and stop pretending it belongs in the active shop.

Your evidence board

Score each offer using buyer signal, support burden, strategic fit, freshness, and repair cost. Do not use vibes alone. Buyer signal includes sales, wishlists, direct questions, clicks, or repeatable search intent. Support burden includes refund requests, unclear downloads, too many explanation messages, or page confusion. Strategic fit means the product helps the shop identity become clearer. Freshness asks whether the promise still matches current buyer problems. Repair cost asks how many focused hours are needed to make it respectable.

The 24 decision rules

The rules are deliberately blunt. If a product has zero signal after three clear traffic attempts, kill or bundle it. If buyers ask the same pre-sale question twice, improve the page before sending more traffic. If the product requires a personal explanation to sound useful, rewrite the angle. If it competes with a stronger product you already sell, bundle or retire the weaker one. If support takes longer than creation did, park it until the delivery is simplified. If the promise makes you cringe, kill it kindly and document the lesson.

Repair sprints that do not sprawl

An improve decision gets one sprint only: page clarity, deliverable upgrade, visual refresh, price test, or onboarding fix. Pick the highest leverage repair and define the done line before opening files. A repair sprint should produce a visible buyer-facing change in under two hours for a tiny product. If the fix wants a full rebuild, treat it as a new product and park the old one.

Bundling without making junk drawers

Bundle products around one buyer moment, not around your leftovers. A good bundle has a clear job: launch a shop, manage a client, teach a week of lessons, plan a family routine. A bad bundle is just a discount pile. When bundling, write a new quick-start guide that tells the buyer which file to open first and what sequence to follow.

The clean archive ritual

Killing an offer is operational hygiene, not failure. Save the product folder, final listing copy, cancellation reason, last metrics snapshot, and reusable parts. Remove it from homepage promotion, update internal product status, and add the lesson to your next product brief. The goal is not to erase work; it is to stop spending attention on work that no longer serves the shop.

Monthly catalog review template

Review no more than ten products at a time. Start with the oldest, lowest-signal, or highest-support items. For each one, assign an outcome, one reason, one next action, and a review date. The review should end with fewer open questions, not a giant improvement backlog. A healthy tiny shop has living products, clear parked ideas, and clean archives.

The 24 decision rules

1. Rule 1. No traffic and no direct buyer questions after three honest promotion attempts → Kill or Bundle.
2. Rule 2. Two repeated pre-sale questions → Improve the page before promoting again.
3. Rule 3. A product that needs verbal explanation → Rewrite the promise or Park it.
4. Rule 4. Weak product overlaps a stronger one → Bundle under the stronger buyer outcome.
5. Rule 5. More support time than creation time → Simplify delivery or Park.
6. Rule 6. Outdated screenshots or claims → Improve within one sprint or Park.
7. Rule 7. Low price but high complexity → Raise price, simplify, or Kill.
8. Rule 8. Good file, bad angle → Improve title/subtitle before rebuilding.
9. Rule 9. Good angle, thin file → Improve deliverable before promotion.
10. Rule 10. One sale with warm praise → Keep and improve onboarding.
11. Rule 11. One sale with confusion → Improve quick-start immediately.
12. Rule 12. Refund caused by mismatch → Rewrite promise before traffic.
13. Rule 13. Refund caused by file access → Fix delivery before anything else.
14. Rule 14. Product teaches a skill your shop no longer stands for → Park or Kill.
15. Rule 15. Product could become a bonus in a stronger system → Bundle.
16. Rule 16. Product has seasonal relevance only → Park with calendar reminder.
17. Rule 17. Product has evergreen buyer pain but weak execution → Improve.
18. Rule 18. Product is mostly a duplicate → Keep one, retire the rest.
19. Rule 19. Product creates brand embarrassment → Kill kindly.
20. Rule 20. Product attracts wrong-fit buyers → Rewrite targeting or Kill.
21. Rule 21. Product depends on unverified claims → Remove claim or Park.
22. Rule 22. Product can be repaired in under two hours → Improve.
23. Rule 23. Product requires a full rebuild → Treat as new product; Park old one.
24. Rule 24. Product still clarifies the shop identity → Keep, even if small, if burden is low.

One-page review worksheet

Product name · Buyer signal · Support burden · Strategic fit · Freshness risk · Repair cost · Decision · One next action · Review date.