I stopped trying to organize my work and built something that deletes the clutter.
I kept hitting the same issue: Too many open thoughts, and no way to force myself down to what actually mattered that day. Every tool I reached for gave me more room to organize and more ways to avoid the work. I'd spend the day building the system instead of doing the thing.
So I stopped looking for a better organizer and built the opposite.
Overmind is an intent based execution engine. Everything you're carrying in the mind gets unloaded and based on whether each one of it is executable today, it either goes into a Crucible that holds exactly three things and hard-rejects a fourth or goes to the Void, where it's permanently deleted in 72 hours. No folders, tags, streaks, or progress charts to farm dopamine from. You get in, pick what matters, execute, and leave.
The bet underneath it: decision fatigue and analysis paralysis aren't character flaws, they're what an overloaded environment outputs. Remove the environment carrying the infinite canvas, the 40 half-decisions, random thoughts, and the paralysis has nothing to feed on.
I'm a solo builder, on a strict runway, building and testing every mechanic on myself first. V0 works and it's pre-launch now: the waitlist is open, and I'm offering 70 lifetime founding seats to fund the rest of the build for people who actually live this problem. I don't need a lot of buyers, just a few handful people who understand what it is and be the early believers.
Genuine question for this crowd, because it's the thing I'm still pressure-testing: would permanent 72-hour deletion feel freeing to you, or make you anxious? That single reaction tells me whether the core bet holds.
For anyone who wants to pre-register or read about it.
Here's the link: https://overmind.caelvyn.com/?utm_source=indiehackers
I think the anxiety may depend less on deletion itself and more on where the item came from.
I would happily let many of my own passing ideas disappear after 72 hours. But I would be much more nervous about deleting something that originated in an email, a client conversation, or a promise made to another person - even if it is not actionable today. Those items carry a social cost, not just cognitive clutter.
So perhaps an interesting thing to observe is not only what people rescue, but what kind of commitment they rescue. If users consistently let self-generated thoughts disappear but save externally created obligations, that distinction might help define where the product’s boundary should be.
Yes, you pointed out the correct thing, if the important thoughts or commitments that aren't yet actionable are deleted too with the same weight as idle unnecessary ones, that is something to look for. But currently in this MVP module it's purely an execution engine derived on logic, formulations to certain constraints in it and meant just to get your work done. Though I'm definitely working on a way to fix this within the boundaries of the product. Appreciate your reply.
The Crucible holding exactly three things and hard-rejecting a fourth is the part I'd bet on. Most tools let you keep everything and just reorganize it, which is why the pile never actually shrinks. I'm the founder of FounderFlow, similar bet, except my constraint is across businesses instead of thoughts, it only surfaces 2-3 things across everything I run that actually need me today. On your question, permanent deletion would make me anxious for anything tied to a real commitment, but for open loops that are genuinely just noise, I think it would feel like relief within a week.
It's amazing to hear someone else using a similar core architecture in a different domain, you got the active working capacity right and the deletion of important commitments is an active signal i'm receiving and working on. Good luck for your project!
Appreciate that, good luck with the founding-seat launch. The anxious-for-real-commitments/relief-for-noise split you described is a good gut check to build against.
The 72-hour rule will feel freeing only if capture is cheap and triage can happen later. Otherwise people will keep things because recreating the thought feels expensive. That is part of why I built DictaFlow: hold a key, say the thought, release, and it lands wherever I am already working. I would test whether people trust the delete rule more once they can capture an idea in five seconds without opening the system.
The 72 hour deletion doesn't make me anxious. It makes me question whether the deletion is targeting the right thing.
Some tasks deserve to disappear because they were never important. Others survive simply because they depend on timing, another person, or information you don't have yet. Deleting those creates unnecessary friction.
I'd pay close attention to what people try to rescue before the timer expires. Those patterns will tell you whether they're losing valuable work or just struggling to let go of low value ideas. That behavior is probably a stronger validation signal than asking whether deletion feels scary.
Most productivity software assumes that better organization solves overload. More folders, labels, dashboards, and systems are added until managing the system becomes another task.
Removing unnecessary information may be more valuable than organizing it. Completed tasks, expired notes, duplicated files, forgotten projects, and low-priority notifications quietly consume attention even when they are no longer useful.
The main challenge is trust. Automatic deletion feels dangerous unless every action is transparent and reversible. A temporary archive, clear rules, and an easy recovery option could make the experience feel safe.
A strong product in this category would not promise perfect organization. It would promise a workspace where only relevant work remains visible.
You've got the core of it. Clutter competing for attention is the tax you pay without knowing it. The more that sits on screen unfinished, the less you actually execute.
On the archive though, it's a poison offered as the cure. The problem was never that things got deleted, it's that too much is entering a mind with limited processing capacity, and that overload is what drives the paralysis. An archive doesn't remove that, it relocates it. Now you've got a second place to monitor, second-guess, and pull things back from, which is the exact loop you were trying to close. Appreciate the comment though, it shows that you understood the concept.
This direction is more interesting than building another productivity system that asks users to categorize everything perfectly.
Most people do not struggle because they lack folders, labels, dashboards, or task-management methods. They struggle because the amount of information entering their workspace is greater than their ability to process it. Every new organization feature can eventually become another thing they must maintain.
A product that removes irrelevant information, closes completed loops, archives stale items, and highlights only what requires attention may provide more value than one that simply creates a cleaner structure for the same amount of clutter.
The difficult part will be trust. Users may hesitate to let software delete or hide information unless they understand the rules and can recover mistakes. A reversible approach, such as temporary removal or an automatic archive, could make adoption easier.
The strongest promise may not be “organize your work better.” It may be “open your workspace and immediately know what deserves your attention.”
How does the product decide what is clutter without accidentally removing something important?
In the current version, the key thing is nothing here auto-deletes, and the system never decides what's clutter, you do. You dump everything out of your head, promote only what's actually actionable today, and whatever you didn't promote you've already decided isn't for today. So the software never judges importance, it just holds the line you drew based on your intent.
The 72 hours is a countdown space. One window to pull something back if today's triage was wrong or you've got more than 3 to execute after previous are finished, then it's gone. It was never built to hold your thoughts, notes and managers already do that. This just gets the exhausting weight out of your head so you can actually start working.
The interesting bet isn't limiting people to three active tasks—it's treating deletion as a feature instead of a failure. I'd keep validating whether users ultimately adopt Overmind because it helps them prioritize better or because permanently removing low-value commitments changes how they think about work altogether. That's a much harder idea for competitors to copy than task limits alone.
You're pointing at something real. The bet isn't the three-slot limit, it's treating deletion as the feature. Task limits are copyable. "Letting go changes how you work" isn't.
Exactly.
The interesting validation will probably be whether users describe the value as "I can manage my tasks better" or "I stopped carrying things that were never important enough to keep."
The language they use will tell you whether Overmind is a productivity tool or a different way of thinking about commitments.
Permanent deletion would feel freeing only if it does not force a shadow backup. I would test hard-delete against a cohort with one-click weekly export and measure two things: rescue rate and duplicate capture elsewhere. If hard-delete users keep a second notes app, the anxiety has not disappeared; it has moved.
Your comment is appreciated and you're right, the rescue rate plus duplicate capture are the two numbers I do care about. If people keep a second notes app, the anxiety didn't disappear but moved to another place. But that's the argument against a built-in archive, not for one. An archive is that second app, just wearing my label, the clutter walks right back in through the recovery door. So the test isn't hard-delete vs. archive. It's whether the anxiety is real once you've used it, or just anticipated before you have. That's a beta question, measured on those exact two metrics.
Fair distinction. Then the useful beta split isn’t archive vs. delete; it’s anticipated anxiety at signup versus rescue and duplicate-capture behavior after a week. If the first is high and the second low, the 72-hour rule is probably an onboarding problem. If both stay high, it’s a product constraint.