All products →Admissions CRM
The enrolment pipeline, built from the same contact graph we prospect with.
Stage v0 · 0 of 4 gates passed
Who it's for
Bootcamps, RTOs, university departments and corporate L&D teams — anyone running an admissions or enrolment pipeline on a generic CRM.
Why we can win it
The contact graph comes from the scraping-and-verification stack that already runs Square 1's own outbound. Generic CRMs start empty; this one starts with the people you should be calling.
The internal user
Square 1 runs its own admissions and outbound on it first. The reference customer is us.
Metric, and its counter-metric
External organisations with at least one daily active user in the last 7 days.Founder hours per active external organisation per week. If that is not falling, this is consulting with a login screen.
The gates
A stage advances when its gate is passed — not when a deadline arrives.
- v0
Contacts, a pipeline view, the existing lead engine — internal only now
Gate: Square 1's own outbound runs on it for 60 days
- v1
Multi-user, organisations, permissions, activity log
Gate: One external design partner using it daily, unpaid
- v2
Enrolment pipeline objects specific to education
Gate: The design partner agrees to pay
- v3
Self-serve onboarding, billing and support with no founder in the loop
Gate: Three paying customers who did not need founder support
What we refuse to build
- ✕A horizontal CRM. Salesforce, Dynamics and HubSpot own the category; Attio and Clay own the open edge.
- ✕Anything that is not an admissions or enrolment pipeline.
Become the design partner
The next gate is a named organisation. If that could be yours, tell us the problem in your own words. A founder replies, personally. Nothing to buy, nothing to sign.