8
9 Comments

We tried to reduce context switching by rebuilding our workspace

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

posted toAvatar for product OMNEX
OMNEX
  1. 1

    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.

  2. 1

    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?

    1. 1

      This comment was deleted 8 months ago

  3. 1

    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

    1. 1

      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

      1. 1

        Thanks, Have you tried this?

  4. 1

    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.

    1. 1

      That distinction — preserved vs. centralized — is exactly the line we’re trying not to cross.

      For what not to include, the rule so far has been: if a feature increases surface area without clearly helping someone maintain momentum mid-task, it stays out. A few things we initially assumed were “obvious” additions didn’t survive early use because they added choice and navigation cost without reducing cognitive load.

      On measurement, we’re deliberately staying qualitative for now. We’re watching for signals like how often people have to leave the workspace to answer a simple question, whether they can resume work after an interruption without re-orienting, and how frequently they say things like “I didn’t have to go look for that.”

      Centralization alone is easy; preserving context is harder and more fragile. Early usage is mostly about pressure-testing whether we’re actually helping people stay in flow, or just moving the clutter into one place.

      if Curious, check https://omnex.tech and fill the early access form to receive the link of omnex app (no credit), for any questions feel free to mail us at support@omnex.tech .

  5. 1

    Building in public really changes how you think about users. We’re seeing feedback shape the product daily—did that happen to you too?

    1. 1

      Definitely — and faster than I expected.

      What changed most wasn’t feature priorities, but how we think about the problem. Things we assumed were obvious or “nice to have” turned out to be friction points once people actually tried to use the product in their own workflows.

      Building in public has been helpful precisely because it forces us to slow down, listen, and resist locking decisions too early. It’s less about shipping more, and more about understanding where the real cognitive load is for users.

      if Curious, check https://omnex.tech and fill the early access form to receive the link of omnex app (no credit), for any questions feel free to mail us at support@omnex.tech