Ask HN: How should we go about marketing our app?
The app itself (http://www.getchowderapp.com) is a collaborative restaurant finder, and came about after many frustrating incidents trying to decide where to eat with my girlfriend (usually something along the lines of "What do you want to eat?" – I don't mind – "Do you want pizza?" – No – "How about seafood?" – No – "Then pick somewhere!!"). A friend and I had some fun developing an app to try and ease the friction of making food decisions when out in a group. It's a little like Tinder for food, only you're matching restaurants, not people, with your friends.
When we initially did our market research, we were aiming solely at indecisive couples who had troubles picking places to eat because they were overwhelmed with options, but later realised that there was a much wider audience and shifted our focus to groups of friends. However, while we've had plenty of people respond with "Huh, neat idea" when we pitched it as an app for groups, I feel like it resonates much more strongly with people when pitched as an app to 'help couples decide where to eat'. When pitched as the latter, we got responses where people explicitly mentioned having this problem with their SOs, as opposed to the former where it was maybe more like 'Cool idea, I could see people using this'.
Given our incredibly limited budget and lack of funding, I'm beginning to think it might make more sense to focus on couples first and expand from there. I'd be very interested in hearing other people's thoughts!
Ultimately we're both just looking forward to the opportunity to launch something in the first place - the experience gained thus far has been very beneficial, and we've had a blast developing it.
Many thanks in advance.
16 comments
[ 2.8 ms ] story [ 42.5 ms ] threadIf so, what are their pain points and how are they being addressed?
If not, then getting one user is more important than a marketing strategy, and harder. People using the app validates the beliefs:
Most importantly, it provides feedback to iterate upon and word of mouth advertising.Good luck.
Monetisation will come primarily from providing analytics to restaurants. Because of the way the app works, we can go to a restaurant and give them info like "x number of people were interested in going to your restaurant, but they went across the road to your competitor instead". In addition to analytics, we planned to do the usual promoted results and coupons etc.
Now think about Foursquare and how even they have not been successful in offering something similar to local companies.
I'd quit before I'd waste any time on this venture.
Unless you view this as a learning experience or side project.
Like I said though, it costs us practically nothing to run and it's been a great learning experience so far - I don't see any reason to give up just yet.
It's one of those problems that everyone faces one evening, but the hassle of using an app is usually higher than actually having a 2-minute conversation about where to go.
That being said, you never know what will work, so don't give up just because of random Internet advice.
It looks like your app doesn't need to have network effects to be useful. That's a good thing. So you'd be fine with even 10 people using this every week. That would be a sign that your app is useful. Once you reach that stage, you can focus on scaling. But just even getting 10 couples to use this weekly is a tough challenge. Do you use it? Does any of your friends actually use it?
Looking at your website, if you are disappointed by the conversion rate, target a smaller niche first and see if the conversions increase. Right now it sounds like a generic "restaurant recommendation". The couples angle is not there. You go with more punchy headlines: "no more arguing Friday night about where to take your SO".
Bottom line: go from 0 to 10 users by sheer force of persuasion. Then come back here and we can chat some more :-)
Also try pitching food blogs and technology/lifestyle blogs to review. Write up some stories like "My wife and I kept ordering gross pizza because we couldn't decide where to eat -- here's how we saved our relationship!" Make them entertaining and relatable, and offer them as content for food and restaurant blogs. Find some quality food blogs or youtube foodies, offer to pay for their dinner if they will use your app to decide where to go.
Find larger food/restaurant apps and sites, ideally ones that complement and not compete with your concept, and look for ways to cross-promote. e.g. they make a post or ad or something to drive users to your app, and in return you put a prominent button on in your app for six months that says "View this in BigFoodApp" and opens their product.
I like the approach suggested by the book "Traction", which boils down to try a bunch of things a little bit to see which one works, then focus on the channel that gets you the most return.
I would try a basic video that just is informative showing off your app.
I would also see If you could get a short video made that is somewhat humorous involving a couple arguing over dinner and then using your app, it could have potential.
I'm hesitant to "like" a restaurant suggestion because if I was to match, then I'm stuck going to that restaurant for dinner when there is possibly a better match that just had yet to be suggested to me. The original Tinder model works because there is no risk of being locked-in (lol).
That being said, I think this is a great idea and IMO your initial use-case and test users should be startups trying to decide what to order the team on Seamless. Print out some flyers that say "Team can't decide what to order for lunch?" and post them around co-working spaces.
If I was building this app my first iteration would have been to show the users a list of the top 10 nearby restaurants weighted by stars on yelp and filtered by price/distance. Let them give a 1-5 thumbs-up rating of as many restaurants on that list as they want and total up the number of upvotes for each option.
Goodluck!