Skip to main content
About Equal Horizons

We started with a question we couldn't shake.

Why does assistive technology so often cost more, work worse, and feel more like an afterthought than the technology built for everyone else?

Our story

A small idea, taken seriously.

Equal Horizons began as a conversation between two students who noticed the same pattern from very different angles: assistive technology that could genuinely change someone's daily life often sat out of reach — either priced for institutions, not individuals, or designed without much input from the people actually using it.

Rather than rush toward a product, we started by talking to people — users, caregivers, educators, and advocates — about what actually gets in the way. That research is still shaping everything we do. We'd rather move slowly and build something genuinely useful than move fast and build something that looks good in a pitch deck.

Today, Equal Horizons is a student-founded, early-stage initiative. We haven't launched a product yet, and we're not in a hurry to. We're building the foundation — relationships, research, and a clear sense of what "affordable and accessible" actually requires — before we build anything else.

Founders

The people building Equal Horizons.

MB

Mithilesh Bhasker

Co-Founder

Leads research and product direction for Equal Horizons, spending most of his time listening — to the disability community, to educators, and to the gaps in tools that already exist — before shaping what we build next.

SS

Sahil Singla

Co-Founder

Focuses on how Equal Horizons grows — partnerships, community relationships, and making sure the organization stays accountable to the people it exists to serve.

What guides us

Our values, in practice.

Accessibility first

Accessibility isn't a feature we add later — it's the starting requirement for anything we consider building.

Affordability

Assistive technology only helps people if they can actually afford it. Cost is a design constraint, not an afterthought.

Human-centered design

We design around real routines and real constraints, not idealized use cases that only work in a demo.

Practical innovation

We're more interested in technology that quietly works every day than technology that's impressive once.

Community feedback

The disability community isn't a stakeholder we consult once — they're part of how every idea gets shaped and tested.

Want to be part of the next chapter?

See how to get involved