aldenfield

See every child clearly.

Aldenfield isn’t another system to log into. It unites the systems your school already has, so the village can spend its energy on the child.

The problem

A dozen systems, no time, and now AI.

An independent Montessori school runs on a dozen systems that don’t talk to each other, and people are the glue: nearly every dollar goes to staff, and part of every staff day goes to carrying information between systems by hand. Simple questions cost twenty minutes to answer, teachers struggle to find time for record-keeping, and parents are flooded with information yet can’t find the one thing they need. And when a staff member leaves, what they know leaves too.

Now administrators are expected to figure out AI on top of it, with no time, no help, and no budget for any. Careless adoption is its own risk: wire an assistant to file shares where permissions have drifted for years, and it will cheerfully answer from files nobody realized were reachable. The mistake was passive; the AI is active.

Every broken system taxes the same resource: time, the one thing a school cannot raise tuition to buy more of.

The answer

One source of truth, in the tools you already use.

Aldenfield connects everything your school already runs into one current picture, scoped to each role. It adds a governed layer over your systems rather than replacing them, and your staff and parents reach it from the chat tools they already use: Microsoft Teams, Claude, ChatGPT, WhatsApp. It works with whichever AI your school chooses; adopting Aldenfield never means adopting a particular vendor.

Ask it for the policy, the schedule, the allergy list. Answered in seconds, not a twenty-minute hunt across five systems.

Tell it to log an observation, request time off, or update a policy. Recorded where it belongs, so nothing walks out the door.

The practice

Built with your school, not for it.

Software alone does not change how a school runs. Aldenfield ships with an embedded practice: a fractional AI office that learns how your school actually works, chooses each workflow with the people who live in it, and stays accountable for adoption. An engagement can start as a conversation on retainer, before any software at all, and grow only when something earns its place.

The AI landscape will keep moving, and keeping up is the office’s job, not the school’s. Nobody on staff has to become an AI expert in a field that changes monthly; the school rents the fluency instead.

It was built this way from the start: from inside a Montessori school’s operations, by a founder who lives these pain points daily.

The safeguards

FERPA-aligned by design.

  • Students never operate the system.
  • Each role sees only what it should.
  • A person confirms anything sensitive.
  • Every action leaves a trail: who did what, never what was asked.
  • Nothing is ripped out to start. Nothing is held hostage if you leave.

Privacy is the price of admission.

Start a conversation.

For schools: a 30-minute conversation about what you run on and where it hurts. For people building in this space: we like comparing notes.