Feedgrip

We initiated a series of blog posts and posted the links in various communities where our target personas (namely Product Managers, Customer Support agents, etc) hang out. Moreover we re-activated our Twitter account with a goal of reaching 1000 followers (now at 400). These efforts resulted in our first demo meeting for 2021 with the Chief Product Officer of a very well known company.

Feedgrip plan for January

• Add one more integration with a feedback channel (e.g. Play Store or Intercom)
• Get our email service back online
• Fire up Fire those nasty ML algorithms we've been building

P.S: Anyone who holds us accountable on 31/1 will get cookies

Started with a tweet regarding expenses and revenue. Copying here:

First #buildinpublic tweet should have some $ data:

Expenses:

• $20 / month for Gsuite
• $0 / month for AWS because ProductHunt Ship comes with $5000 credits
• $15 / week / person for our cocktails 🍸

Revenue:

• $0 yet 🤗

We are really happy that Feedgrip has reached the magic number of 3 beta users! Not that magical, but for us it is super important!

How we achieved this

We've been shamefully cold email-ing people for 4-5 months now. It was difficult at the beginning, since we only had one integration up and running (namely Drift), which meant that we only could target Product Managers in companies that are using Drift to collect user feedback.

As we kept adding integrations to collect feedback from (Zendesk and Help Scout) the pool of people we could talk about Feedgrip became a little bit larger.

However, cold emailing did not work for us very well. We had less than 1% response rate, and none of these emails ended up in the user beta testing the product.

The first 3 beta testers found us themselves, through our Medium posts, Twitter and IndieHackers presence.

We have to think about this and adjust our strategy in the weeks to follow.

P.S: Another 3 demos booked for the following week! Let's hope we get another 3 beta users :)

Our private beta users can connect Feedgrip to their Help Scout account and get a Product Manager's view of all the feedback found in customer conversations. Fused with other sources (e.g. feedback manually entered in the platform, Drift conversations or Zendesk tickets and more to come), Help Scout conversations can reveal much desired features or bug reports.

Users can search on their feedback and form topics of their interest.

Our Drift integration is now live!

Our private beta users can connect Feedgrip to their Drift account and get a Product Manager's view of all the feedback found in customer conversations. Fused with other sources (e.g. feedback manually entered in the platform, Zendesk tickets and more to come), Drift conversations can reveal much desired features or bug reports.

Users can search on their feedback and form topics of their interest.

We just released Feedgrip private beta!

It includes:

• Zendesk integration: Companies with Zendesk Support can hook it up. Thus, PMs can get an abstract view of user requests

• sentiment analysis: We perform sentiment analysis on all the requests

• automatic feedback grouping: We group similar requests together

• and some more whistles and bells

Next up: Integration with Drift

The first of many integrations is now in production for our private beta users! We deployed our Zendesk connector, thus our users are now able to:

• Search in their Zendesk tickets
• Filter them with tags, sentiment and date period
• Investigate semantic groups of tickets (that is, tickets that are related to each other)
• Pin the tickets they want to their workspace in order to work with them later

New name, new landing page, same goal: Be the absolute AI-powered solution for feedback management!

After changing our name, we decided to do some serious work on design, both of our Landing page and our product!

Next goal: Private Beta release for Zendesk users on November 30!

We changed our name from Ambissues to Feedgrip. The reason to do that was twofold:

1. People didn't know how to spell Ambissues
2. Ambissues didn't give any sense of what our product is doing

This was not easy, even in our early stage, since the name is everywhere (Twitter, Website, Indiehackers, Medium, Blogs, etc). Some place (like Indiehackers e.g.) don't even allow the change of the name.