Why I parked the tester programme and shipped 4 days ahead

What the plan was

Pack #2 of my Knack catalogue (Indie Hacker Launch, knack.run) shipped on day 3 of a 9-day plan. The decision that cut 4 days was parking the tester programme.

The week 2 sprint plan had a standard de-risking loop: build the skills on days 1-3, recruit 5 testers on day 4, gather feedback by day 7, soft-launch day 8, public-launch day 9. Week 2 was meant to be week 2, full 7 days, half of it spent waiting on people.

What I changed and why

On day 3, with the four skills built and five worked examples written, I asked: what is the tester loop actually catching?

The worked examples already run each skill against a real scenario (Product Hunt listing copy, weekly build-in-public posts, SEO foundation install, launch-day playbook) and print the full output. A buyer can read the example, see the deliverable, and decide if it matches the launch they need.

The tester loop adds two things: "did the install work on my machine" and "is the output worth £99 to me". The first is fine to defer (install scripts are tested clean in a throwaway dir). The second is buyer-signal, which is what Pack #2's actual sales over the next 6 weeks will tell me, faster than a tester batch.

What I'd do differently

Nothing yet. The bet is conditional. If Pack #2 sells (any non-self purchases by week 6), worked-examples-only goes into Pack #3. If it doesn't, the tester programme comes back in with the assumption that worked examples weren't sufficient signal.

What's live

Indie Hacker Launch, 4 skills, 5 worked examples, £99 lifetime. There's a free starter pack at knack.run if you want to see the format before paying.