[sandeep45]

Arethuza: Thanks for your feedback.

We have a rules engine, which can be used to really fine tune when and how the feature experiments are shown.

For example, you can setup so 1. feature experiments are only shown to a customer who has logged in at at least X times. 2. You can control so they don't see an experiment after it has been seen once by them. 3. You could say that if they have seen 1 feature experiment, then they shouldn't see another 1 for X days. 4. You could also only show to X percentage of your traffic. 5. And many more rules.

I like the idea of being able to crowd source ideas. It would be a great feature for me to "kick" and see what customers say :)

[arethuza]

No problem.

BTW One question that I think anyone considering an investment would ask is: "Do you use your own product to collect data on features for your product?". :-)

[sandeep45]

Arethuza: Absolutely. I have been "kicking" every feature my co-founder has brought to me, before I build them. Recently he told me build a feature which shows a google map, with customer thumbs up displayed by locations for a feature. Before building this thing, i "kicked" it by putting a mocked maps image with a button on top saying "enable report". Within days it was clear that this feature was not a top priority.

Also I use FK to monitor our existing features and ask feedback on them. I love that now i don't have to write 4 lines of code to monitor 1 line of code. FeatureKicker's no-change solution to monitor and get feedback on existing features rocks.