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

The neat use-case I see coming out of this is enhancing an onboarding process.

I work for a company which sells wine online, and a large number of people have strong preferences about the types of wines they like (red, white, chardonnay, half-cases, etc.)

It's useful to give people a survey - combined with an explanation of how the site works - as they are signing up. Even more useful is to use their answers to show the new customer a wine which is suited to their tastes. (If you like high-end reds, it wouldn't make sense to show you a half-case of inexpensive white wine to convince you to make you first purchase.)

And if our marketing department can manage their survey, marketing copy, and graphic design without having to ask developers every time they want a change (or if they can save me the time of writing a customizable interface) then all the better.

Onboarding. That's where it's at, yo.

The idea of surveys as a paywall mechanism (eg, New York Times paywall with a survey) is, at first glance, pretty unappealing, because paywalls are de-facto abhorrent. But we'll see; I may not mind filling out a 4-question questionnaire in order to read an article that would otherwise be blocked. Especially if I know that after filling it out once, I will never ever have to fill the survey out again.

And let's not forget about the adult industry! Instead of captchas... well, why not get some interesting marketing analytics out of the deal?

Interested to see how this evolves!




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

Search: