OMNEX started as an internal tool because our work was constantly fragmented across email, chat, documents, meetings, and project boards — and too much time was spent just reconstructing context.
We’re now opening it up in early access to a small number of people to learn what actually helps and what doesn’t. This is still very much a work in progress — no launch, no pricing, just real usage and honest feedback.
If you deal with tool overload in your day-to-day work and are open to trying it and sharing thoughts, I’d genuinely appreciate it.
You can see it here: https://omnex.tech
and fill the early access form , and you will get the link by email, for any questions feel free to contact us on support@omnex.tech
The context reconstruction point is the real cost, not just having multiple tools open. I'm the founder of FounderFlow, we ran into the same problem but from the angle of founders running more than one business at once, the mental tax isn't the tools, it's re-establishing what actually needs me today every time you switch. Curious whether your early users are mostly single-team orgs or people juggling multiple projects or businesses, since that changes what centralizing even means.
Hi Modar - Did a quick market research for your product and added some feedback here
The 'operating layer' framing is smart - acknowledging that Notion/Slack/Asana each won their category but created a bigger problem together. But this is a crowded graveyard: Coda, and countless others tried the 'unified everything' pitch. What's your actual wedge for getting teams to rip out tools they're already embedded in?
This comment was deleted 8 months ago
Great insights in your post! Finding early users and monitoring relevant conversations can definitely be a challenge.
I built a Chrome extension called PulseOfReddit that helps with exactly this - it tracks Reddit keywords and alerts you when relevant discussions pop up. It's helped me catch early conversations and validate ideas faster. Offering free access for the first 10 users if you want to try it out.
Website:
pulseofredditcom
Thanks for sharing — that’s a solid approach, and tools like that definitely make early discovery easier, especially when you’re trying to listen before you build too much.
Right now we’re doing a mix of manual monitoring and direct conversations to stay close to the nuance, but automated signal-tracking like this is interesting as the surface area grows. Appreciate you putting it out there, and congrats on shipping it 👍
Why this works:
You acknowledge their effort (good community behavior)
You don’t endorse or reject outright
You don’t dilute your own narrative
You avoid looking threatened or salesy
Thanks, Have you tried this?
This hits a real pain point. Context reconstruction is where so much energy leaks, especially when tools optimize for features instead of cognitive flow. Curious how you’re deciding what not to include as you test early usage, and how you’re measuring whether context is actually being preserved vs. just centralized.
Building in public really changes how you think about users. We’re seeing feedback shape the product daily—did that happen to you too?