Cameo validated demand before it built the app

In this 2019 Bytes Over Bagels interview, Cameo co-founder Steven Galanis describes an early lesson that is easy to say and hard to practise: validate the customer outcome before investing in the finished product.

A useful first version is allowed to be manual

Cameo’s earliest website was deliberately small. A customer entered who the video was for, their email, the requested message, and a price. The team then contacted talent manually and had the video returned by email. Galanis says they completed more than 10,000 Cameos before building the creator app.

That approach made the earliest product less elegant, but more informative. It allowed the team to learn whether someone would actually pay for a personalised video, what talent needed to fulfil the request, and which parts of the interaction required software.

Early failure produced the signal

The team’s first attempted sale exposed a broken payment flow. A parent still found them via Twitter because the request mattered: a birthday video from his daughter’s favourite player. The delivery was late and imperfect, but the daughter’s recorded reaction showed the founders the emotional value of the outcome.

The lesson is not to romanticise poor execution. It is to identify the smallest honest version of the customer promise, then learn from a real purchase attempt. A polished app would not have answered those questions faster.

What founders can take from it

• Design the first version around the valuable outcome, not the final interface.
• Keep manual work where it teaches you what to automate.
• Treat failed checkout, fulfilment, and delivery moments as product research—not just bugs.

This is an interpretation of a 2019 conversation. Cameo’s product and scale may have changed since the recording.