A school admissions portal is not simply an online form. It is the process that takes a prospective pupil from application to review, assessment, offer and enrolment without losing documents, payments or decisions along the way.
For a Nigerian private school planning its 2026 budget, start by testing an existing admissions module before commissioning custom software. If the school only needs parents to enquire, book visits and submit basic details, a good public website may be enough. Custom development becomes more reasonable when the school has several admission stages, campuses, approval roles or integrations that ready-made software cannot support.
These are my illustrative professional project-scoping allowances, not surveyed Nigerian market averages or fixed quotations:
| Approach | Initial planning allowance | What you are buying |
|---|---|---|
| Admissions enquiry and application pages on an existing website | ₦450,000–₦900,000 | Mobile forms, document instructions, notifications and a manageable enquiry workflow |
| Configuring an existing school admissions product | ₦750,000–₦1.8m for substantial setup/integration work, plus any software fees | Process configuration, branding, migration, training and supported integrations |
| Focused custom admissions portal | ₦1.8m–₦4.5m | Applicant accounts, secure documents, application stages, review and decisions |
| Multi-campus or deeply integrated admissions system | ₦4.5m+ | Campus-specific rules, permissions, assessments, fee reconciliation and links to existing school systems |
A simple hosted product may cost much less than these professional implementation allowances. A complex migration or integration may exceed them. Ask suppliers to quote the actual admission journey, not just the number of pages or login screens.
First decide whether you need a portal at all
There are three different problems schools often describe as “we need an admissions portal.”
Problem one: prospective parents cannot find information or make an enquiry. They need clear entry requirements, age groups, dates, fees or fee-request instructions, visit booking and a reliable contact route. Fix the school website’s admissions journey before paying for private accounts.
Problem two: applications arrive, but staff process them manually. Documents are scattered across email and WhatsApp, application fees are checked separately, interview dates are missed, and nobody knows which applicant has received an offer. A configured admissions module or a focused workflow can help.
Problem three: the school operates a complicated admissions process. Different campuses have different entry criteria, staff review only assigned applications, entrance assessments affect decisions, and accepted applicants must move into the school’s student records without re-entry. That is a stronger case for custom integration or development.
Buying a portal to solve the first problem is often an expensive substitute for fixing a confusing website.
Buy existing school software or build your own?
Buy or configure when your admissions process is standard
Several Nigerian school-management products already advertise admissions, parent records and payment features. Their billing models differ: some charge per student or term, others charge by school or offer enterprise arrangements. Compare the current written quote and a working demonstration rather than treating any vendor’s headline subscription as the full implementation cost.
Ask the vendor to demonstrate your school’s application form, document uploads, application-fee status, reviewer roles, offer letters, export and support process. Confirm whether the admissions feature is included in the exact plan you are considering.
The key buying question is not “does the software have admissions?” It is can our staff complete one real admissions cycle without falling back to a parallel spreadsheet?
Build when the workflow itself is unusual or strategically important
A custom portal can be justified when a school’s actual process cannot be configured safely in an existing system. Examples include several independent campuses, school-specific entrance assessment rules, multiple approval committees, conditional offers, scholarship decisions or an integration with an established student information system.
But custom means taking responsibility for access controls, backups, document storage, error recovery, monitoring, deployment, training and future changes. The software is not finished because the application form looks polished.
A useful first release might cover application → verified fee where applicable → staff review → decision → applicant notification, while leaving advanced analytics and unrelated school administration for later.
What actually drives the price?
Applicant and guardian accounts
Will parents apply without creating accounts, or do they need to save a draft and return? Can one guardian apply for two children? How are duplicate applications handled? A “simple login” becomes more involved once identity, recovery and privacy are defined.
Documents and personal data
Applications may contain birth dates, addresses, previous school information and documents relating to children. Collect only what the school actually needs, restrict access by staff role, define retention and deletion procedures, and use appropriate consent and notices. Nigeria’s Data Protection Commission provides the official national framework; have qualified counsel review legal obligations for the school’s particular processing.
Do not ask a developer to send real applicants’ documents through a public demo or a personal messaging account.
Payments and admission decisions
Some schools charge an application fee; others do not. If payment is required, the application should not be marked paid merely because the parent returned to a success page.
Paystack’s verification guidance explains server-side transaction checks and warns against fulfilling the same transaction twice. Its webhook documentation explains how to authenticate incoming events. A robust workflow links the verified amount, currency and reference to the intended application and makes retries safe.
Payment is also not the same as admission. A paid application can still be under review or declined; the portal must not automatically turn a payment into an offer.
Staff review, assessments and notifications
Who can see a submitted application? Who can edit a score, request a missing document, schedule an interview or approve an offer? What happens when the responsible staff member is absent? Every extra approval layer or notification channel needs clear rules and tests.
Existing school records
If an accepted applicant becomes a student, can the school transfer the correct record into its current student system without duplicate identities? A vendor’s “integration available” claim should be tested against the specific product, API access and data format your school uses.
A realistic example: 300 applications in one intake
Imagine a private school receives 300 applications for its next intake. Parents submit forms and documents, some pay an application fee, staff screen eligibility, shortlisted pupils attend assessments and the principal approves offers.
The main cost driver is not storing 300 rows. It is preserving the correct state of each application when a parent submits twice, a payment confirmation arrives late, an assessment is corrected or an offer is withdrawn.
For this school, I would ask for a demonstration using a small set of fictional applicants:
- A guardian starts an application on a phone, saves it and completes it later.
- The portal accepts only the permitted file types and protects private documents.
- A failed or pending application fee does not appear as paid.
- The same successful payment event arrives twice but is recorded once.
- A reviewer sees assigned applications, not every child’s records.
- An offer cannot be issued without the school’s required approval.
- The accepted applicant is exported or transferred without creating duplicate student records.
- An administrator can find the audit trail when a parent disputes the status.
If the supplier cannot demonstrate these behaviours, a low quotation is not yet a reliable quotation.
The hidden cost of the cheapest option
A subscription may be affordable until you add setup, messaging, payment fees, document storage, migration, custom forms and support during the busiest admission week. A custom portal may have no recurring software licence but still needs hosting, backups, monitoring, security maintenance and someone to respond when an application fails.
Compare at least three years of total ownership cost:
- Existing software: subscription + setup + integrations + support + export or exit costs.
- Custom software: discovery + development + testing + infrastructure + maintenance + future changes.
For either option, insist on a usable data export and written responsibility for domain, hosting, payment accounts and administrative access. The school should not lose its admissions history because it changes suppliers.
What should be included in a developer’s quotation?
Request a written scope covering public admissions information, form fields, guardian access, documents, payment states, review stages, offer decisions, notifications, reporting, mobile testing, accessibility, staff training and handover. The W3C’s form guidance is a useful reference for clear labels and usable form controls.
Ask for acceptance criteria rather than a long feature list. Specify who will own the code repository and infrastructure, whether there is a maintenance agreement, how backups are restored, and what the school receives if the relationship ends.
If your real need is only a public-facing website, compare the school website cost guide. If you need authenticated results for enrolled students, that is a separate school result portal decision. For custom engineering scope, see custom software development costs and payment integration costs.
So what should your school choose?
Use a clear website for enquiries, existing admissions software for ordinary application workflows, and custom development only when the process or integrations genuinely demand it. That decision protects the school’s budget and makes it easier for parents to apply.
If your school is evaluating a new admissions system, contact me with the number of campuses, approximate applications per intake, existing software and the steps staff currently follow. Please use a description or fictional sample rather than real children’s records. I can help assess whether configuration, a focused website improvement or a custom MVP is the responsible next purchase.
