Will you replace Canvas, Moodle, or our SIS?

Only if you have a written reason those products cannot do the job. More often we integrate and build the missing operations layer. Replacing a campus SIS is a multi-year program we will not hide inside a marketing page.

Do you store student data in a specific certified way?

We follow the hosting and access rules in the contract. We do not claim FERPA certification, WCAG legal certification, or ministry accreditation. Your institution owns policy and DPAs with vendors.

It can draft feedback for an instructor to accept or reject. Unattended high-stakes grading is an academic decision we will not sell as a default. Integrity and appeal paths stay yours.

What about accessibility?

We design for keyboard use, labels and structure. A formal accessibility audit or legal sign-off is a separate scope if you need it.

Can parents message teachers in the app?

Only if that is in scope with moderation and records-retention rules. It is a product decision, not a free chat widget.

Software for the academic calendar, not a generic users-and-dashboards app

Education operations run on cohorts, terms, sections, enrollment statuses, waitlists, add/drop windows, assessment attempts, accommodations, and staff roles that are not “admin.” We build and integrate systems around those objects: LMS-adjacent workflows, registrar tools, instructor consoles and the student-facing surfaces that must stay in sync. We are not an accreditation body, not a student-data regulator, and not a replacement for your academic policies. We encode the policies you can state.

The split: learning delivery versus running the institution

A learning management system is where content, activities and often grades live. A student information or operations layer is where applications, deposits, section assignment, attendance exceptions, transcripts and staff workload live. Many painful “LMS projects” are actually registrar projects wearing a course-shell costume. We start by asking which object is wrong today: the course, the person, the enrollment, or the assessment attempt.

Enrollment is a state machine. Applied, admitted, deposited, registered, leave of absence, withdrawn, completed, each state has documents, payments, and who may change it. If your SIS forces a workaround every term, custom software can own that spine and treat the LMS as a downstream roster consumer via standard interchange (LIS-like APIs, CSV that is actually validated, or LTI where a tool must launch inside the LMS).

Assessments need academic integrity controls you define: attempt windows, randomization, late policies, lock dates, and a clear path for accommodations (extra time, alternative format) that does not require a one-off email to IT. We will not build a “cheat-proof” exam. We will build the workflow so policy is visible and auditable.

Student operations include the unglamorous work: section capacity, instructor assignment, room or virtual-meeting links, certificate issuance, and parent or sponsor portals where those roles exist. Permissions are ferocious: a teaching assistant is not a registrar; a student must not see another student’s assessment.

Problems we see in education operations

Term rollover is a fire drill
Sections are cloned by hand, rosters disagree, and last year’s TAs still have access. You need a rollover job with a checklist, not heroics.
Add/drop lives in inboxes
Capacity, waitlists, and prerequisite checks are tribal knowledge. The enrollment object should enforce them.
LMS gradebook versus registrar of record
Two numbers, one transcript. You must name which system wins and when a grade is official.
Admissions is a spreadsheet plus WhatsApp
Documents, interviews, deposits. A pipeline with statuses beats a shared drive named Final_v7.
Accommodations are tribal
The exam tool does not know the student has extra time. The flag must travel with the attempt.
Certificates and transcripts are desktop publishing
Issuance should hang off completion rules and a number you can revoke or verify.

What we typically build or integrate

Enrollment and student ops
Applications, section registration, waitlists, leaves, and staff queues.
LMS-adjacent tools
Roster sync, LTI tools, instructor grading helpers, and student portals that do not fork the grade of record.
Assessment workflows
Attempt lifecycle, late policies, accommodations, and review, not a new psychometric theory.
Identity for campus-like settings
SIS-driven accounts, role changes at term boundaries, and deprovisioning when a student withdraws.
Parent, sponsor or employer views
Where those relationships exist, with explicit consent and field-level limits.
Growth for programs that sell seats
Landing pages and CRM for continuing education or bootcamps, still no ranking promises.

Use cases

Independent academies and training companies
Cohort-based programs, payments, certificates, and a lightweight LMS or a better skin on one you keep.
Edtech products
Multi-tenant tools for schools: tenancy, rostering, and FERPA-like caution without claiming a certification we do not have.
K–12 or higher-ed departments
A specific pain (clinical placements, thesis tracking, language-lab booking) rather than a second SIS.
Content and video for instruction
Lesson media pipelines with academic review, not unattended AI courses.

How education work is delivered

Discovery with the academic calendar
Map term dates, freeze windows, and who may change a roster after week two. Policies beat wireframes.
Scope one spine
Usually enrollment or a single high-pain workflow (placements, assessments). Do not replace the SIS and LMS in one release.
Architecture
Person and enrollment as sources of truth, LMS as consumer or producer with a written direction, and data-minimization for student records.
Build against a fake term
Staging with realistic add/drop and incomplete grades. Registrars click it before students ever see it.
Launch on a calendar boundary
Mid-term cutovers are how you get split brains. Then iterate on the exception queue that appears in week one.

Questions we hear first

Will you replace Canvas, Moodle, or our SIS?: Only if you have a written reason those products cannot do the job. More often we integrate and build the missing operations layer. Replacing a campus SIS is a multi-year program we will not hide inside a marketing page.

Do you store student data in a specific certified way?: We follow the hosting and access rules in the contract. We do not claim FERPA certification, WCAG legal certification, or ministry accreditation. Your institution owns policy and DPAs with vendors.

Can AI grade essays?: It can draft feedback for an instructor to accept or reject. Unattended high-stakes grading is an academic decision we will not sell as a default. Integrity and appeal paths stay yours.

What about accessibility?: We design for keyboard use, labels and structure. A formal accessibility audit or legal sign-off is a separate scope if you need it.

Can parents message teachers in the app?: Only if that is in scope with moderation and records-retention rules. It is a product decision, not a free chat widget.

Bring the term calendar and the broken object

Is it enrollment, roster sync, assessment attempts, or certificates? Send the systems you already run (SIS, LMS, payments) and the exception that appears every term.

Start a Project