I think I found my wedge. I also think I might be fooling myself. Help me find out.
Posted AETHR here a while back. You tore it apart, 75 comments and the one that stuck was "useful later, not now."
So I went back to the codebase and rebuilt it around one thing: you paste a messy brain dump and it auto-sorts the tasks, goals, and metrics out of it. No setup. Dump and go.
Now I've convinced myself the wedge is cognitive unload.
People are completely exhausted by manual administrative work and data entry. We are moving into the era of agentic workflows, users don't want to spend mental energy deciding which folder a task belongs in or manually stringing together heavy API integrations. They want the system to decide for them. I want AETHR to stop competing with Notion or Asana, and instead be the autonomous, agentic ingestion layer that feeds them.
If this is the right wedge, the endgame isn't to build another app you have to manage, it’s to make it so you barely have to open AETHR at all because your voice notes, forwarded emails, and raw Slack clips just ingest and route themselves automatically.
Here's my problem: I can't tell if that's a real insight or just a story I'm telling myself because I already coded it. Founders are dangerously good at rationalizing the thing they already built.
I became certain this was the wedge last week. Now I've convinced myself the wedge is cognitive unload, So I'm not asking you to validate me. I'm asking you to try to break the thesis:
https://getaethr.vercel.app/
Paste your ugliest, most chaotic pile of notes and tell me if the auto-routing felt like an actual agentic workflow, or just a gimmick.
If it's a gimmick, say so plainly. That's more useful to me than a like.
And the real question: is "cognitive unload" via agentic ingestion actually the wedge, or am I just one more founder in love with my own demo?
The wedge might be real, but I would be careful with the phrase “cognitive unload.”
It sounds intelligent, but it may be too abstract for the user who actually has the pain.
The sharper test is probably not whether people like auto-routing. It is whether they already have a repeated dump-point where tasks, goals, metrics, notes, emails, and Slack fragments pile up and become mentally expensive to sort.
If that moment is real, AETHR has a wedge.
If the user has to invent a new habit just to use it, then it risks becoming another productivity layer.
I’d pressure-test the thesis around one question:
“What messy input do people already create every week that they hate organizing afterward?”
Voice notes after meetings, messy founder notes, forwarded client updates, Slack brain dumps, research notes, sales call notes. One of those probably has to become the first wedge.
Happy to put a tighter version in writing if useful. I’d map the wedge risk, first user segment, positioning, and the simplest validation test before you build more around the thesis.
This is an incredible pushback, and you hit on exactly why I felt like I might be fooling myself. You’re 100% right "cognitive unload" is a product-builder's abstraction. Nobody walks around actively looking for an app to unload cognitively. They just want their mess sorted.I built this parser to stop the pain of sorting that specific note.
But you’ve named the huge risk: if the user has to invent a brand new behavioral habit just to use AETHR, the product becomes homework again and it dies.
I would absolutely love to take you up on your offer. If you're willing to put it in writing, how would you map out that simplest validation test to find out which of those existing dump-points (voice notes, messy founder scraps, forwarded client emails) is the actual highest-pain wedge worth betting on?
Yes, this is exactly the part I’d put in writing rather than try to answer loosely in the thread.
The useful thing is not just picking voice notes vs founder scraps vs forwarded emails. It is mapping which one already has enough pain, frequency, and willingness to change behavior.
Drop your email and I’ll send over the tighter version. I’ll keep it focused on the wedge risk, first user segment, positioning, and the simplest validation test for AETHR.