Studio

Building things that help people learn and work better.

The studio is where the work gets made — curriculum, tools, workshops, and the infrastructure that supports all of it.

Start with the learner

The best learning products are designed around what people are trying to do, not around what's easiest to teach. We build from that constraint — it makes harder problems and better outcomes.

Outcome-driven design Tested with real learners

Build in the open

Curriculum that's locked in a product doesn't improve the way open curriculum does. When possible, we publish our work openly so it can be used, forked, and made better by everyone who touches it.

Open source by default Community-driven improvement

Ship, then improve

Waiting for perfect is how learning products die in a drawer. We build things that are good enough to be useful, put them in front of real people, and iterate from actual feedback.

Working beats perfect Feedback-driven iteration

What we're building

Live

Workshops

Live, hands-on training for teams and individuals. Currently focused on AI for business and engineering — how to use it in your actual work, not just in demos. Delivered as open enrollment or private team sessions.

View workshops →
Live

Fractional leadership

Embedded engineering leadership on a part-time basis. Jeff works directly with your team — in standups, with your people, reviewing your systems — without the cost of a full-time hire.

Learn more →
Building

OpenMath

An open source curriculum project for math education. Built to be free, forkable, and adaptable — so teachers and schools can take it, customize it, and make it work for their students. Still in active development.

Coming soon
Building

Open source tools

Small tools, utilities, and infrastructure that come out of building everything else. When something's broadly useful, we open it up. No grand plan here — just a bias toward publishing the work.

On GitHub

How we think about building

Every project in the studio starts with the same question: what does the person on the other end of this actually need to be able to do? Not "what can we teach" or "what do we know" — what do they need to walk away able to do?

That sounds simple, but it changes everything about how you design a workshop, build a curriculum, or structure a coaching relationship. It means saying no to a lot of interesting material that doesn't serve the outcome. It means building slower and testing earlier. It means the product is never really done.

We also believe strongly in publishing. Most of the work we do gets better when more people can see it and use it. That's why OpenMath is open source, why we share curriculum frameworks, and why we write about what we're learning. The studio is a workshop, not a vault.

Interested in building something together?

If you have an idea for a learning product, a curriculum project, or just want to talk about what the studio is working on — reach out.

Start a conversation →