Every system starts with someone who refuses to accept the status quo.
That's me.
I'm Abhishek. I build systems. Most of them break.
Current active system: Acuresh. Next experiment: NeuroFlow.
I build systems. Most of them break.
I'm a second-year CS student who decided textbooks weren't enough. Three startups later (two dead), I'm still iterating.
❯abhishek --stats
The track record
Building at the intersection of AI, healthcare, and human systems.
3+
ventures built from zero
Each failure became the foundation for something stronger.
2
design patents secured
IDE architectures that redefine developer workflows.
22+
languages supported in Curalive
Borderless healthcare. No patient left behind by language.
❯abhishek what-i-build
What I build
I build systems that solve real friction instead of chasing shiny ideas.
Healthcare infrastructurethat scales across languages, cultures, and borders (Curalive / Acuresh).
AI execution enginesthat don't suggest—they act. NeuroFlow removes the gap between decision and action.
Developer toolswith patented IDE designs engineered for speed, clarity, and flow state.
❯abhishek philosophy
How I work
I collect failures like assets. Each one builds clarity.
I don't ask "is this innovative?" I ask "does this solve a real, scalable problem?" Every system I build carries the scar tissue of the ones that came before it.
A healthcare platform helping foreign visitors navigate Indian hospitals in 22+ languages. Currently testing with early pilot users to fix the massive friction in medical tourism.
❯abhishek project --detail neuroflow
NeuroFlow AI (In Dev)
An experimental AI workflow tool. Still pre-system. Trying to figure out how to make LLMs execute tasks reliably instead of just generating text.
❯abhishek project --detail neuroskin
NeuroSkin (Concept)
R&D concept for a wearable interface. Strictly an exploration / long-term bet right now.
❯cat about.md
// about.md — the deeper story
About
I am not just a student, developer, or founder. I am a systems builder.
❯abhishek origin-story
The origin
I stopped waiting for the 'right' internship and started building (and breaking) real systems instead.
Most of my learning happens outside the classroom—shipping code, talking to users, watching things fail, and then rewriting them.
I don't build features in a vacuum anymore. I build systems that solve real friction.
❯abhishek values
What I care about
Execution over ideas— Ideas are infinite. Shipping is everything. I'd rather build a broken prototype than polish a perfect pitch deck.
Failure as data— I collect failures like assets. 3+ ventures, 2 failures, each one a compression algorithm for what actually works.
Systems thinking— I don't build features. I build systems. Every component exists in relation to everything else.
Borderless by default— Technology should scale across languages, cultures, and economies without friction.
❯abhishek vision
The vision
I architect the future of how we live, heal, and interact with technology.
Redefining how humans interact with healthcare and intelligent systems through borderless execution. Creating systems where AI is not just a tool, but the primary execution engine of human intent.
Building borderless solutions that scale across languages, cultures, and economies without friction.
❯cat notes.md
// notes.md — thinking out loud
Notes
Fragments of thinking. Unpolished, raw, honest.
❯ls notes/
2024.08
On building in public while still learning
The tension between being a student and being a founder is not a bug—it's the feature. Every textbook concept gets immediately stress-tested against reality. Theory meets execution every single day.
2024.06
Why I stopped calling myself an "entrepreneur"
The word has been diluted to meaninglessness. I build systems. I architect infrastructure. I solve problems. Labels are for LinkedIn. Execution is for the real world.
2024.03
Failure taxonomy: a personal framework
Not all failures are equal. Some are noise (bad timing, bad luck). Some are signal (bad assumptions, bad execution). Learning to distinguish between them is the entire game.
2024.01
The finder = minder + grinder equation
My personal operating formula. A finder sees opportunity. A minder manages risk. A grinder executes relentlessly. You need all three. Most people are one. I'm training to be all three.
❯cat contact.md
// contact.md — let's talk
Contact
Got a project, an idea, or just want to talk systems? I'm always up for a good conversation.
Reach me
Every message lands directly with me. No gatekeepers, no middlemen.