LaunchBook
A booking proof of concept for local business owners to manage products or services, set availability, and share an appointment link with customers.
The work is paused. It remains here because the decision to stop was as important as the interaction work that made the booking flow usable.
What the proof of concept demonstrated
The PWA let a local business owner add products or services, schedule availability, and share a booking link. I tested a complete booking flow from the customer side without payment.
No business owners used the proof of concept, so this is not presented as a validated market or a launched service. It was a working product exploration.
Why I paused it
Payment was the next major step. The intended model was to operate as a payment provider and take a percentage of each transaction.
Before building that layer, I evaluated the economics, legal scope, and compliance obligations. Competitor pricing made the transaction-fee model unattractive, and the additional complexity was not justified by the revenue potential.
Stopping was a product decision. Continuing because the prototype worked would have meant investing in a business model I no longer believed was viable.
What I took from it
A build can be technically successful and still be the wrong product to pursue. LaunchBook reinforced the value of testing the product, operating model, and compliance implications together before treating implementation progress as a reason to keep going.