The student platform for Montessori schools
Their work. Their plan. Their record.
Waypoint is the student platform built for Montessori schools, starting with adolescent programs. The student builds the plan, keeps the record, and assesses the work. The guide observes, confers, and countersigns.
The problem
Your program runs on ownership. Your software runs on compliance.
Montessori adolescent programs run on real work: self-directed study, occupations, micro-economy businesses, seminars, community responsibility. And most of them manage that work in Google Classroom.
Google Classroom is honest software. It was built for a different model of school, and it does that job well: the teacher assigns, the student submits, the teacher grades. But run an adolescent community on it and the tool contradicts the guide every day. You own this work, says the adult. Await your next assignment, says the screen. Compliance architecture cannot carry a pedagogy built on ownership.
The assignment pipe
- The adult assigns. The student complies.
- The record belongs to the teacher.
- Grades close every loop.
- Work exists because it was assigned.
Waypoint
- The student sets the plan. The guide countersigns.
- The record belongs to the student.
- Self-assessment against a progression. No grades.
- Work exists because the student committed to it.
A waypoint is a reference point a traveler sets for themselves along a route. That is what this tool holds: the student's own fixed points, not the adult's assignments.
The product
Five rooms in the student's workspace
Everything below is live in the demo, seeded with a fictional school. Click through it yourself. It takes two minutes to feel the difference.
01
Work Plan
The student sets the week. The guide countersigns it.
Goals, commitments, occupation shifts, seminar prep: the student writes the plan on Monday and answers to it all week. A stuck student flags the item instead of hiding it. The countersignature means the guide has seen the plan and stands behind it, not that the guide wrote it.
02
Journal
A working record with real reflection, not busywork.
Adolescents will write honestly about their work when the writing belongs to them. The student decides what the guide sees. Shared entries become conferral threads. Private entries stay private, and no adult platform ever reads them.
03
Projects & Seminars
Preparation, sources, roles, readiness.
A seminar works when everyone arrives prepared, and readiness should be visible before anyone walks in. Roles rotate, questions are drafted in advance, and a project board holds the long work: the hypothesis log, the sampling schedule, the thing the team owes each other by Friday.
04
Occupations
Real responsibilities and real numbers.
The micro-economy is not a simulation, so the software cannot be one either. Shifts, a ledger with actual dollars, and the decisions a crew has to make when the sourdough sells out by ten: raise the price or bake a third batch. The numbers are the curriculum.
05
Progress
Self-assessment against a Montessori progression. No grades anywhere.
The student marks where they are in each domain, attaches evidence, and declares when something is ready to show. The guide countersigns the claim or confers about the gap. There is no gradebook in Waypoint. There is no percentage hiding behind a setting. It does not exist.
Built in plane order
The interface expands as the child does
Waypoint's deepest design rule comes straight from the four planes: freedom within structure, expanding with development, expressed in software. Not a maximum-engagement design at any age.
Now
Adolescents
The full workspace: work plans, journal, seminars, occupations, self-assessment. Student-owned, guide-countersigned. This is what the founding cohort is building with us.
Next
Upper Elementary
At the second plane's end: a work plan, a journal, and the tools for going out and student-led conferences, guide-mediated. The child's first waypoints, set with an adult beside them.
Never
Before the second plane
Deliberately not child-facing. The younger child's record can live in the system, but the interface at that age belongs to the guide. That is what MMAP and MMAS already are. By design, not by omission.
A record that begins with the guide at six becomes a workspace the student owns at sixteen.
The guide's side
Observation first. Nothing to grade, everything to see.
The guide's view is not a control panel. It is a prepared environment for observation and conferral: who has shared, who has flagged, whose plan is waiting for a signature, whose silence has gone on a week too long.
- A conferral feed Journal shares, flagged commitments, and progress claims arrive as invitations to confer, not items to score.
- A countersign queuePlans and readiness claims wait for the guide's signature. Signing means: I have seen this, and I stand behind it.
- Synced to MMAP Progress summaries and records flow to the adult platform, so school records live where school records live. Students never touch MMAP, and what a student marks private never leaves their journal.
Privacy as design
A work tool, not a surveillance tool
Software for adolescents earns trust by its architecture, not its policy page. Here is the stance, plainly:
- A separate platform from MMAP, with separate student accounts. Students never touch the adult system.
- Built for FERPA and COPPA compliance through school agreements. The school is the client. The family signs nothing with us.
- No ads. Ever. There is no version of this where ads appear.
- No social feed. No likes, no followers, no streaks.
- No peer-to-peer messaging.
- No data sold, no data mined, no engagement metrics on children.
- School-provisioned accounts. No personal email required from any student.
- The work belongs to the student and the school. When a school leaves, the records leave with them.
The journal a fourteen-year-old keeps about her own work is hers. Building software that honors that sentence is the whole job.
Design partners
We are building Waypoint with three to five adolescent programs
Not beta testers. Design partners. Programs whose guides and students will shape what gets built, in exchange for terms that honor the risk of going first.
Founding pricing, locked permanently
The price you set with us is your price for as long as your school runs Waypoint. Not introductory. Permanent.
Direct input on the build
A standing line to the people writing the software. What your guides need shapes what ships next.
Named as a founding school
With your permission, your program is named as a founding school of Waypoint. Your practice, credited.
Questions
Asked and answered
How does Waypoint relate to MMAP?
Waypoint is a separate platform in the Montessori Makers Group family, and an add-on for schools that run MMAP, the Montessori Alignment Map. The connection between them is a narrow sync: progress summaries and records flow to MMAP so school records live where school records live. Student accounts are separate, student journals stay in Waypoint, and students never touch the adult platform.
You do not need MMAP to use Waypoint. If you have it, the two work as one system with a clean wall between the student's workspace and the school's records.
What ages is Waypoint for?
Waypoint is built in plane order. Adolescent programs get the full workspace now, and the founding cohort is adolescent programs only. Upper elementary comes next: work plans, journals, going-out planning, and student-led conference portfolios, mediated by the guide. Before the second plane, Waypoint is deliberately not child-facing at all. The younger child's record can live in the system, but the interface at that age belongs to the guide. That is a conviction, not a gap in the roadmap.
What does it cost?
Design partners set the founding price with us, and that price is locked permanently for their school. General pricing will be published at launch. We will not do the thing where the price is a sales call.
What does Waypoint replace?
The assignment pipe. Google Classroom, the LMS, the shared-drive-and-spreadsheet system holding your work plans together. It does not replace the guide, the conference, the seminar, or the community meeting. Software that tries to replace the guide has misunderstood the pedagogy at the door.
When can we start?
The design partner cohort comes first: three to five adolescent programs building with us directly. General availability follows. If you want the earliest possible seat and a voice in what gets built, apply as a design partner. Otherwise the waitlist is the honest answer, and we will write when it is your turn.
Do students need email addresses?
No. Accounts are provisioned by the school. No personal email is required, and Waypoint never asks a student for one.