Industries · Education

The school is growing. The paperwork is growing faster.

Could you pass an accreditation audit next week, without a scramble?

Custom school-operations software for multi-campus networks, microschools, and independent education: student records, compliance, audits, and the administrative layer generic SIS platforms don’t model.

Already running Alma, PowerSchool, Gradelink or another SIS? Keep it. We build the workflows around it: personalized learning records, attendance across sites, family communication and network reporting that connect to the system you already pay for.

IMC
MICROSCHOOL OPERATIONS PLATFORM LIVE SINCE AUG 2026 · AI LAYER IN DEVELOPMENT
CES
10 CAMPUSES · 1,200+ AUDITS · PREP FROM DAYS TO UNDER FOUR HOURS
Your SIS stays
INTEGRATE, EXTEND OR BUILD AROUND IT, NOT RIP-AND-REPLACE

SINCE 2012 · VETERAN-OWNED · SDVOSB + HUBZONE CERTIFIED · SAM REGISTERED · US + INDIA

Quick answer

Logic Square builds education operations software for school networks, microschools and independent schools: the workflows a student information system does not hold, connected to the SIS you already run. Three kinds of work. Integrate what exists, so enrollment entered once in your SIS reaches the tools staff use every day. Extend what is missing, a module or an automation added to the system you have. Build a dedicated operating layer when the learning model, cross-campus roles and family view need one record the SIS cannot hold. We built Commons, the operations platform the Indiana Microschool Collaborative runs across five schools, and the audit workflow CES Academy runs across ten campuses. Replacing a working SIS is the last option, not the first.

EDUCATION / GROWTH vs THE ADMINISTRATIVE LOAD ENROLLMENT: GENTLE PAPERWORK: STEEP AUDIT-TRAIL RAIL: LOAD FLATTENS STRUCTURED RECORD ENTERS WITHOUT A SYSTEM, ADMIN OUTGROWS THE SCHOOL; WITH ONE, PREP DROPS DAYS → HOURS

FIG. 01 / Growth is gentle; paperwork is steep. A structured audit trail is what bends the second curve back down.

01 / The domain

The record your software forgot.

Non-traditional schools, microschools, multi-campus networks, hybrid and mixed-age models, usually have a student information system that does its job: enrollment, the official record, state reporting. The trouble starts around it. Learner goals and evidence live in a spreadsheet or a second app, attendance for the pod is taken somewhere the SIS cannot see, parent updates go out from three inboxes, and the network office reconciles sites by hand every month. The system of record is fine. The system of operations is a patchwork, and the patchwork is what an accreditation audit, a scholarship reconciliation or a second campus exposes.

When the model is the differentiator, that gap isn’t cosmetic. The very things that make the school distinctive (the cohort structure, the multi-site rules, the state-program paperwork) are the things the generic SIS refuses to hold.

02 / Operational realities

Where the load piles up

  • Attendance and records fragmented across sites, models, and spreadsheets.
  • Accreditation evidence assembled by hand, under deadline, every cycle.
  • State-program and ESA/voucher paperwork the SIS never modeled.
  • Student data spread across tools with no shared privacy discipline.

03 / Signs this is you

If you’re seeing this

  • An audit next week would mean a scramble, not a query.
  • Each campus quietly runs its own version of the process.
  • Your SIS handles grades but not how your school actually runs.
  • Growth means more admin headcount, not more capacity.

04 / What we build

Software that carries the school’s shape.

Three ways in, in order of cost: integrate the systems you have, extend the one workflow that is missing, or build the operating layer the model needs. We tell you which on the first call.

Student records for non-traditional structures

Mixed-age cohorts, hybrid models, multi-site enrollment: records shaped to how the school is actually organized.

Audit & accreditation workflows

Evidence captured as work happens, so preparation is a query, not a multi-day reconstruction.

Multi-campus rails

One set of rules across every site, with roles scoped by campus and a network view the office can trust. Sometimes that is a configuration job in the SIS you have. Sometimes it is a module on top. For CES it was a focused audit platform, not a new school system.

Compliance-aware records

FERPA- and COPPA-aware engineering: access controls and minimum-necessary design from the first schema. Awareness and discipline, not a certification claim.

SIS integration

Your SIS keeps enrollment and the official record. We connect it to the rest: enrollment in from Alma, PowerSchool or Gradelink, attendance or progress out, on the schedule the vendor supports and with errors routed to a person. For the Indiana Microschool Collaborative the integration with Alma is designed to run daily in both directions. What a vendor will actually permit decides the design, so we start there.

Parent/guardian communication

Communication that lives in the system of record instead of scattered inboxes.

IMC network dashboard with microschool performance overview.
IMC NETWORK ADMINISTRATOR VIEW
CES classroom observation form with scored teaching criteria.
CES CLASSROOM OBSERVATION FORM, 2026 VERSION

05 / Proven in production

Audit prep still a scramble? See the audit platform CES runs across ten campuses, then book the same call.

“What stood out most was Logic Square’s willingness to really understand our model and build around it rather than trying to force us into a generic platform.”
George Philhower, CEO, Indiana Microschool Collaborative Clutch review, July 2026

06 / The build-vs-buy reality

PowerSchool, Alma, Brightwheel, and when the model is non-standard.

PowerSchool, Alma, Brightwheel, Gradelink and the rest already do a lot. Alma sells to multi-school networks and lets you add custom fields, forms and competency rubrics. PowerSchool runs district-level operations and lets an admin extend pages with new tables without custom development. brightwheel gives a multi-site operator centralized records, billing templates and reporting by location. If your model fits what those platforms configure, use them. Paying us to rebuild a gradebook is money wasted.

Custom work earns its place in the gaps those platforms document around rather than in: a competency-based learning record with goals, evidence and badges per learner; attendance that has to reach the state system from a pod that the SIS does not model; scholarship paperwork that must be rebuilt from attendance and fees every month; a network view across sites that live in different products. Sometimes the fix is an integration. Sometimes a module. Sometimes an operating layer with the SIS underneath it. The question on the first call is which parts of the current setup stay, which connect and which get built.

Buy what works. Integrate what can connect. Build what makes your model different.

07 / Is this you

Who this is for, honestly.

USUALLY THE RIGHT FIT WHEN
  • You run several campuses, or one with a learning model your SIS cannot express.
  • Staff spend hours a week moving the same records between systems.
  • Accreditation, state program or scholarship evidence is rebuilt by hand every cycle.
  • You have an SIS you want to keep and tools that will not talk to it.
PROBABLY NOT WHEN
  • A supported product already does what you need once configured. We will say so on the call.
  • Nothing needs to connect to anything.
  • The staff time you would save is less than the build would cost.

Common questions

Education software, answered.

Why doesn’t a standard SIS fit a non-traditional school?

Often it does, for enrollment, the official record and state reporting. Alma, PowerSchool and Gradelink all document custom fields, standards or competency grading and configurable scheduling. What they do not model is the daily operating layer of a non-standard school: learner pods with goals and evidence, attendance taken where the pod meets, family communication tied to the record, roles that span campuses. The fit question is about those workflows, not the SIS as a whole.

Do you replace our existing SIS?

Not unless replacing it is the cheapest answer, and it rarely is. We look at what the current system handles well, what is missing and whether an integration connects the rest. For the Indiana Microschool Collaborative the design keeps Alma for enrollment and official records while Commons runs the daily workflows and the two are designed to exchange enrollment and attendance daily. Two systems, one owner per record, no double entry for those workflows.

How do you handle student-data privacy?

With FERPA- and COPPA-aware engineering: access controls, minimum-necessary data design, and audit logging, built in from the first schema. That is awareness and design discipline, not a certification claim.

Can you support accreditation and audits?

Yes. For CES Academy, a 10-campus, Cognia-accredited network, we built the audit platform behind 1,200+ audits; report preparation went from days to under four hours, as reported by the client. The pattern is evidence captured as the work happens so a review is a query, not a reconstruction.

What did you build for the Indiana Microschool Collaborative?

Commons: attendance, learner pods with tasks, goals and badges, family messaging, role-based access and activity fee payments for five schools and about 223 students as of October 2026, live since August 2026. Enrollment and state reporting stay in Alma. An AI-assisted layer for teachers is in development and nothing AI has shipped as of October 2026.

Do you handle multi-campus networks?

Yes. CES runs one audit process across ten campuses; Commons scopes roles and records by school across five. The work is one set of rules, roles by site and a network view, built as a layer or an integration on whatever each campus already runs.

Can you support ESA / voucher and state-program paperwork?

We build the operations side those programs depend on: attendance and fee records generated from one source, with the fields a program asks for captured as work happens. Each program publishes its own invoice and documentation requirements, and your portal (ClassWallet, Odyssey, Step Up) stays the portal. We have not built a dedicated ESA invoicing system; we have built the records it draws on.

How long does an education build take?

It depends on what is being built. A scoped integration between an SIS and one other system is a different engagement from a new operating platform; the first is weeks of work with vendor access as the long pole, the second is phased, with working software in use before full rollout. We scope roles, sites, integrations and the evidence required on the first call, and we do not quote from a web form.

Do you develop microschool software or integrate existing systems?

Both. For the Indiana Microschool Collaborative we built Commons, the operations platform a microschool network runs on: attendance, learner goals and progress, family messaging, permissions and activity fees across five schools, designed to exchange enrollment and attendance with the network’s Alma SIS. A platform is not always the answer. We help operators decide whether the need is met by the software they have, an integration, a focused module or a dedicated layer.

Education engagement

Your school already has software. Does it work together?

Bring the list of systems you run and the one job staff do by hand. On a 30 minute call with Silouan or Vineet we tell you whether it is a configuration, an integration, a module or a platform, and whether it is worth building at all.