Flow

Beautiful team chat with tightly integrated task management

#2 Product of the WeekSeptember 01, 2015
+1
Discussion
Would you recommend this product?
4 Reviews5.0/5
Tasks is the one big missing piece of Slack.
Upvote (16)Share
@andrewwarner But doesn't @slack integrate with task applications through their API? Not sure how it works, but I thought maybe there was a way.
Hey, Product Hunters! We may not be making life-sized Lego blocks, but we’re on a mission to make working together easier for teams. And our team is happy to answer any questions you have about Flow and where we’re headed with it. :-)
Upvote (13)Share
@userhue What he said! Super excited to be on here, and looking forward to hearing everyone's questions 🙋🏼🙋🏼🙋🏼
@awilkinson Wow, Flow chat looks great! Flow is starting to feel like a good balance between Slack, Trello and Asana. Curious to know how you and @userhue (hey Lance!) are planning on getting people to switch from those tools. Also, how much are you charging for Flow? I'm tempted to try it.
@userhue Props on great copy - your Product Hunter welcome made me smile (:
@eliservescent Haha -- thanks Elisa! I'm always amazed at the breadth of products featured on PH... :-)
@robjama Robleh -- great to "see" you my friend! You can use Flow -- with no limits -- for as long as you need to see if it's a fit... and when your team has adopted it, we have pretty standard SaaS pricing tiers based on team size. It works out to between $6 and $12 per user. In terms of getting people to switch, we've observed that task management is a software space where switching is quite common, so our strategy is to tap into that and give teams enough time to form a habit of using Flow... helped along by our new team chat functionality, great on-boarding, and early lifecycle messages/emails. In the end we think we've struck just the right balance between the things people love about those other products you mentioned. ;-)
During my last meeting, I switched between Trello & Slack every 30 seconds. There's an undeniable use case here.
Upvote (10)Share
@kkdub Hey Kelly -- absolutely! And we're going to make Flow's connection between chat and tasks even tighter over the coming weeks.
It looks beautiful! Every pixel well-placed. And you can't really say "No" to the pricing scheme.. Can I ask how Metalab's work on Slack has influenced the decision process here? And do you see the chat part totally taking over the rest of the workflow?
@mmariansky Hey Matty. Great question ☺️ We've used a ton of chat products over the years—all the big ones—and while we found that they made us feel great, and super connected, we noticed that we actually got less done. We found that using chat was a little like having a manic brainstorming session. You leave a messy whiteboard and walk out feeling super energized, but then when you meet a couple weeks later you haven't actually moved the ball forward. We realized that if we didn't convert our big, messy conversations into next steps, nothing got done. Of course, we used Flow for this, but we kept thinking "man, it sure would be nice if we could create tasks as we're talking" yada, yada, yada, 10 months later: Flow Chat! 😎✌️
Upvote (15)Share
@awilkinson Thanks, but to be more precise - other task/project managers chose to build a Slack/Hipchat integration, but you guys built a whole new Slack (and a very nice looking one). I strongly believe that a lot of Slack's success comes from the early work done by Metalab, and I'm very very curious to see where this will go next
@mmariansky An integration didn't feel like a very elegant solution, and our customers kept asking us to add Chat to Flow. We'd much rather say "hey, we solved your problem" instead of "hey, we solved your problem, but go over there and pay more money for this other product".
Upvote (11)Share
This is a great product. I often switch between Slack and Trello; with Flow it's all at one place.
@d4nyll Thanks, Daniel! We observed how people use Flow (and other task managers) and saw that there's plenty of discussion that occurs before a task or project is created. Those conversations were happening in email and meetings -- and in team chat tools. For that last group, while having discussions in a chat tool was a time saver, there was still a noticeable amount of friction... created by having to constantly switch apps. We saw that people were having discussions but relying on someone to transfer/transcribe the chat outcome into the task manager... which didn't always happen. And so we wanted to eliminate that friction and make it a no-brainer to have productive (and some non-productive!) conversations -- but know that the talk is easily turned into action.