Some more feedback, after watching the video and taking a quick look at the site:
- I think I really like the idea but I didn’t see how you get from comments to a conclusion. Somebody reads the comments and edits the Description and Outcome fields? In which case, what does the audit trail look like?
- I get that you think this will reduce the need for meetings, but: 1) I think suggesting “no meetings” sounds faddish/unrealistic and 2) the calculator is cheesy, it’s both obviously not what real meetings cost and also accurate to the penny…
- In my last BigCorp job, the thing to sell against would be Slack and Jira, IMO the two worst technologies in most dev orgs today. Good that you mention them but maybe give some examples of why using AsyncGo is better, especially vs. Jira.
- The pricing seems a little odd. It seems like this would target remote startups but then maybe they never pay you (5 users free). But it’s not freemium because “all features unlocked.” And from 6-50 users it’s the same price. I’m no pricing expert but if I can’t see you you’d make money on me, I’d worry about committing to the product.
- We all want money but selling your consulting service in the same place as your product makes it look like you don’t believe in the product. And does anybody really hire this kind of consultant based on a website? Seems far fetched, I would stick to the product on the website.
- For many people lock-in is a dealbreaker especially if the company might not stick around. How do I get my data out?
- Browser extensions are nice but is it for all/most browsers?
- Update the Blog! I see this a lot: you start a blog because it seems like a good marketing trick then you don’t keep up with it. Post at least monthly, or take it down, because a stagnant blog implies a stagnant product, and here you have all these HN eyeballs ready to read your blog! Not every post has to be about the product directly, you can talk about adjacent things, blog about the tech stack, about remote work culture, etc.
Good luck with it! Again, I think I like the idea, it reminds me a bit of early Basecamp, but it could use some more explanation to get people to try it.
- I think I really like the idea but I didn’t see how you get from comments to a conclusion. Somebody reads the comments and edits the Description and Outcome fields? In which case, what does the audit trail look like?
- I get that you think this will reduce the need for meetings, but: 1) I think suggesting “no meetings” sounds faddish/unrealistic and 2) the calculator is cheesy, it’s both obviously not what real meetings cost and also accurate to the penny…
- In my last BigCorp job, the thing to sell against would be Slack and Jira, IMO the two worst technologies in most dev orgs today. Good that you mention them but maybe give some examples of why using AsyncGo is better, especially vs. Jira.
- The pricing seems a little odd. It seems like this would target remote startups but then maybe they never pay you (5 users free). But it’s not freemium because “all features unlocked.” And from 6-50 users it’s the same price. I’m no pricing expert but if I can’t see you you’d make money on me, I’d worry about committing to the product.
- We all want money but selling your consulting service in the same place as your product makes it look like you don’t believe in the product. And does anybody really hire this kind of consultant based on a website? Seems far fetched, I would stick to the product on the website.
- For many people lock-in is a dealbreaker especially if the company might not stick around. How do I get my data out?
- Browser extensions are nice but is it for all/most browsers?
- Update the Blog! I see this a lot: you start a blog because it seems like a good marketing trick then you don’t keep up with it. Post at least monthly, or take it down, because a stagnant blog implies a stagnant product, and here you have all these HN eyeballs ready to read your blog! Not every post has to be about the product directly, you can talk about adjacent things, blog about the tech stack, about remote work culture, etc.
Good luck with it! Again, I think I like the idea, it reminds me a bit of early Basecamp, but it could use some more explanation to get people to try it.