My first experiment began around March 2026. The collection expanded through August and September. Five featured stories show the process in depth; the full 16-app KEYSTONE collection below shows the wider range of school needs it supports.
Staff systems need a prepared presenter demo. Use fictional pupil records. Attendees can browse the public GCSE Hub; staff-only links require authorized access.
These examples anchor the session. Each starts with a school problem and a useful result.
Turn subject videos and course information into something families can explore.
A website in place of the requested presentation. The project introduced Rolly to Cloudflare and direct AI-assisted publishing.
Current pupil information in iSAMS needs to be easier for staff to access and use.
A focused view that makes existing pupil data easier to navigate.
Announcing new pupils is a recurring school pain point: information needs to reach the right people clearly.
A purpose-built way to prepare and share new-pupil announcements.
OpenApply information needs a simpler way to be shared with the staff who need it.
A clearer view of admissions information for the school workflow.
A new school needs an internal home for staff information, resources and processes.
An expanding staff portal, with a CMS and admin area so content can be maintained.
Explore each tool’s school problem, current purpose and BUILD takeaway. Where Rolly has shared the origin, the entry includes that story. Each development journey has more detail to tell.
App descriptions and access labels: KEYSTONE Apps Gallery ↗Visitor requests and arrivals involve several people, decisions and handovers.
Welcomes walk-ins, accepts staff-arranged visit requests and guides visitors through the appropriate arrival route.
After Family Pass, Rolly started the visitor app, paused it, then resumed and completed it in August 2026. The work introduced email, QR scanning, multi-level permission routing and Microsoft 365 sign-in through Entra.
A familiar campus process can reveal the next capability you need to learn.
Families need to submit photographs and details for parent and guardian access cards.
Provides a clear application form for family campus access cards.
Around May–June 2026, the safeguarding lead asked Rolly to help produce a form for family ID photographs. Rolly extended his GCSE learning into an app that accepted submissions and stored files and records, learning Cloudflare R2 and D1 along the way.
One real request can take a first website experiment into a working submission workflow.
Families need an accessible way to explore subject videos and course information.
Brings subject guidance and short videos together to support GCSE choices.
Around March 2026, Rolly was asked to make a presentation from videos and course content. He tried a website instead, using ChatGPT. He discovered Cloudflare, published manually at first, then asked whether AI could connect and publish directly.
Questioning the requested format can uncover a more useful way to serve the audience.
School identity needs to be applied consistently across colleagues’ everyday work.
Helps staff install Lato and find practical WASBKK visual identity guidance.
A small resource can make a shared standard easier to follow.
Email signatures need consistent details, formatting and school identity.
Creates on-brand WASBKK email signatures.
A focused generator can remove repeated formatting work.
Pupil photographs need consistent cropping and formatting for iSAMS.
Prepares pupil photographs directly in the browser.
A narrow task can be a useful first app idea.
Colleagues need a shared home for school information and daily work.
Brings people, updates, systems, documents, workflows and support into one staff portal.
From August 2026 onward, THE NEST became Rolly’s largest ongoing project. It was the first where he added a CMS and admin workspace, allowing content to be maintained as the school’s needs expanded.
Think about the people maintaining an app as well as the people using it.
Facilities and technology issues need enough detail to reach the right team.
Accepts help requests and routes issues to Facilities or Tech Support.
Routing and clear request information matter as much as the form itself.
New colleagues need clear instructions to activate and use their school email.
Sends the information staff need to start using their school email account.
A repeated onboarding step can become a focused workflow.
Announcing new pupils is a recurring school communication pain point.
Turns Admissions information into clear announcements for colleagues welcoming each arrival.
Rolly described the starting problem as the difficulty schools face in announcing new pupils. The aim was to make that recurring communication clearer and easier.
Start with a task colleagues repeat and the information they need.
OpenApply information needs to be easier to share and follow through onboarding.
Tracks the journey from inquiry to a fully onboarded pupil handed over to iSAMS, in a living record synchronised from OpenApply.
In the planning conversation, Rolly described Pupil 360 as a simpler way to share OpenApply data. The current gallery describes its wider onboarding role.
A clear first purpose can grow into a more substantial workflow.
Current iSAMS pupil information needs a lighter interface for staff.
Offers pupil data, timetables, birthdays, locations, email tools and flexible print or file outputs.
Rolly described the initial purpose as making iSAMS easier to use when accessing current pupil data.
You can improve access to information without replacing its source system.
Authorised colleagues need access to essential pupil health information.
Provides restricted access to sensitive pupil medical records and health information.
The intended user and their permissions are part of the app’s purpose.
The Tech Team needs a usable view of pupil laptop records and specifications.
Searches records by year group, reviews specifications, prints reports and exports data.
Make the output match what the person doing the task needs.
Personalised, letterheaded documents require repeated data and layout work.
Merges CSV or Excel data into personalised PDFs locally in the browser, without an email account.
A document workflow can become a useful app in its own right.
Pupils need a clear view of their own lessons and school week.
Shows today’s lessons, the current class and the full week, personalised from iSAMS. Pupil sign-in is required; staff accounts are currently unsupported.
Design around the person using the tool, not just the data it displays.
Real operational needs, before opening day.
A website instead of a presentation; Cloudflare and publishing.
Family ID photo submissions; R2 for files and D1 for records.
An earlier project resumed and completed: email, QR and multi-level permissions; Microsoft Entra / Microsoft 365.
Wycombe Abbey International School Bangkok.
The biggest ongoing project; the first CMS and admin build.
For each demo: explain the request, show the useful app and share one correction or new thing you learned. That makes the first step feel possible.
Browse the KEYSTONE Apps Gallery ↗