As builders, it is dangerously easy to fall into the trap of adding "just one more feature." You convince yourself that deeper customisation, endless sub-menus or complex hierarchy trees are what will finally unlock user retention.
In reality most teams don't want more complexity they want less clutter. The biggest productivity killer today isn't a lack of tools; it's the constant friction of switching between chat apps, task trackers, docs and wikis just to piece together daily context.
Right now, I am working in a startup that is building Unified Orbis, an AI-native WorkOS designed to solve this exact problem. We're consolidating core team communication, task management and automated workflows into a single intelligent workspace so teams can cut down on tool sprawl and focus on actual execution without juggling five separate subscriptions.
We're working on Dora Dungeon, a game designed specifically to make gaming more accessible for blind and visually impaired players.
The idea came from a simple question: Why should gaming depend so heavily on what a player can see?
Dora Dungeon uses voice interaction and audio feedback to allow players to navigate and interact with the game in a different way.
We're currently improving the experience and would love to hear from people interested in accessible gaming.
What features would you expect from a game designed primarily for blind players?
We're particularly interested in feedback from gamers, accessibility advocates, developers, and people who have experience designing accessible products.
If you'd like to see what we're building, here's the app:
First, a genuine thank-you: ClawTeams just went #1 Product of the Day and #1 Product of the Week on Product Hunt. A huge part of that came from feedback in this community, the questions, critiques, and edge cases you all raised shaped what we built. So this post is half thank-you and half an invitation to keep going on the harder problem underneath it.
We've been building ClawTeams, an IM-native platform where you describe an outcome to a "team lead" agent and it splits the work across specialist agents that run in parallel, inside the chat tools you already use (Slack, Telegram, WeCom, DingTalk, Lark). I wanted to share what we're working on and get this community's take, because the deeper we get the more convinced I am that the hard problem isn't making agents smarter. It's making a group of them accountable.
We're excited to announce the launch of our Virtual Card feature, designed to solve some of the most common challenges businesses face with shared business cards.
SubmitMap is 294 launch platforms mapped: what each one asks for, what it costs, and how long it takes. Free to read, no signup.
The part I actually care about is the MCP server. Point Claude at it, and it qualifies your product against all 294, picks the ones you'd pass, then hands you the exact brief for that form: every field and the traps that silently kill a run. You press submit, and it records it.
We're building an assessment layer that scores candidates on two things, separately: can they actually do the job (Work-Fit) and will they thrive in how the company operates (Culture-Fit) through one adaptive AI conversation instead of a DSA round and a gut-feel culture interview.
The core idea: before any assessment exists, a hiring manager defines 4-6 things the hire will really do in their first 90 days. That list becomes the rubric. Candidates get a scoped task built from it (PR review, small build, debug), and an AI asks live follow-ups based on what they actually say so a rehearsed answer breaks on question two.
We deliberately skipped personality tests and generic "culture fit" replaced with structured, evidence-based behavioral scoring, because that's what the research (and the hiring leaders we've talked to) says actually predicts performance and reduces bias.
What we don't have yet, and why we're here: a real rubric built with a real hiring manager. We want to co-define the first 4-6 activity list and value set with a handful of companies actually hiring right now not guess at it ourselves.
We re putting together a private 14-day Founding Cohort for Zenor a personal AI tool engineered specifically to help high-responsibility leaders manage daily decision load and reduce context-switching.
