How these were built
SGAF, NetCall and the free tools started from a job someone was already doing. I learn that job, design the path through it, build the system and keep it running.
SGAF
Boards were already doing the governance. The record was papers, memory and whoever knew where the last pack lived. SGAF puts audits, risks, visit plans and the annual statement on one connected record for UK schools and academy trusts.
The product is the record, not a pile of separate documents. The data model, the permissions and the generated papers have to agree with each other, or the board is back to hunting for the last pack.
NetCall
I built NetCall for my wife, who umpires netball. I am not the umpire. The app follows her courtside workflow: prepare the match, score live, track the centre pass, share a clean result when the whistle goes.
It is a native iPhone app because the job happens standing up, in bad light, with the game still moving. Android is in an invite-only beta.
iPhone £2.99. Android coming soon (invite-only beta).
Free tools
The free checks exist because I needed them on a board, not because they make a good demo. Any board can run them without a sales call.
Free-SchoolAI is a separate library: six hundred and fifty-two prompts for school staff that fill in from their own school, meant to run on a machine they control. A person still owns the draft.
The same method
I use AI through the build: to read the domain, try journeys, write and refactor code, and look for faults. I decide whether AI belongs inside the product at all. When it does, a person still checks the output and owns the release.
Writing code is not a release. I verify the real product before I call the work finished.
Right now the stack is Next.js, TypeScript, PostgreSQL, Supabase, SwiftUI, and model APIs I can test. The tools will change. The job will not.