We use it/love it at Uber. Had a problem has been with the results building up in RabbitMQ and causing the queue to exceed it's memory allocation. We disabled results, and fortunately that's now the default with this release.
Interesting idea. I made an attempt to vet a similar idea in the spring of 2009, so maybe my experience can help you out:
In order to prove or disprove the concept without actually building out any kind of CMS or infrastructure, I set up a marketing site and some demo restaurant mobile sites (really good looking stuff built on jQTouch). Next step was to build prospect lists with every OpenTable restaurant in a handful of Ohio cities (I live in SF now, but was in Cincinnati at the time) and do a ton of cold calling.
After hundreds of pitches at different price points, I only managed to sell a few at $49/year and decided not to pursue any further. Having little prior sales experience (sold CUTCO as a high schooler) was a problem for me. Timing is crucial and being too early was another likely inhibitor. Figuring out the best sales channel is may be your biggest challenge. Along with how best to pitch the restaurants, who are not traditional early adopters.
I'll be keeping an eye on you guys. Best of luck!!
Thanks for your feedback! This sounds precisely like what we're encountering right now: restaurants are uncertain why people would want to see their site on a phone and how it increases their bottom line. We'd like to educate them and show them that customer discovery = ROI, but we're not sure how to evaluate that in our context. Some people here have suggested success stories, which we think is fantastic.
