Built something internally to reduce chaos at work — looking for early feedback
We built an internal tool to solve a problem we kept running into as a team — too many tools, too much context switching, and work getting fragmented.
It started as a simple internal fix, not a product.
Now it’s at a stage where we’d like a few thoughtful teams to try it and tell us what actually works and what doesn’t.
We’re not selling anything and not launching publicly yet — just looking for honest feedback from people who deal with this kind of chaos daily.
If that sounds relevant to you, happy to connect privately.
www.omnex.tech
admin@omnex.tech
This problem resonates — context switching and fragmented tools are one of those silent productivity drains that founders and teams often notice only after it already costs hours per week. The fact that you started this as an internal fix and are now exploring it with others makes the feedback you get much more grounded.
One thing I’ve noticed in workflows like this is that the real signal of value isn’t just people opening the tool, it’s whether it actually changes where people go next after an interruption. For example, do people return to their actual work faster, with fewer search loops across chat/email/docs? That kind of behavioral signal often tells more than raw usage numbers.
Curious — in your early tests, what’s the strongest unprompted behavior change you’ve seen (like fewer cross-tool hops, faster re-entry, or less hunting for context)? That kind of insight usually helps sharpen early validation before a broader roll-out.
Thanks — this is exactly the direction we’re measuring. In early tests (small sample so far), the strongest unprompted change we’ve seen is “OMNEX first after interruption”: people come back, open OMNEX, and use it to re-orient (what I was doing + why + what’s next) instead of starting in Slack/Jira/Docs and doing the usual scavenger hunt. The metrics we’re tracking around that are: time to first purposeful action after return (comment/commit/task update), # of cross-tool hops before that action, and repeated context lookups (same ticket/doc opened multiple times). Still validating which pattern is most consistent across teams — if you’re open to trying it with a real workflow, early access is here: https://omnex.tech (fill the form and you’ll get the app link by email). Also happy to send a direct invite if you DM me.