Teachers who learned to code — not the other way around.
Slate House started in classrooms and training rooms, not a venture studio. We became software engineers because we wanted better infrastructure for the educators we already respected.
A humble origin
We have spent years as teachers and instructors — leading sections, designing workshops, and supporting learners who showed up tired, curious, or both. That work mattered to us long before we wrote our first API route.
When we moved into software, we did not leave pedagogy behind. Instructional design is not a buzzword on our site; it is how we think about sequencing content, writing clear outcomes, choosing assessments, and making sure free material genuinely helps someone decide whether to go deeper.
We are still relatively new as engineers. We will not pretend otherwise. What we bring is years of standing in front of rooms (and Zoom grids) watching what helps people learn — and a stubborn belief that independent educators deserve tools built with that same care.
Educators first
Engineers second — and still learning
Built in the open
Small team, no ivory-tower pretense
Slate House is our attempt to give independent professors the subscription model, discovery, and publishing stack that creators in other fields have had for years — without asking them to compromise on how they teach.
How we got here
Before Slate House
We taught in classrooms, workshops, and online cohorts. We wrote syllabi, ran labs, graded at midnight, and cared deeply about whether students actually understood the material.
The gap we kept hitting
Brilliant educators were stuck behind institutional paywalls or generic course platforms that treated content like files, not learning experiences. The tools did not match the craft.
Learning to build
We are not career startup founders. We picked up software engineering because we wanted to solve a problem we had lived — not because we had a pitch deck. We are still learning, and we build in public about that.
Why Slate House
A place where independent professors own their audience, set their prices, and publish work shaped by real instructional design — not just upload-and-forget video libraries.
Instructional design, for real
We have designed curricula, run train-the-trainer programs, and rebuilt courses when the data (and the students) told us something was not working. These principles shape the product.
Learning objectives first
Every feature starts with a question: what should the learner be able to do after this? We design backward from outcomes, not forward from features.
Scaffolded progression
Free previews, tiered access, and sequenced content are not paywall tricks — they are how adults actually learn. We built the platform around that rhythm.
Multiple modalities
Video, text, PDFs, quizzes, and discussion belong together. Good instruction meets people where they are; our tools reflect that.
Feedback loops
Comments, forums, and analytics exist so educators can see what lands and adjust. Teaching is iterative; the product should be too.
The ivory tower, opened — carefully
We are not here to replace universities or declare the end of tenure. We are here because many extraordinary teachers will never have a lecture hall again — and many curious students will never sit in one. They still deserve thoughtful instruction and a fair way to support the people who provide it.
If that resonates — whether you want to learn or to teach — we would be glad to have you on Slate House.
Join the community
Explore independent educators or start sharing your own expertise. We built this for people like you.