One paying SaaS customer: a worksheet for testing the business

Write the evidence without hiding the small numbers

Thanks to Dex for sponsoring this video.

Luke’s August account reports 142 signups and one customer paying $9 a month for Scripti. The customer’s continued use and positive review are encouraging, but they do not establish a repeatable business.

1. Record signups, paying customers and continued use as separate measures.
2. Write what the paying customer actually does with the product.
3. Separate direct customer feedback from your own assumptions about why people do not buy.

Find the basic task that still breaks

The video describes features taking attention while core issues remain unresolved. A new feature can feel productive without answering the reason a customer cannot finish the job.

1. Choose the main task a customer is paying to complete.
2. Follow that task through the current product and record any failure.
3. Prioritise a reproducible basic defect ahead of speculative additions.
4. Check the repair with the actual task rather than only a successful build.

Give the business question a real test

Luke distinguishes a failed product from a business that has not been prioritised or adequately tested. This is a historical account, not the current status of Scripti.

1. Choose one audience, promise and route for showing the product.
2. Define the observation that would support or challenge that choice.
3. Collect actual use and feedback before interpreting inactivity as rejection.
4. Review the result at a chosen point and decide which assumption to test next.

The takeaway

An appreciative customer is useful evidence about a specific job. Signups and unfinished marketing plans cannot substitute for testing how the next customer finds and uses the product.