AB-TASK
One App for Tasks, Talks & Docs
-
2
Why would anyone use this? Genuine question as I'm not sure what the advantage would be.
I see something like Trello / Google Docs / Slack. If I'm already using those tools (which perform each of their own functions incredibly well) why would I jump ship to yet another all-in-one simplified task management platform that I don't know will still be around next week?
Edit: In the Kanban board I can't drag a task from one column to another. I have to select the checkbox on the task card (shouldn't that be used to mark the task as done?) and then hit 'edit' which opens up a side panel. I had tried click the task but that brings me to a blank page (of a chat window?) and there's a "back" arrow in the top right which opens up the same side panel. But doing it the second way leaves me on a page with no way to navigate back to the board I was just on.
This is a perfect example of how each function you've implemented is an objectively worse experience for the user. Especially power users as I don't see any shortcuts. I'm genuinely interested to know what you think your USP is because telling users that they only have to sign in to one platform in order to use an array of mediocre tools ain't going to cut it.
Also, a 5 person team is limited to 70 tasks per month and you charge for connection time to your server? What?!
-
1
Thanks for the detailed feedback! I really appreciate you taking the time to check out AB-TASK and share your thoughts. If you'd like to see how everything fits together, I'd be happy to walk you through it on a quick demo call. You can book a 15-minute session here: https://calendly.com/ab-task-georgy/15min or a 30-minute deep dive here: https://calendly.com/ab-task-georgy/30min. Happy to answer any questions!
The real power of AB-TASK is context consolidation and communication efficiency. Instead of constantly switching between multiple apps, you get everything in one place. The universal communication channel is at the core of the app - it supports real-time chats with message streaming, collaborative editing, and seamlessly integrates with all items within AB-TASK. Essentially, you can have real-time conversations inside tasks just like in Slack, and everything stays connected.
You can create follow-ups (think threads) of any types (tasks, talks or docs). It all consolidates context and creates a great foundation for AI enhanced workflows. AI will be our main focus for this year in terms of further product development.
Regarding the Kanban board - drag-and-drop is actually being released tomorrow! It’s been the most requested feature, and I totally get how important it is for usability. Overall, five years of development is a long time, and while I wouldn’t call AB-TASK 100% complete or bug-free (what product ever is?), I’d say it’s a mature MVP at this point, and we’ll be dropping the "beta" label soon.
On pricing - yes, it's a bit different from the usual SaaS model. We charge based on AWS resource consumption, not per user or per feature. The 70 tasks per month for a 5-person team is just an example usage pattern to give a rough estimate of costs. There's no limit on functionality or the number of items - every user gets full access. The price is solely based on how intensively the app is used, and for light users, the cost can even be zero.
Hope that clears things up! Again, really appreciate your feedback, and if you’re open to it, let’s chat - I’d love to show you around AB-TASK and hear more of your thoughts.
-
-
2
Kudos to your dedication and 5 years grinding. I know the feeling as I'm currently in it. Keep grinding and you will see the light at the end of the tunnel soon!
-
1
Thank you for the kind words and I wish you luck with your project as well!
-
-
2
That’s an incredible journey—five years of dedication and $200K is no small feat, especially bootstrapping the whole thing. AB-TASK sounds like a powerhouse, and I can imagine the challenge of balancing real-time communication, task management, and documentation in a single platform.
Now that you’re shifting focus to growth, what’s the game plan? Are you leaning toward organic marketing, paid ads, or maybe partnerships with early adopters? Also, curious—what’s been the biggest technical or product challenge along the way?
Either way, huge respect for sticking with it. Looking forward to seeing AB-TASK in action! 🚀
-
1
Thanks, I really appreciate the support! It’s been a long road, but seeing AB-TASK come together makes it all worth it.
On the growth side, we’re focusing on a mix of direct marketing campaigns, conducting demo calls, and building a community around the product. We’re also creating social media content to raise awareness and connect with teams looking for a streamlined collaboration tool. It’s a learning process, but the goal is to get AB-TASK in front of the right users who’ll benefit the most from it.
As for the biggest challenge, without a doubt, it was building the universal communication channel. Getting real-time message streaming and collaborative editing to work seamlessly was a major technical hurdle. But it’s also one of AB-TASK’s core strengths, so the effort was well worth it.
Excited to take this next step and get more teams using it. Appreciate the encouragement!
-
-
1
Yes.
Hey, founders, we all build teams. When there is more than 1 person working on a project, the problem of team communication rises.
It's not just about talking to each other. It's also about how we manage tasks, exchange knowledge and make decisions within our teams. Everything is team communication in the end.
How do people solve this problem? Well, they use apps! "Oh, I need to communicate in real-time." Here is a messaging app. Let's say, Slack. "Oh, I need to manage tasks." Here is a task-management app. Let's say, Jira. You get the idea.
What's wrong with this approach?
You end up with multiple apps and it quickly becomes a mess. One day a developer opens a story in the task management app and realizes that most of the discussions about the story took place in the messaging app. They start digging in the messaging app to gain the necessary context or even worse, they just don't bother to do it.
Does this sound familiar to you? Please share you thoughts!
-
1
The problem with team communication is two-fold in my opinion:
-
The team members do not all use the app at the same level. This is usually due to a lack of onboarding/training for the entire team. Just assuming that people will learn how to use the app effectively from their knowledgebase is not an effective team communication success strategy.
-
The company assumes that all team members feel comfortable using the same tools. When you are forcing some team members to use apps that they hate it's only likely that the "unhappy" users will engage with the tool less. This makes communication more difficult for everyone involved.
The solution in my opinion is to discuss how to use communication tools in your organization before you choose tools to use. At a small company like an indie startup, this should be fairly easy.
Hope this helps!
-
-
1
I totally agree. Too many tools out there! I actually read not long ago that the average IT team is using 40-60 tools. Just look at the chat apps...I miss the good old days when I could just talk with someone on Skype. Nowadays, you need to use Telegram, Slack, Discord, Signal, Whatsapp, and plenty of other tools. A quick search on google shows that you have solutions like Shift, All-in-One Messenger, and other similar tools. Might worth checking out.
Comment