1EDU.app

A whole technology office, for schools that can't hire one.

Small educational institutions run on spreadsheets, memory, and one overworked administrator. 1EDU is the operating platform that replaces the patchwork — with AI working the desk.

Start with an assessment →

No demo gauntlet, no sales tour — an honest assessment decides what you need before anything is sold.

Cutaway illustration of a small schoolhouse, each room a working department
Fig. 1 — the institution in cross-section: every room a working department, every department one system.

In this platform

01 Advancement

Donors, grants, and the CRM — the whole development office in one view.

02 Learning

Staff training, knowledge base, and video — with expiry-aware certifications.

03 Curriculum

Versioned units mapped to outcomes; the accreditation evidence pack, always current.

04 Operations

SOPs, forms, automations, and documents — how the school actually runs.

05 Reporting

KPIs and board packets computed from the record, not rebuilt for it.

06 AI

Grant drafts, policy watch, and a staff assistant that cites its sources.

The assessment decides which you need →

№ 02 — The Method

Assess your needs.
Then choose your software.

Every engagement begins the same way: we sit with how your institution actually works, and we write it down. What comes back is not a sales pitch — it's a plan.

Line illustration of a surveyor's folded map with a plotted route
  1. Current-state technology assessment
  2. Business process assessment
  3. AI opportunity assessment
  4. Systems architecture — current and target
+ 6 more deliverables in every full engagement
  1. Software recommendations, alternatives included
  2. Implementation priorities
  3. Integration plan
  4. Budget estimates in ranges, not false precision
  5. Multi-year technology strategy
  6. Board-ready executive summary

If the roadmap recommends our platform, you'll see the scoring that got it there. If it recommends someone else's — or keeping what you have — it says so. The fee is never contingent on choosing us.

Request an assessment

Two minutes of quick questions — it makes the first conversation twice as useful.

Reading your answers...

One more thing

Received

Thank you — your answers are already shaping the assessment. A person (not an autoresponder) will reply to set up a scoping conversation.

GET /.well-known/1edu.json — a live response, generated from platform config:

{
    "name": "1EDU",
    "tagline": "The technology office for small educational institutions",
    "api": {
        "base": "https://1edu.app/v1",
        "access": "private",
        "intake": "https://1edu.app/v1/intake"
    },
    "modules": [
        "advancement",
        "learning",
        "curriculum",
        "operations",
        "reporting",
        "ai"
    ],
    "mcp": {
        "endpoint": "/mcp",
        "status": "live",
        "transport": "streamable-http",
        "auth": "Bearer token (same ApiClient tokens as the REST API)"
    },
    "how_to_get_access": "Provisioned with an engagement \u2014 start with an assessment."
}
  • AVersioned REST at /v1 — anything you can click, your systems can call.
  • BAgents drive the same surface over MCP: same permissions, every action audited.
  • CYour data exports whole — CSV, PDF, JSON. Leaving is a feature, not a fight.

General notes

  1. Every capability exists as a versioned API before it gets a screen — the interface is a client, never a cage.
  2. This sheet describes itself: the manifest at left is served live by the platform it documents.
+ 2 more notes
  1. The MCP surface ships alongside the API, so the assistants your staff already use can drive the same records.
  2. Tenancy is per-institution, never per-seat — the whole staff works, the price doesn't move.
Project1EDU Platform
Drawn byJ. Connor
Date2026.08
RevA
ApprovedPending your assessment