JRFuentes7

Been using it since alpha stage. Love the way I can ramble and it turns it into coherent paragraphs that I can edit for my recap of meetings or to prepare drafts of emails :)

E. P. I. C.

Here's a quick overview of what we do:

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.

Thanks, austenallred. I'm not sure what you mean by "people will go out of their way to get it". Can you tell us more? I'd love to address that in our application.

Ummm... looks like we maxed out the number of concurrent viewers (max: 50) who can see the Google Doc. We're going to move the application to our blog.

Cool. Can you go a bit deeper and tell us why? As in, why is that more compelling to you?

Very good thoughts, porter. We'll consider this more and edit our application. This is precisely the kind of feedback we're looking for here. :)

"Honestly, I think it's a cool widget! It doesn't sound nearly big enough to get a 10x return on VC though."

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."

Thanks. You're right that it's not just what users say. You have to observe what they do, too. In the next version of our product, we want to provide a "confidence score" for a person's feedback, which is based on what we've observed them doing in the application (e.g., are they a power user? are they freemium or enterprise user? did they leave yes/no feedback + commentary?).

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.