non engineers are bothering me in slack, I hate non engineers

PlsStopSlacking 9000

EMBARRASSINGLY EASY TO BUILD
2/10
Congratulations, you've confused 'I hate interruptions' with 'I hate humans.' Therapy is also an option.

An agent that auto-responds to non-engineers in Slack, triages their requests, routes them to the right person, and protects your precious flow state so you can pretend to be productive.

This is EMBARRASSINGLY_EASY because Slack's own platform, plus three existing tools, already does 90% of this. The remaining 10% is just a simple bot with GPT-4o that reads messages, detects if the sender is non-technical, and fires a polite auto-reply. The real problem here isn't technical — it's that you work with other humans.

whycantwehaveanagentforthis.com
Try Your Own Problem

Viability Analysis

Market Demand65
Tech Feasibility95
Competition78
Monetization40
AI Disruption Risk85
Fun Factor88

Pros & Cons

What's going for it

Genuinely solves a real productivity problem — context switching from Slack kills deep work and there's solid research to back that up
Could expand to full internal IT/HR triage bot, which companies actually pay for — Jira Service Management charges $20+/user/month for this
Slack's API is excellent, well-documented, and a solo dev could ship an MVP in a weekend
The 'non-engineer detection' angle (checking Slack profile title/role) is a funny but genuinely useful routing heuristic

What's against it

Clockwise and Reclaim already do the focus-time protection piece and have millions in funding — you're fighting uphill
Slack's native Workflow Builder does basic auto-response for FREE — your potential customers will realize this the moment they Google it
The 'I hate non-engineers' framing is a product with a TAM of exactly one person: you
Slack Enterprise Grid admins can block third-party bots entirely — your enterprise sales cycle just became a nightmare
If you build this and sell it, your first support tickets will be from... non-engineers. Enjoy.

Who You're Up Against

Open Source Alternatives

When Will Big AI Kill This?

Most Likely Killer

Slack (Salesforce)

Timeline: Already happening — Slack AI launched in 2024

Now3mo6mo1yr2yrNever

How They'll Do It

Slack AI already summarizes threads, auto-responds, and Salesforce is baking Agentforce directly into Slack to handle exactly this kind of message triage natively

Your Survival Strategy

Niche down hard into engineering-team-specific workflows — PR review reminders, incident triage routing, on-call escalation — things Slack AI won't touch because they require deep dev tooling integrations

Confidence

88%

If You're Crazy Enough to Build It

Solo Dev Time

1 weekend for MVP, 2 weeks for something you wouldn't be embarrassed to show people

Team Size

One mildly antisocial backend engineer, which tracks

Estimated Cost

$50-200/month in API costs at scale; $0 to start on Slack free tier

Tech Stack

Slack Bolt SDK (Python)GPT-4o miniRedis (for rate limiting)Railway or Fly.io for hosting

Want to actually build this?

Work with me to ship it.

Survived the verdict? Good. Let's build the damn thing.

Got another problem that needs an agent?

Roast My Problem

whycantwehaveanagentforthis.com

PlsStopSlacking 9000: AI Agent for non engineers are bothering me in slack, I hate no | Why Can't We Have An Agent For This?