Test service demand before building another SaaS feature

Separate the observation from the conclusion

Thanks to Omnisend for sponsoring this video.

Luke reports $54 from more than 100 hours of SaaS work and a $100 one-hour consulting call followed by another booking. Those are historical results from one person, not a general earnings comparison.

1. List the actual enquiries you have received and the problems people describe.
2. Separate a paid engagement, a warm lead and a compliment.
3. Write down what the first customer needed, what you delivered and what remained unresolved.

Try a small service experiment

The video proposes pausing unpaid product work for a 30-day test. Treat that as Luke’s recorded experiment, rather than a promise that consulting will work for another business.

1. Choose one concrete problem you are able to help solve.
2. Define the deliverable and the evidence you will collect from the engagement.
3. Record time spent on preparation, delivery and follow-up, not just the call itself.
4. Follow up on actual demand rather than replacing it with another speculative feature list.

Look for a repeatable problem

The Omnisend segment covers follow-up automation; the central lesson is to notice demand before deciding whether to productise it.

1. Compare the problems across completed conversations.
2. Identify what repeats and what is unique to one customer.
3. Review whether the service is useful and sustainable before turning its steps into software.
4. Keep the observations from the experiment separate from future revenue projections.

The takeaway

One paying client is evidence of one solved problem. It does not by itself establish a consulting business or a repeatable SaaS opportunity.