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
Trending on Indie Hackers
The AI cold email gap is almost always context, not quality. LLMs write grammatically correct emails all day. What they can't automatically do is know the recipient just published something, raised a round, or shipped a feature worth referencing.
Workflows that actually work: AI for template and tone, structured research for the specific hook. Maybe 30% research, 70% drafting automation. The research is where the ROI is.
What's your research input process before AI drafts the email?
The AI cold email gap is almost always context, not quality. LLMs write grammatically correct emails all day. What they can't automatically do is know the recipient just published something, raised a round, or shipped a feature worth referencing.
Workflows that actually work: AI for template and tone, structured research for the specific hook. Maybe 30% research, 70% drafting automation. The research is where the ROI is.
What's your research input process before AI drafts the email?
Hey
Really like the clarity vision behind OMNEX.
While exploring the site, I noticed something interesting:
The concept is strong, but it’s still a bit hard for first-time visitors to immediately understand WHO it’s for and how a team would actually use it day-to-day.
Most early SaaS products struggle with this stage — positioning before traction.
I help early founders gather structured user feedback and identify conversion gaps before launch.
If you’re open, I’d love to share a short outsider feedback breakdown.
Appreciate the thoughtful feedback. You’re right — positioning before traction is the hard part. The core idea behind OMNEX isn’t replacing tools like Slack or Docs, but reducing the context switching between them by bringing the work and conversations around it into one flow.
I’d definitely be interested in seeing your outsider feedback breakdown — always helpful to get a fresh perspective at this stage.
My feedback is mainly around polish of your ui/ux. The site on mobile has a lot of rough edges where things don’t quite lineup or are hidden.
"This looks very interesting, the problem of tool overload is definitely real. I'm also building a tool for nomads called NomadLife and I'm looking for some early feedback/user testing too. Maybe we can help each other out and exchange some thoughts on our projects?"
looked at the site... the problem you're describing is real, everyone i know drowns in context switching between tools. but honest feedback: the landing feels like it's talking to enterprise and the post feels like you're talking to solo builders like us. those are pretty different people with pretty different pain
what's the actual first thing someone does when they log in? that would help me understand if it's for me or not
What specific outcome would prove you're solving the right problem?
The OMNEX early stage vibe reminds me of how I wasted 8 months building a SaaS with no paying customers because I didn’t pressure-test the problem.
Focus on solving the core problem of decision clarity and accountability, not just tool overload. Ask your testers what decisions they didn’t have to re-explain. Don’t try to be everything to everyone; you’ll end up competing with giants like Notion.
How are you currently validating that the problem you're paying for is the one people pay to fix?
Modar : this is thoughtful work, and you’re clearly reacting to a real pain. Context switching isn’t just annoying; it quietly erodes decision quality over time.
One thing I’d encourage you to pressure-test early isn’t feature completeness, but what problem you’re actually anchoring on.
From your site, there are two different problems intertwined:
• Fragmentation of tools
• Fragmentation of ownership and decisions
Those aren’t the same buyer moment.
Teams don’t usually wake up saying “we need fewer tools.” They wake up when:
– decisions get revisited because context is lost
– accountability blurs across Slack, email, docs
– leadership can’t trace why something happened
If OMNEX becomes “another place everything lives,” you risk being evaluated against Notion / ClickUp / Linear.
But if OMNEX becomes the system of record for decisions and ownership, that’s a very different category and a much more painful problem to replace.
For feedback sessions, I’d suggest asking testers:
What decision did you not have to re-explain this week because of OMNEX?
If that answer is clear, you’re onto something real.
It may help, you need good ads budget or keep it free for a while. Try to make it lightweight, slack uses minimum 2GB of memory everything is scattered but people are used to some tools, so take best loved parts of every tool
Looks really polished visually, nice work. The scrolling feels a bit laggy.
I’m struggling a bit with the “why” though. Most teams are already deeply embedded in tools like Microsoft Teams and Outlook or Google and Slack. Those tools are trusted, integrated, and hard to replace. Introducing another all-in-one tool means extra "risk", setup, and behavior change.
From the website, it’s not clear why this should be used instead of the existing stack or who this is really built for.
The data retention limits also feel like a dealbreaker for many business use cases.
Context switching is definitely a real problem. I just don’t yet see why this would be the solution teams choose.
Totally fair pushback — and thank you for being that direct.
On the “why” / switching risk: OMNEX isn’t meant to replace Teams/Slack/Outlook/Gmail. The bet is narrower: when you get interrupted (meeting → ticket → Slack thread → doc), teams lose where they left off and why a decision was made. OMNEX tries to be a re-entry screen that reconnects the pieces (task + doc + chat thread + decision + next step) so you spend less time hunting and re-reading. If it doesn’t reduce time-to-reorientation in real workflows, it’s not worth adopting — that’s exactly what we’re validating.
Laggy scrolling: agreed — that’s on us. If you can share what device/browser you were on, I’ll reproduce it and fix it.
Data retention: also a valid concern. Current limits are a beta constraint, not the end state. The plan is configurable retention by workspace (including “keep everything” for orgs that need it), but I don’t want to hand-wave it — if retention is a hard blocker for your use case, I’d love to know what minimum policy you’d require (e.g., 90/180/365 days, or unlimited).
If you’re open to it, I’d love your honest take after a quick look: https://omnex.tech → early access form, then you’ll get the app link. Even 5 minutes of “this isn’t clear / this won’t work because…” is gold.