HN user

ljensen

100 karma
Posts9
Comments8
View on HN

I'm glad that you like the idea.

Here's the official privacy policy: http://roadrules.co/terms/privacy.html

We're trying to maintain everyone's privacy while offering a helpful service. Some ways that we are doing that include

- In the app, the user has a white list to manage who can request location and availability data. - Maintaining as much data on the phone as possible (versus sending it to the cloud).

In terms of predicting customers' behavior, this concept of holding a human context to Big Data is best illustrated with the story earlier this year in which Target predicted that a teenage girl was pregnant:

http://www.forbes.com/sites/kashmirhill/2012/02/16/how-targe...

In terms of predicting financial meltdowns, I'm interested in seeing how MIT thinks their data will change human behavior. For the most part, people know when financial bubbles are not sustainable; they just choose not to act.

A Real Jobs Plan 14 years ago

Clinton's speech at the DNC emphasized updating Americans' skillset as a "pull strategy".

As it relates to tech, this means enabling people to apply technology to leverage their current skillset; from manufacturing jobs to the arts.

As it relates to entrepreneurship, this means investing in programs that encourage entrepreneurship - of any industry - throughout country. YC is an efficient model for entrepreneurship in tech. In the beer industry, the Samuel Adams Brewing the American Dream program (http://btad.samueladams.com/) is another good model because it offers a variety of resources and levels of assistance.

This undermines my basic assessment that if a business on Yelp has at least 100 reviews, it compelled enough people to respond an is worth checking out. I'm still able to use this methodology on Foursquare; if people consistently check into a place, it can't be that bad.

Nice interface. I like how the smart prioritization and timeline add context to the end customer. This looks like a useful community management tool.

I don't understand the customer support aspect of the tool beyond offering a customer view and messaging. The video demo glosses over what a customer support issue would look like since the person had already figured out the problem by the time Support could respond. Can you offer a demonstration of what an exchange might look like if support was needed?

Also, your use of the word "proactive" made me think that the tool helps anticipate problems. Every example demonstrated reaction(sending emails after a sign-up or payment event). Even your Crewpedia case study was a reactive example because support had to respond and make changes to the UI based on how people were using the page. Can you offer some examples of how the tool allowed users to expect an event? Otherwise, I suggest using a different word such as "insightful" or "contextual".