Outcome: retention
Most first-year attrition is decided in the first six weeks. First Six is built around that window, to turn early disengagement into early support.
The challenge
A large share of first-year attrition is set in motion in the opening weeks, before census, before results, while a new student is quietly deciding whether they belong. Miss that window and the most expensive part of the funnel leaks.
.svg)
Outcomes
What changes when First Six is running for your team.
Support delivered inside the window that decides attrition
Help reaches students in the first six weeks, while their decision to stay is still open.
Early signals turned into early action
A dip in week two becomes a timely nudge or a human reply, not a withdrawal form.
Belonging built deliberately
Connection is engineered through weekly contact and relevant events, not left to chance.
A measurable read on how cohorts settle
Aggregate, privacy-safe trends let you compare cohorts and see what's working.
How First Six helps
The same six-week method, pointed at what your team needs.
01
Orient every week
Personalised weekly guidance keeps new students from drowning in the noise of first year.
02
Catch the dip early
A quiet check-in surfaces a wobble in week two, and a human inbox answers fast.
03
Build belonging on purpose
Relevant events and a warm tone turn a new enrolment into a student who feels they belong.
04
Act inside the window
Everything is pointed at the first six weeks, where most first-year attrition is decided.
What you get with First Six
Three things this gives your team from the first week.
Orient
Weekly, personalised guidance keeps new students from drowning in the noise of first year.
Catch
A quiet check-in surfaces a wobble early, and a human inbox answers fast.
Belong
Relevant events and a warm tone turn a new enrolment into a student who stays.
Outbound webhooks
Subscribe your own systems to signed First Six events (request created, crisis, updated, resolved), delivered over HTTPS with an HMAC signature you verify.
Help desk & CRM (email-to-ticket)
When a student asks for help, open a ticket in the help desk your staff already watch (ServiceNow, Salesforce, Jira Service Management, Zendesk), via email-to-case.
Calendar (ICS)
Add events to the calendar students already use.
Student information system
Sync enrolment and audience groups from your student information system. CSV roster import is available today; the direct push endpoint is in early access.
SAML 2.0
Single sign-on via SAML 2.0. In progress.
OpenID Connect (OIDC)
Standards-based single sign-on via OpenID Connect.
Microsoft Entra ID
Single sign-on via Microsoft Entra ID using OIDC.
Protect your first-year cohort
See how the first six weeks change retention.
Frequently asked questions
What teams ask us most.
By acting in the window where most first-year attrition is decided. It keeps students oriented, catches disengagement early, and gets human support to them quickly. Those are the things that move whether a student stays.
Yes. Engagement and wellbeing trends are reported at the cohort level, and you can compare cohorts over time, all aggregate and privacy-safe.
Not as broad monitoring or risk-scoring. Cohort signals are aggregate and suppressed; when a student signals they're struggling, support staff can see who and follow up, with that access logged.
First Six is configured per cohort and connects to your single sign-on, so a pilot can run for a single intake without a long integration project.