Eassa Ayoub
Most software makes users carry its complexity. I build software that feels like thinking— systems that match how humans actually work.
The question is never "is this complex?" It's "WHO carries the complexity?" I vote computer.
It starts with a tap.
Your finger hesitates over "submit" for the thousandth time.
Another spreadsheet. Another app. Another fix.
But the chaos remains.
What if the problem isn't you at all?
What if the software you use daily was built to fight your brain?
That's why I build differently.
Here's the pattern I can't unsee:
Every layer you add is complexity the user eventually carries. Transfer it back to the machine.
Ever seen a grown adult break down over a password reset?
Ever watched someone avoid their CRM like it's a haunted house?
Seen a colleague stare helplessly at a screen overloaded with dropdowns?
Heard someone sigh, "I'm just bad at keeping track of things"—when the real problem is their tools?
Cognitive Overload
Mental exhaustion caused by badly designed systems.
Users take to complete tasks in poorly structured interfaces
When systems overload your brain with tiny decisions
Not because users don't need it—because it's mentally exhausting
This isn't about special modes or accessibility theater. Cognitive ease is just better engineering. If it's easier for the most overloaded user, it's smoother for everyone.
Where the pattern shows up
Same Question,
Different Layers
I don't "add AI." I keep pulling on the same thread and interrogate the system until the unnecessary parts confess. The goal is to collapse the distance between intent and truth. In architecture, fewer hops. In UX, fewer decisions. When the same principle works at different scales, I trust it.
Working memory is finite — Build for that or build friction.
→ CRM rebuild. Max three choices per screen. Decision fatigue gone.
Every abstraction should earn its place — If it can't justify the hop, it goes.
→ Agent memory with real retrieval and decay. No wrapper theater.
These aren't limitations — They're the structure. Encode them and illegal states can't exist.
→ Regulatory rules that compile. Illegal states are type errors.
Let's Build
I'm looking for teams building real systems—or rescuing promising ones from prototype purgatory.
Practical AI Integration
Intelligent features designed to simplify tasks, not complicate them.
Tailored Systems & Workflows
Custom-built solutions that reflect your natural cognitive patterns.
Cognitive Load Reduction
Interfaces meticulously crafted to eliminate decision fatigue.