Admissions CRM
Every enquiry, on one board
Admissions & Growth
Pages, posts, events and a gallery on your own domain, authored by the people who run the institute rather than by whoever has the FTP password.
cms · 24 API routes60% against our own specification — in progress, see build statusOne of the four we would rather you knew about before a demo than after one. What exists is below; so is what does not.

Markdown source, published on your slug or your own domain.
What is on, and photographs with the caption the upload required.
Not maintained by hand, and therefore not wrong.
Your site posts to the same capture endpoint this one does. One enquiry, one board.
How it actually works
The renderer takes Markdown and emits React elements. It never emits HTML, so nothing an author types can become script in a visitor’s browser. That is stronger than sanitising, because there is no sanitiser to have a gap in.
A sample. Each is a real key in the catalogue, described for a school administrator rather than an engineer.
cms.site.viewcms.page.publishcms.post.publishThe shipped role templates that hold it by default. Each is a copy you own and can edit — nothing in the code reads a role's name.
Naming these here is cheaper for both of us than discovering them in week six of a pilot.
Naming these is cheaper for both of us than discovering them in week six.
Every enquiry, on one board
Nothing ships until somebody says so
A hundred seats, twenty-five courses and no conversation. If you would rather see it driven by someone who knows it, that takes twenty minutes.
Or open the sandbox (opens in a new tab) and click around first. No form.