3 ms·

To add on: your design is fine. Work on pinpointing what burning problem you solve and how your solution is better. I had a hard time imagining the answers to

• jamesmcintyre 8y ago
  Thanks so much for the feedback! We are definitely iterating on our messaging and I value this feedback, we know we're not 100% there with the messaging. The primary problem we're addressing is that of "too many apps" causing scattered information and often redundant workflows. Slack does a good job of allowing very specific "hooks" to be created, i.e. a bot which updates a channel of specific activity in a specific app. Likewise, Zapier allows users to configure "one-to-one" type automation. We designed Nifty to continuously scour all your teams' data across all of their apps and then automatically predict relevant actions or information as user's are using their existing apps. In short, Nifty is designed not just to allow the configuration of one-off, "one-to-one" integrations but to continuously suggest any number of helpful actions or data across all of your apps without any manual configuration of the integrations themselves. I know it's a wordy description and, again, we're working on that but I wanted to make sure I communicated to you the difference between our product and some of the existing solutions out there. Thanks again for taking the time to leave your feedback, it's greatly appreciated!