Hacker News new | past | comments | ask | show | jobs | submit login

I think the website illustrates perfectly what can be wrong with a landing page, I had absolutely no idea what the product is suppose to do. Is it a mocking api generating fake user data ? "A Simple Data API" is also to vague to get an idea on what the product is doing. (I had the answer when having a look at the footer but I'm not sure everyone will have a look at the footer).

The pricing page is also really terrible, I see a list of prices for data types but I have no idea how it's actually billed. There is a small infobox on the bottom saying that I'm billed for each successful request, but that should be on the top since I had no idea what the price meant (the button is not inside the box as any pricing page by the way).

It would be also nice to have a price average for the api, how much does it cost to look-up basic customer info on 1000 numbers ? I have to use a calculator to answer that.

(By the way does it work outside the US ? I can only see US phone formats and zip codes).




Agreed. My best guess would have been that the service is an API that allows you to access information on individuals. I suppose this could be useful, but I don't immediately see what "powerful apps" I would build.


On the CRM/targeted marketing side, there are use cases for finding out address and other personal info from any tidbit of information you have. Many times you only get an email or phone, or on the flip side a name + address.

Few examples: In a call center environment, looking up the name and address of the caller to know who you're talking to. Matching loosely on name and zip code can provide the operator with a good idea who they are talking to. The system can then match the caller to demographic and interest data to better support sales/marketing/routing decisions.

We use fullcontact to get social profile (twitter, fb, angellist, linkedin, etc) based on an email or phone number in order to better know the user and their social influence that they can have for our customers. Why? Many third party booking systems (flights, hotels, misc travel, etc) provide only the required fields to make the booking stick with the provider (hotel, for example), in order to prevent the provider from contacting the customer directly and taking away that third party booking service (Expedia, for example) revenue. As such, if Expedia only sends name and zip code, or name and phone number, we can match that with existing public data and/or look it up in fullcontact (or something like this phone reverse lookup) in order to get a more complete profile of a guest.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: