For teams →Every product here has an internal user before it has an external one. Each is behind a gate we publish, and each page says where we are against it. Nothing on this page is for sale yet — what we are looking for is a design partner.
The enrolment pipeline, built from the same contact graph we prospect with.
For: Bootcamps, RTOs, university departments and corporate L&D teams — anyone running an admissions or enrolment pipeline on a generic CRM.
Next gate: Square 1's own outbound runs on it for 60 days
The back office for cohorts, enrolments, revenue recognition and subsidy reporting.
For: Training providers under a subsidy or compliance regime — Singapore SkillsFuture, Australian FEE-HELP and RTO/CRICOS reporting — who reconcile it in spreadsheets today.
Next gate: Our enrolment-to-revenue flow runs through it with no spreadsheet
Mandatory training, competency attestation and revalidation — with the audit trail a regulator inspects.
For: Healthcare providers' L&D and compliance teams — the people who track who has done which mandatory training, and prove it at inspection.
Next gate: A named provider organisation, a named clinical stakeholder, and a written problem statement, agreed in writing
The logged-in shell every other pillar runs on: navigation, identity, permissions, the audit log, and the event spine that accumulates graded work over months. It is infrastructure. We ship it, we use it, we never invoice for it.
Staff own the core: architecture, data, security, release, anything touching a paying customer. Graded learners build the periphery under staff review — importers, admin screens, reports, tests. We know who is good because we graded them. Three rules keep that on the right side of the line: