Case studyReal job
How we built a school website with a family fee calculator
We built a new website for a small independent school.
- Next.jsThe website
VercelHosting the site
ResendEnquiry emails
All figures, levels and people in the video are made up. The school's own fees, photos and branding are not shown.
Transcript
This is a made-up family working out their fees on a school website we built. They add each child, pick a level and tick what applies, and the estimate updates as they go. Nobody asks them for a name or an email to see it.
The client is a small independent school in Australia, and they came to us for a new website. Their old one looked dated, it was hard to use on a phone, and parents had trouble finding things, like how to enrol.
I set those problems out in our proposal, with one more: the old site didn't show what the school is really like. The school accepted it. So the job was a new site, with photos and video from a shoot we organised.
Two things shaped the build. A content editor needs a database and a login behind it, and the school chose not to take that on, so they send us their updates instead. And enrolment had to stay simple and inside the budget, so it starts with a short form.
Then, at a review meeting, the school asked for a fee calculator. Their fee schedule has a rate for each level, discounts for second and later children, concession rates and extras. Working out a family's total from the schedule means applying all of that by hand.
We built it into the site that day. It runs in the parent's browser, from the school's fee schedule. Nothing is sent to a server, so there's nothing to store. And the page says the figures are indicative, and that final fees are confirmed on enrolment.
Enquiries come through a Book a Tour form. When a parent sends it, the school gets an email with the parent's address as the reply-to, so answering is just hitting reply. The parent gets a thank-you email straight away.
A person at the school still reads each enquiry, writes back and arranges the visit, and the school confirms final fees. On our side, a person puts up each update they send.
The school reviewed the draft on the page itself, with our review toolbar. A reviewer clicks the thing they want changed and types a note. The toolbar saves the note with the page, the element and a screenshot. Today, when we've made the change, the toolbar's change log marks it done, and the reviewer can jump straight to it and check.
Now the detail. It's a Next.js site, hosted on Vercel. There's no database and no login. The content lives in data files in the code, so an update is a small change that we check and publish. The calculator is a client component, so its maths runs in the browser. The form posts to a server route, which checks the name, email and message before it sends anything.
The calculator is the careful part. Each child gets a level, a concession switch, a bus option and a new enrolment switch. The sibling discount starts at the second child, and children are sorted by fee first, so the highest fee counts as the first child. The early payment discount comes off tuition only, and not off concession rates. A new enrolment adds the one-off application fee and bond.
Enquiry emails go out through Resend, from the school's own domain. Resend only sends from a domain once the DNS records it generates are in place. The school's domain sits with their IT provider, so the provider added those records, and made the switch to the new site.
One small decision: if the parent's thank-you fails to send, the enquiry still goes through, because the school already has it.
The hard part wasn't the code. It was fitting around a school year. The school chose to start in the new year, several staff reviewed the draft, and the school chose the photos that went on the site.
It's been live since June 2026, and we host it. The school sends us updates, like newsletters and event dates, and we put them up. The form doesn't store enquiries, so we don't count them, and there's no before and after to show you.
If parents have to dig through your website for fees or how to enrol, get in touch.
Families can work out an indicative fee estimate for each child in the browser, without giving a name or an email. Enquiries reach the school by email with the parent's address as the reply-to, and the parent gets a thank-you. The school reviewed the draft on the page with our review toolbar.
How and why they came
The school came to us for a new website. Their old one looked dated, it was hard to use on a phone, and parents had trouble finding information, enrolment pathways in particular. The site also didn't show what the school is really like.
I set those problems out in our proposal and the school accepted it. The job was a new site, built for phones first, with photos and video from a shoot we organised.
The problem
Two decisions shaped the build early. A content editor needs a database and a login behind it, and the school chose not to take that on. They send us their updates instead. Enrolment had to stay simple and inside the budget, so it starts with a short form that emails the school.
Then, at a review meeting, the school asked for a fee calculator. Their fee schedule has a rate for each level, discounts for second and later children, concession rates and extras. Working out a family's total from the schedule means applying all of that by hand.
What we built
- 1

The site
Programme and enrolment pages, news and newsletters, built for phones first. It grew past the pages first planned so it would feel complete.
- 2
A family fee calculator
Families add each child, pick a level and switch on what applies. The estimate updates as they go and breaks down by child, with discounts, extras and one-off costs shown separately. It runs in the browser from the school's fee schedule, so nothing is sent or stored. The page says the figures are indicative and that final fees are confirmed on enrolment. We built it the day the school asked.
- 3

Enquiries by email
A Book a Tour form, and an enrolment enquiry form. The school gets each one by email with the parent's address as the reply-to, and the parent gets a thank-you email straight away.
- 4
Review on the page
The school marked up the draft pages in place with our review toolbar.
The site's own code on a local copy, with sample data
The fee calculator with three made-up children.
The system's own output. Sample brand and data.
The school's copy of an enquiry, with the parent as reply-to.
The system's own output. Sample data.
A sample note left on the draft with our review toolbar.
Our review toolbar on a local copy. Sample note.
The same note in the toolbar's change log, marked done.
Our review toolbar on a local copy. Sample note.
What a person still does
Someone at the school reads each enquiry, writes back and arranges the visit, and the school confirms final fees on enrolment. When the school sends an update, a person on our side puts it up.
The technical detail
What each tool does here
Next.js
- Pages are Server Components by default, and a Client Component is the way to add state and event handlers that run in the browser.1
- The calculator is a Client Component, so its sums run in the parent's browser.
- The enquiry forms post to Route Handlers, which take custom requests on the server.2
- The route checks the name, email and message before it sends anything.
Documentation
Resend
- Resend sends from a domain you own, and you add and verify a domain before sending with it.1
- Verifying means giving your DNS provider the DKIM and SPF records Resend generates.2
- The school's domain sits with their IT provider, who added the records and later made the switch to the new site.
- Each send can carry a reply-to address, which is how the school's copy of an enquiry replies straight to the parent.3
Documentation
Our review toolbar
- It switches on only from a review link.
- A reviewer picks an element on the page and types a note, and the toolbar saves the note with the page, the element and a screenshot.
- Since the school's review, the toolbar has also gained a change log: each note shows as pending, in progress or done, and the reviewer can jump to it on the page to check.
Vendor links checked 16 November 2026.
Design decisions
No database
Content lives in data files in the code. An update is a small change we check and publish.
Sibling discounts by fee
The sibling discount starts at the second child. Children are sorted by fee first, so the highest fee counts as the first child.
Early payment on tuition only
The early payment discount comes off tuition, and not off concession rates. Extras such as the bus are added per term, and a new enrolment adds the one-off application fee and bond.
The enquiry comes first
If the parent's thank-you fails to send, the enquiry still goes through, because the school already has it.
A short form
Only the name, email and message are required, so the form stays quick to send.
The hard parts
Fitting a school year
The school chose to start in the new year, and review meetings were planned around the days staff overlap.
Several reviewers
A few staff reviewed the draft, over more than one review round.
Photos
The school chose which photos went on the site.
The domain
The school's domain and DNS sit with their IT provider, so the email records and the switch to the new site went through them.
Where it stands
Live since
June 2026
- It's been live since June 2026, and we host it.
- The school sends us updates, such as newsletters, opening hours and event dates, and we put them up.
The enquiry forms don't store anything, so we don't count enquiries, and there's no before and after figure on this page.
Questions
Can a school website have a fee calculator without collecting family details?
On this job, yes. The calculator runs in the parent's browser from the fee schedule in the site's code. Nothing is sent to a server, and the page says the figures are indicative.
How should sibling discounts work in a fee calculator?
That's the school's policy to set. On this job the discount starts at the second child, and children are sorted by fee first so the highest fee counts as the first child.
Can enquiry emails come from the school's own domain?
Yes, with Resend, once the domain's DNS records are added and verified. Here the school's IT provider added them.
Do we need a content management system to keep the site current?
Not on this job. The school chose not to run a database and a login, so they send us updates and we publish them.
How can staff review a new website before it goes live?
On this job, with our review toolbar. Staff left notes on the draft pages, and each note carried the page, the element and a screenshot.
Want parents to find your fees and enrolment details on your website?
Book Free AssessmentProduct names and logos belong to their owners and are shown to identify the systems connected.