Looking for honest feedback on a new way to reduce tool overload
I’m looking for honest feedback on something I’ve been building.
Like many of you, I kept struggling with context switching — email, Slack, calendar, docs, tasks, meetings… everything scattered. So I built a small internal tool to bring it into one place.
It’s early and rough around the edges, and I’m not trying to sell anything — I just want to learn whether this actually helps or if I’m solving the wrong problem.
If you’re open to testing it and telling me what works / doesn’t, I’d really appreciate it.
Here’s the link:
https://omnex.tech
Hi Modar, Your Omnex post is still in the useful early stage: a clear tool-overload hypothesis and a direct request for testers to say what works and what does not. I’m building Build Before 2030: a manually reviewed public record where makers claim a Founding 100 number, set one measurable 30-day milestone, and later add proof of what shipped. The first cohort is free. Omnex feels like a strong fit. Interested? https://buildbefore2030.com
Nice idea! The tool overload problem definitely resonates.
One thing I’m curious about: when someone lands on the page, what’s the first job you want OMNEX to replace? Email, chat, task tracking, or something else?
Right now it reads like an “everything workspace”, which is powerful, but sometimes harder for users to anchor on one clear starting point.