I posted about my Slack task manager here 3 months ago. Here's what actually happened (including 4 months of Slack review rejections)
▲ 15 r/Slack+1 crossposts

I posted about my Slack task manager here 3 months ago. Here's what actually happened (including 4 months of Slack review rejections)

Hey IH,

I posted Qevo here about 3 months ago, the inbox-style task manager where tasks get pushed directly to people's queues instead of getting buried in Slack threads.

Figured I'd share an update because the main thing that happened wasn't growth, it was a masterclass in getting rejected by Slack.

The Slack Marketplace review process is brutal

When I posted, the Slack integration was "pending approval." What followed was 4 rounds of rejections over 3 months. Every round had 4-5 specific issues to fix, then a 3-4 week wait to find out you missed something else.

Things I had to fix across the rounds:

The bot was named "Queue" but the app was named "Qevo." Confusing users apparently. Simple fix, but you only find out after a full review cycle.

My landing page showed /qevo as a command that grabs the last channel message. Reviewers tested it, it failed. Turns out the bot needs to be a member of the channel first. (Was not a requirement in their earlier versions). Had to auto join public channels, add a proper error message for private ones, and update the landing page copy.

They rejected im:history and mpim:history as user token scopes, "too much access to workspace data." So DM support via bare `/qevo` had to be dropped entirely.

My app listed Spanish as a supported language. They asked for proof. The bot responses were actually translated (using the user_locale field Slack sends in the slash command payload) but I had to explain how.

A typo in the long description: "Start using GQevo today." Only caught in review round 3.

The whole process took longer than building the original integration.

Where things actually stand

The Slack app is now what I am hoping is about to be approved as per my last messaging with them. Slack app is now approved and live

Email to task is still the feature that gets the best reaction. People immediately get it. Slack is taking months to ship.

What I'd do differently

Don't list a feature as "coming soon" or "pending approval" in your launch post. Just launch when it's ready. The Slack integration being in-progress for 3 months after my original post made updates awkward.

Read the Slack app review guidelines obsessively before submitting. The checklist they publish covers maybe 30% of what they actually check.

Still free for individuals, $3/seat/month for teams: getqevo.com

Happy to answer questions about the Slack review process specifically. It's not well documented and I wish someone had written this post when I was going through it.

I've also seen a few other founders here going through the same Slack approval battle. Would be curious if anyone else has tips or horror stories, mine was apparently a rough one

u/Asipahio — 17 hours ago

I built a task manager where tasks come to YOU — no more "did you see my message?"

Hey IH,

I got tired of the same problem every team has: you assign a task in Slack, it gets buried in threads, the person never saw it, nothing gets done. You follow up. Repeat forever.

So I built Qevo — an inbox-style task manager where tasks are pushed directly to people's personal queues. No searching, no missed assignments, no "I thought you were handling that."

  • Everyone has their own task queue (like an inbox for tasks)
  • You push tasks to specific people. They land in their queue, guaranteed
  • They manage their own queue and work through it at their pace

What I built in ~3 months:

  • Personal task queues (free forever, no limits)
  • Email-to-task: forward any email → instant task
  • Slack integration: /qevo in any message → task created (Still pending their final approval)
  • Chrome extension for one-click task capture from any webpage
  • Team plan for pushing tasks across teammates
  • Shareable queues + productivity stats

Why another task app? Most task managers are project centric (Trello boards, Jira backlogs). Great for planning, terrible for the actual handoff. "I assigned it to you" means nothing if it's buried in a 200 card board. Qevo is person-centric - each person has their queue, and things land there directly. You can also see how busy someone is if they share their queue.

Where I am:

  • Launched about a month ago
  • Free plan for individuals, Team plan at $3/seat/month
  • Have a Chrome extension live on the Web Store

What worked:

  • The email-to-task feature gets the best reaction. People immediately get it
  • Starting with a free personal plan (no credit card) removes signup friction completely

What I'm struggling with:

  • Getting the first paying teams (individuals love it, converting to team plan is harder)
  • Finding the right channel to reach project managers and team leads

If you manage a team and hate losing tasks in Slack/email, I'd genuinely love feedback. Happy to give anyone here extended trial access.

Link: http://www.getqevo.com

reddit.com
u/Asipahio — 3 months ago

You know the feeling. You're deep in something, a message comes in, you mentally note "I'll reply to that in a minute" and then you surface three hours later and it's gone. Not gone from Slack, gone from your head.

That was me constantly. Slack messages, emails, things people mentioned in passing. They'd evaporate unless I acted on them immediately. My memory was not the system I thought it was.

I tried every task app. The problem was none of them were where the tasks were coming from. Tasks were living in Slack, in my inbox, in meeting notes and getting them into a separate app required enough friction that I'd skip it when I was busy. Which was always.

So in January I started building Qevo, a single inbox where anything actionable can land. Forward an email, send a message to a Slack bot, paste a link, it becomes a task. No app switching, no friction, nothing falls through.

Where I'm at:

2 months in, building mostly solo Handful of users, no paying customers yet Product works, now trying to figure out if anyone else has this problem badly enough to pay for it That last part is where I'm stuck. I know I had this problem. I know the people I've shown it to nod when I describe it. But converting that into users who actually stick around and eventually pay, that's the gap I'm trying to close right now.

If this resonates with you, or if you've solved this kind of distribution problem before, I'd genuinely love to hear how you thought about it.

http://www.getqevo.com if you want to look.

reddit.com
u/Asipahio — 4 months ago