Skip to content
Schoolhouse

Custom development

Your school, your way.

Every school works differently. If Schoolhouse doesn't do something you need yet, tell us — we'll scope it, quote a fixed price, and build it on the platform itself.

What we build

If you can describe it, we can probably build it.

These are the most common requests — never the limit. Bring us the problem, and we'll work out the change.

Report cards and grading scales

Your layout, your scale — percentages, letters, GPA, IB 1–7 or a national scheme — with comment banks and bilingual reports.

Fee structures

Sibling discounts, instalment plans, term-based billing, VAT and local tax rules, scholarships and bursaries.

Integrations

Accounting packages, learning platforms, identity providers, fleet tracking, government reporting — via our documented REST API.

Workflows and approvals

Trip permissions, purchase requests, leave rules and multi-step approvals that match how your school actually decides things.

White-label and app-store publishing

Your name, domain and icon — and, once the mobile apps are released, those apps published in the stores under your own school's account.

Certificates, ID cards and letters

Bespoke designs that match your existing stationery, with the same numbering, verification and revocation built in.

Statutory payroll for your country

Income tax, social insurance and pension rules for your jurisdiction, so payslips are right for where you operate.

More languages

Full translation with native-speaker review, including right-to-left scripts, for the languages your community speaks.

Data migration

Students, guardians, fees and history moved from your current system, checked row by row before anything goes live.

Private cloud or on-premise

Deploy to your own infrastructure in the region your regulations require, with your identity provider and your backups.

How it works

From idea to live, in four clear steps.

No hourly surprises and nothing built before you've agreed to it.

Step 1

Send an inquiry

Describe what you need in plain words. No technical detail required — a screenshot or an example document helps.

Step 2

Discovery call

We ask the questions that matter, usually in one call, and tell you honestly whether it's a small tweak or a bigger build.

Step 3

Fixed-price proposal

You receive a written scope, timeline and price before any work starts. No hourly surprises.

Step 4

Build, review, launch

We build it on the platform itself, you review it before it goes live, and upgrades carry it forward.

Why build on Schoolhouse

Custom work that survives every upgrade.

The worst thing about customised software is the day the vendor ships an update and your changes break. We build custom work as part of the platform, so that day never comes.

Built on the platform, not bolted on

Custom work uses the same API and module structure as the product, so every upgrade carries your changes forward.

A documented API to build on

118 documented operations, described in an OpenAPI specification, with response contracts checked by the server.

Held to the same standard

Schoolhouse ships with 277 end-to-end checks. Custom changes are tested the same way, so they're safe to release.

Deployed your way

Custom modules run wherever Schoolhouse does: our cloud, your private cloud, or your own servers.

Describe what you need.

Your inquiry goes straight to our support team. A few details help us give you a useful answer, fast:

  • 1What problem are you trying to solve, and who has it?
  • 2An example — a current report, a spreadsheet or a screenshot — if you have one.
  • 3Any deadline, such as the start of a term.

Prefer email? Write to aqbutt05@gmail.com.

Custom development FAQ

Common questions about custom work.

How much does a custom change cost?

After a short discovery call we send a written scope and a fixed price — not an hourly guess. Small changes such as a report layout or certificate design are usually quick; larger modules and integrations are scoped individually.

Will custom changes break when Schoolhouse is updated?

No. Custom work is built on the same API and module structure as the product and is maintained alongside it, so upgrades carry your changes forward.

Who owns the customisations?

We agree that in the proposal. Most schools want the change available to them permanently; some ask for exclusivity. Tell us what matters to you.

Can you integrate with our existing systems?

Yes — accounting packages, learning platforms, identity providers, fleet tracking and government reporting are all typical integrations. Schoolhouse exposes a documented REST API to build on.

Can we get a private or on-premise deployment?

Yes. Schoolhouse runs in the cloud, in a private cloud or on your own servers. On-premise and private-cloud deployments can be arranged as a custom engagement; ask us.

Prefer to talk it through first?

Book a demo and bring your questions — we'll show you what's already there before you commission anything new.

Prefer email? aqbutt05@gmail.com