Meet the team

A small team out of Boston University who got tired of study tools that did not know what they were studying. We build Sapling between problem sets, and we use it for our own classes first.

Andres LopezFull stackWorks end to end, from the database up through the screens, and keeps the two halves speaking the same language.

Jack HeAI architecture and new featuresDesigns how the agents, the graph, and your own materials fit together, and builds what Sapling does next.

Jose Gael Cruz-LopezFrontendBuilds the interface you actually study in, and the motion and layout that keep it out of your way.

Luke CooperAPI integrationWires Sapling to the services your course already lives in, so your calendar, grades, and files arrive on their own.

Hang NguyenMarketing internRuns the social side and the short-form video, and carries Sapling to the student groups and classmates we would never reach on our own.

How we work

•We use Sapling for our own courses before anyone else sees a feature. If it does not help us pass, it does not ship.

•Every feature has to feed the graph. A tool that knows nothing about what you already understand is a tool we would not add.

•We read every piece of beta feedback ourselves. There is no support queue between you and the people who built it.