We're applying to YC W2014, and we'd love your feedback on our application: docs.google.com/document/d/1kv_Rgr4-y9wvrOxwZdTevhW-r-i5pktUBcw6t0ufazY
Give it to us straight. We've got thick skins.
-- UPDATE -- CRAP! Looks like we exceeded Google Docs' max number of concurrent viewers. Here's our application on Tumblr: startupsthehardway.tumblr.com/post/63091956854/featurekickers-yc-w2014-application
That said, I do think it demonstrates some ability to hustle. Here, what you're really doing is getting HN to write, or rather optimise your YC application. You're exploiting the vanity of HN, i.e. everyone wants to look smart by providing an ingenious comment. You synthesise the best into your application, and make off like a bandit. That would be a pretty novel hack in itself. :)
the fact there are no competitors gives me pause. That's actually not a good thing.
--------------- "Assuming we obtain 4500 customers within 5 years, charging an average of $1000/mo, we expect to earn $54M in annual recurring revenue from our products and services."
- this is waaaaay too unrealistic IMO. Any company willing to pay $1k per month for this would probably just build the feauture themselves, no? I don't think large companies are your target market. -----------------------
- dejamore: I love the video - dealonaire.com link didn't work
Our product helps software teams “make something people want.”
When teams build or improve software, they crave data to inform their decisions, but calling, emailing, and surveying customers falls short. Product teams can’t afford to get this wrong given limited and expensive engineering resources.
With FeatureKicker, a team can quickly add a “call to action” for a new feature on a website. When a user clicks on the experimental button, our tech opens a modal window and gets user input on the new feature.
Similarly, teams can get feedback on existing features of their website, so they can improve their product.
Have either of you worked on product teams before? Do you have feedback from product teams? Usually this isn't a problem of competing features, but usually of "will people use this" at an entire product or project level. MVP is how most people I know attack these things.
I hear ya... we worry about that sometimes. But then I think about what PG says re "it's our Altair." We gotta start somewhere.
How big is the market? There are 5M product managers in the US, according to LinkedIn. Assuming 13 PMs per company, there are many, many companies that should be using this.
I don't think you could or should replace our tech with a click event. I'll agree that 404 tests are a good start... but they lack qualitative data and a rules engine. I believe that's an inferior customer experience.
We've interviewed 100+ product teams at this point. We're getting good feedback -- especially re "getting data on existing features."
Could you have a view for end users so you can see all proposed new features? Sort of crowd-sourced product marketing...
Edit: What about letting end users suggest completely new features this way? (e.g. allowing them to draw on a screenshot of the page and say "I want a button here that does XYZ").
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 :)
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?". :-)
I think the idea is really cool and I can see how useful it could be for companies, but do you have evidence that users actually give feedback via your method?
I'm trying to look at this product from that side of the equation, and I could see me getting frustrated that clicking "Sign up with Google+" doesn't actually do that. If you have evidence showing that users are willing to give feedback, or have some type of insight regarding that, I'd definitely include it in the application.
Goodluck!
We think this is because we ask the right person, the right question at the right time. Its the right person, because this person clicked on the feature, its the right question because the question is about the feature they clicked on and not their age, gender etc. and its the right time because they are in the app, just clicked on the feature and at the height of their curiosity when it comes to that feature.
In regards to frustration, we believe this is a valid theoretical concern, but in practicality with our 27 beta customers, we haven't yet had anyone complain.
We think this is because our customers are using this in a "logged-in" product, leveraging our rules engine to control how often the feature experiment is shown and to who.
One idea would be to make your video a little more natural and less 'cutesy'. They are trying to get to know the real you.
Good luck! Our company, Loveseat (formerly Bidbash) got an interview for summer '13 - but, we didn't get in. Met PG and that was fun. We're still doing it though! Stick with it.
Seems like a cool little widget, but I doubt the market for it would be big enough to be worth your time. It's a small enough of a problem that most people won't notice it, and if they do they could easily solve it themselves. People won't be looking for a solution, and it's not cool enough that people would share it just because.
As for your questions, your responses are way too long.
I think this seems like an "easy" thing to build in-house, but we believe getting this right will take a ton of time, which companies could put towards doing what they do best.
Here is what we have: 1. The rules engine, to track visitors and fine control who see's feature experiments and how often. 2. An analytics suite, to capture all data and show it in a form which is digestible and allows a PM to take action 3. Making overlays work cross browser and device. 4. Solution which requires absolutely no-code to get feedback on existing features. A gui where PM's can visually find features on their website, tap on them and configure them to ask for feedback.
One concern I'd have if using this product, is that often the customer says what they think they want, but don't actually need. So I'd expect there to be some decent "management" tools for working through all the feedback. Maybe some sort of internal scoring or feedback system within the company or something.
As for the internal scoring system, we integrate with JIRA so you can send your data to your existing prod-dev mgmt tools. We hear KANO analysis is really powerful when it comes to scoring your prod roadmap.
One thing I think you guys should consider in your target market is mobile app developers. Also consider looking at Backend-as-a-service providers like StackMob/Pars in your market size estimations.
Good luck!
What do you mean by "Backend-as-a-service"? Tell me more.