☠️ 30%+ of startups fail due to lack of product-market fit. In this eBook, you'll learn how to avoid it. Only $10 for a limited time.
Tzelon and Ron are two developers who came with an idea: creating a tool that allowed Twitch streamers analyze their streams and creating short videos with the best moments. But they failed to build an audience around the product and couldn’t get any customers to keep going with the project.
February 2, 2019
Sponsor Failory and get your business & product in front of +20,000 CEOs, startup founders, entrepreneurs, developers and marketers every month.
Do you want to grow your business? With GenM you can get free marketing from an apprentice as part of their training. The student will work 40 hours per month creating content, increasing SEO rankings, carrying out advertisement campaigns...
Want to take ownership over the growth of your business, but don't know where to start? Get 1-on-1 advice from vetted growth experts about your business.
Hire pre-vetted, remote talent and pay them while complying to local laws. Check how it works!
No more changing developers every time you start a new project. With our full range of development services, no project is too big, too complex, too mobile or too software for us to complete. We’re the only web-dev partner you’ll ever need.
A 5-minute read that's informative, witty and free? That's Morning Brew — the daily email that delivers the latest news from Wall Street to Silicon Valley.
Hey, I’m Tzelon, a 30-years-old, frontend developer and maker from Israel.
Though at the moment I’m doing research on the question “How to launch a product as a Maker?” I’m learning about the process one should go through before launching a product. From building an audience to what to do after the launch. With that knowledge, I’m creating a tool for Makers, to guide them through the process. You can check it out at CreateCamp.co.
Hi, I’m Ron, 30-year-old software developer, studied computer science at the IDC Israel, an addicted podcast listener and an amateur poker player.
Tzelon and I are friends since we were 6-year-old, we share the same passion for creating our own things, over the years we have started many projects and abandoned them soon after. We always waited for the “right time” to take a leap of faith and work on something full time, until Twitch Highlights.
What was Twitch Highlights?
Twitch.tv is a live streaming platform focused on video game live streaming, the streams are interactive as the streamer talk to the viewers and they can chat with him.
The average length of a stream is ~8 Hours. That's very long… most of the viewers don’t watch the entire stream. But what if the most interesting\entertaining part of the stream happens when you are not watching?
This is where Twitch Highlights kicks in, we analyzed the stream and created a short video with only the most interesting and entertaining parts of it.
As enthusiastic Twitch viewers with families and a full-time job as developers, we couldn’t watch all the full streams as they are very long (~8 Hours), but we didn’t want to miss it entirely, so we took inspiration from sports, mostly NBA.
Shortly after each NBA game a highlights video with the most interesting moments of the game was available on the NBA website.
We have tried to build many things over the years and we thought that we need to go “all-in” on Twitch Highlights for it to succeed. We quit our jobs and start working on it every day.
Our business model was simple, streamers will use Twitch Highlights in order to generate highlights videos out of their raw streams, and by doing so they will increase their overall viewers number. The equation was pretty clear to us, as a streamer “more viewers” = “more revenue” so as long as we will help the streamers make more money they will be willing to pay for Twitch Highlights monthly subscription.
Hire pre-vetted, background verified candidates who have experience working at top companies like Google, Amazon, TCS, IBM, Microsoft and the likes
We knew it’s important to validate our idea before jumping into coding. We followed the “The Lean Product Playbook”, we create personas with their struggles and needs.
We work to refine the feature list that we will build to our MVP, we also created a landing page and sent cold emails to professional streamers. We got few responses from streamers who recognize the problem from their daily routine, and a lot of silence from others.
Taking all we learn from that week, we jumped right into coding, using Computer Vision algorithms and OCR to detect objects and text on the video, setting up our environment on Amazon servers and Lambda functions.
We worked on it for three months, writing code and nothing else. We loved it! We had no knowledge in Computer Vision so we needed to learn it from scratch. We use Node.js and found a great open source library for Computer Vision, Opencv4nodejs, the owner of the library was very helpful and kind, thanks Vincent Mühler. He helped us get started and after a few weeks, we were able to analyze a video stream from different perspectives. First, we tried to figure out what is currently happening in the game so we started to look for text messages that were displayed in the game such as “Victory Royale” in Fortnite, this way we knew that we have detected an interesting message, the streamer won the game.
Another perspective was looking at the messages frequency at Twitch.tv chat, we figured out that when there is an anomaly in the average messages per second, something interesting might have happened and the viewers are going crazy.
So by combining those and some other “secret” indicators, we have figured out pretty well what are the interesting moments and extract them.
We still had a long way ahead of us, but we minimize editing time of a stream from ~12 hours to ~4 hours!
Three months in, we wanted to get some beta testers, but we failed to make connections in the streamers world. The streamers who were willing to talk to us before didn’t answer our emails now, and it was hard to find professional streamers to try our product in other social networks. It was our first obvious failure.
We failed to understand how important it is to have marketing strategies and build an audience around Twitch Highlights.
Yes, we tried sending cold emails, post on forums and Reddit. But it’s hard to get anyone attention this way for a brand new product when no one knows you.
We failed to build an audience around Twitch Highlights. After we couldn’t find any beta testers it’s was hard to continue, our motivation and momentum were declining fast, very fast! There was no one to give us feedback on our work and tell us it was useful for them. If you can’t help others with your product you have no energy to work on it.
Instead of confronting with our real problem, we tried to improve Twitch Highlights by adding more features, classic mistake. It’s didn’t took long until we realized we fail to execute on our idea, we run out of money and with no potential users on the horizon we had to go back to work.
Some numbers, we live in Israel so with were burning about 2500$ a month from our savings just to put food on our table and rent an apartment (We are both married).
We spend about $500 on AWS servers and lambda. And we worked on it for about 8 months.
I definitely would work very hard on building an audience around Twitch Highlights, and my personal online presence before I quit my job. I always thought that be 100% on something will guarantee its success, but I now think we should as makers, first build a platform on which we could build our products, and building this platform takes time, months even years, it includes knowing who we want to serve, get involved with that community, building our reputation with them and really live with them. I'm here to run a marathon, not a sprint.
I would have spent more time on networking and building a community around the problem first, before going after the solution. We have started working on the product without gathering enough “intel” from our audience and actually make sure that it is a real pain for them and they do see the value of our solution.
Because we are developers the easiest part for us is the actual execution so we just jumped into it as fast as we can, even though we knew that the validation and market research part is crucial.
So I would definitely spend more time on research, planning, validating before writing the first line of code.
But I think that the main reason that we rushed into building the product is that we were scared that our time will run out, in terms of our savings.
I consume most of my knowledge from audio, mostly podcasts and audiobooks my favorite podcast is “Hashavua”, a podcast in Hebrew that was made by two incredible guys that shared their experience and interviewed so many great entrepreneurs, I have listened to the entire show twice :), very recommended for Hebrew speakers.
“Lean Startup” is also an amazing resource and can really help in working in the right process.
My Twitter handle is @ronco1st.
Invite us into your inbox and get immense learning and 80+ deals on tools to help you scale your startup (worth up to $50,000)!