The art of building together
Every useful release starts with observed friction, not a feature checklist.
Built for independent teachers
So we made one: a practical home for courses, community, and the patient craft of helping somebody learn.
Begin with the teacher
Workbench began with a plain observation: people with hard-earned knowledge deserve more control over how they share it. We built the first version alongside seven working teachers, then kept listening.
Read the early field notes →“In the future, useful teachers will sell knowledge, not products.”
Amir Hassan · Founder, Workbench
Study supports belonging
The platform is only part of the work. We test with real cohorts, make space for candid questions, and design tools that let a teacher stay recognizably themselves.
Every useful release starts with observed friction, not a feature checklist.
We prototype in workshops where teachers can pull apart the details and rebuild them with us.
Clear language, generous defaults, and practical support are product decisions.




A core belief
“Transparent work earns durable trust.”
We share what we can, explain what we can’t, and make the tradeoffs visible.
Actions speak louder
The principles are simple enough to remember and specific enough to use.
Quiet voices and awkward edge cases often carry the most useful information.
A strong decision leaves the next person with context, ownership, and room to improve it.
We prefer an honest constraint today to a polished surprise tomorrow.



Meet the people
We are designers, engineers, educators, and operators working across nine time zones with one shared standard: leave the work more understandable.

Learning systems · Toronto

Community · London

Product design · Lagos

Engineering · Austin