A school website can be a five-page brochure.
It can also become an admissions system, result portal, payment flow, document centre and parent communication tool.
Those are different projects.
For 2026 planning in Nigeria, I would use these bands:
| Scope | Planning budget | Typical outcome |
|---|---|---|
| Focused school information website | ₦350,000–₦700,000 | Core pages, admissions information, enquiry, gallery, contact |
| Admissions/content-focused website | ₦600,000–₦1.2m | Better structure, CMS, news, calendars, downloads, forms, analytics |
| Website + payments/advanced forms | ₦900,000–₦2m+ | Application workflows, verified payments, richer administration |
| Student/parent portal or result system | ₦1.5m–₦5m+ | Authenticated records, permissions, results, billing, dashboards |
| Full school management platform | Scope as custom software | Operations beyond the public website |
These are my planning ranges, not an official Nigerian price list.
The important decision is where the public website ends and the private school system begins.
What a normal school website should do well
For most schools, the public website needs to help four groups:
- prospective parents;
- current parents;
- students;
- staff/partners looking for official information.
A useful first version might include:
- Home;
- About;
- academics/programmes;
- admissions;
- fees or fee guidance where appropriate;
- calendar;
- news/announcements;
- staff/leadership;
- gallery;
- downloads;
- contact and location;
- enquiry or application form.
The website should make the next step obvious.
If a parent is ready to ask about admission, do not bury the contact form under six menu levels.
My school website admission enquiries guide goes deeper into that conversion problem.
What pushes the budget up?
1. Admissions workflow
There is a difference between:
Download the admission form.
and:
Create an application, upload documents, pay a fee, receive a reference number, let staff review it, request corrections and send a decision.
The second is software.
2. Results
Publishing a PDF timetable is simple.
Giving each student authenticated access to private results requires identity, authorization, data modelling, admin tools and auditability.
Treat that as a product feature, not a page.
3. Online payments
Schools may want application fees, tuition, events or other payments online.
Paystack’s current Nigeria pricing, for example, lists local online transactions at 1.5% + ₦100, with the ₦100 waived below ₦2,500 and local fees capped at ₦2,000. See Paystack pricing.
The gateway fee is only one part of the project.
The website also needs to verify the transaction and attach the payment to the correct application or student record.
4. Content volume
Schools produce a lot of information:
- term dates;
- circulars;
- events;
- admissions notices;
- news;
- exam timetables;
- staff updates.
A website that only the developer can edit becomes stale quickly.
I would include a content-management process and train at least two responsible staff members.
5. Photography and media
Parents judge a school partly through the environment they can see.
Good photography can matter more than fancy animation.
Budget for actual images of classrooms, facilities, activities and campus life rather than filling the site with stock photos that could represent any school.
What about student data and privacy?
Once the site or portal collects personal information, treat it seriously.
A public enquiry asking for a parent’s name and phone number is already personal data. A student portal can contain much more sensitive information.
Nigeria’s data-protection framework is administered by the Nigeria Data Protection Commission. See the NDPC for current regulatory guidance.
At a practical level, ask:
- What data do we actually need?
- Who can access it?
- How long do we retain it?
- Can staff export it safely?
- What happens when a staff member leaves?
- Are student records separated from public website content?
Do not treat a school portal like a normal contact page.
Should the website and portal be one project?
They can be connected, but I would still separate the scope conceptually.
The public website is an acquisition and communication system.
The portal is an authenticated operational system.
That separation makes budgeting clearer and allows a school to launch the public site without waiting for a large software project.
A sensible phased approach
Phase 1: public website
Launch credibility, admissions information, enquiries, news and downloads.
Phase 2: application workflow
Add structured online applications and payment verification if the school needs it.
Phase 3: private portal
Only after the workflows and ownership model are clear, add results, bills, documents or parent/student accounts.
This is usually safer than trying to rebuild the whole school operation in one contract.
What should a school website quote include?
I would look for:
- page and template scope;
- admissions responsibility;
- CMS/editor access;
- forms and spam protection;
- payment scope if included;
- mobile responsiveness;
- analytics;
- Search Console;
- domain/hosting ownership;
- training;
- backups and maintenance;
- portal exclusions;
- post-launch support.
Avoid the cheapest possible website if nobody can maintain it
The recurring risk for school websites is not launch.
It is abandonment.
A beautiful site with last year’s admission date creates distrust.
A simpler site that the school can update every week is often the better system.
If you are planning a school website and are unsure whether you need a normal website, an admissions workflow or a full portal, send me the features you have in mind and the current admission process. I can help separate them into a sensible first scope.
