Max Sheahan × Intent Solutions

The education arm, assembled.

Three pieces, one claim: your catalog teaches people to build, and a pedagogy layer would make what they learn stick. This page holds the plan that makes the argument, a module from your own curriculum rebuilt to show the method, and the classroom product that proves I ship.

The whole package runs about forty minutes. The plan alone is twenty.

01 · the argument 02 · the method 03 · the product
01 The argument

An education arm for Intent Solutions

The full case, written after reading your corpus end to end: positioning, both curricula, the session guides, the partner playbook, the metrics. What the program does well, where the learning science is thin, and what an education arm built on both of us looks like. Pricing, engagement models, three partnership structures, risks, and a 30/60/90.

How it fitsThis is the spine. Everything below exists to back a claim this plan makes. Read it first; it is about twenty minutes.
02 The method, shown working

Schema Studio

The plan says your strongest sessions teach by copy-paste, and that the skill never transfers. Easy to say. So I took one module of your curriculum, the 60-minute database session, and rebuilt it: the learner designs the schema instead of pasting it, through modeled construction, supported practice, and a solo build, with a performance task at the end that the original never asks for.

Every phase has a before-and-after toggle showing your original module verbatim next to the upgrade, so the value of the pedagogy layer is visible rather than asserted. And the solo build is coached by Claude, live: a tutor reads the table the learner is designing and responds the way a teacher would, name what is right, name what is missing, point at the next move. The API key sits server-side in a Pages Function; the browser never touches it.

How it fitsProof of method. This is what "pedagogy layer" means in practice, applied to material you already own. Plan to spend fifteen minutes inside it.
03 The product

PANDA

The plan proposes AI for educators as the next rung on your ladder, and that rung needs someone who builds for the classroom. PANDA is that evidence: a behavior-and-academics platform I built as a working middle school teacher and ran with real students, on the same Google stack your curriculum already teaches.

The case for why it matters to this partnership is written up separately. Below it sit the thesis the product is built on, which I will let make its own argument, and the app itself, running on a synthetic classroom: three periods, six weeks of data, no real students.

How it fitsProof of product. The plan argues teachers are the next vertical; this is what shipping for that vertical looks like from someone who stood in the room.

What this builds toward

An education arm with two lanes. The first upgrades what you already sell: the pedagogy layer across the catalog, exit outcomes named for every session, assessment that checks learning instead of activity, and session guides any trained instructor can run, not just you. The second is net new: AI for educators, the vertical neither of us can build alone. You have the delivery system and the audience. I have the classroom, the instructional design, and the product above.

The plan lays out three ways to structure it. None of them require trust upfront; all of them are built so the work proves itself the way this page does, one shipped artifact at a time.

One more thing worth noticing. You shared the corpus at eleven on a Sunday morning. By that night this package was live, the plan, the rebuilt module, and the demos, built with the same tools the curriculum teaches. That is the loop, running.

The ask is simple. Read the plan, walk the proof, and tell me which of the three structures reads right to you. Thirty minutes on a call settles the rest.