For families
A clearer path from choosing a tour to receiving the details needed for the visit.
Make school tour booking easier for families and staff.
A single workflow for publishing tour availability, accepting bookings, coordinating calendars, and preparing staff for each visit.
In staging with industry partners, with feedback from the first progress review now being implemented.
01The problem
What makes this worth solving?
Booking a school tour can become a chain of forms, emails, calendar checks, confirmations, and manual follow-up. Families want a clear way to choose a suitable visit. Staff need the booking to arrive with the right details and fit the school’s actual availability.
When those pieces live in separate tools, the burden falls on staff to keep them synchronized. Small gaps create extra communication, inconsistent preparation, and avoidable administrative work.
02What I’m building
How the product is meant to work
The platform brings configurable tour types, booking forms, availability, calendar connections, email templates, and pre-tour preparation into one workflow.
The goal is not to add AI everywhere. It is to use automation where it can remove repetitive coordination while keeping school staff in control of the experience.
03Why this project
Why I’m spending time on it
This project is being developed with industry partners who understand the daily workflow and the exceptions an outsider would miss. That makes it possible to test each product decision against real operating knowledge instead of assumptions alone.
It is also the clearest current test of whether I can turn product and technical experience into software that becomes valuable enough for schools to keep using and eventually pay for.
Intended value
What should become better if this works?
The value is still a hypothesis until sustained use and payment confirm it.
For school staff
One place to manage availability, booking details, calendars, communication, and preparation.
For operators
A repeatable admissions workflow that can improve as real usage reveals what matters.
Related field notes
The story behind the current evidence.
Building with real partners changed the kind of evidence I had.
A working prototype is one thing. Building alongside people who know the problem changes what the work means.
Read the field noteThe first progress review went well. The feedback mattered more.
A strong response was encouraging. The useful part was learning where the product still differed from the real work.
Read the field noteFollow the build
Too many ideas? Help me decide what to build next.
Get honest updates on what ships, what fails, and what changes next, straight from the work in progress.
Email list for updates
Also building Build Forward, a project-decision skill for Codex and Claude Code.