1
1 Comment

Building in public: testing a different approach to context switching

Over the last few years, my work ended up scattered across Slack, email, Notion, calendars, docs, and project tools. The tools themselves weren’t the problem — losing context between them was.

So I built OMNEX, a workspace that focuses on one thing:
helping you resume work without reconstructing context after interruptions, handoffs, or time gaps.

Not trying to “replace everything” on day one.
The current focus is a very specific moment:

When you come back to work and ask: “what was I doing and what happens next?”

Where we are now
• Working MVP (web app)
• Early access users testing real workflows
• No pricing yet, no credit cards — this phase is about learning

What I’m looking for
• Founders, builders, operators, or remote team members
• People juggling multiple tools and threads daily
• Brutally honest feedback (what’s confusing, useless, or actually helpful)

If context switching drains your energy more than the work itself, I’d love your input.

👉 Early access: https://omnex.tech
Happy to answer questions or share what we’re learning so far.

on January 6, 2026
  1. 1

    Interesting experiment. I’ve noticed with context-switching changes, clarity usually comes less from how it feels and more from what outcome actually shifts.

    Curious — what’s the one signal you’re watching to decide whether this approach is better (speed, fewer dropped tasks, deeper focus, something else)?