A student lifecycle that runs itself, from first week to renewal

Problem

A student's record touches the CRM, the community platform, and the student performance platform at every stage: enrollment, coach and cohort assignment, birthdays, renewal, offboarding. Each stage used to need someone to notice the date and update three systems by hand, or it didn't happen until someone complained.

What I built

• A nightly sync of coach, cohort team, and program level from the CRM into the student registry, plus a CRM to community sync that retags coach and program level.
• An enrollment catch that flags data problems at signup, built and waiting on go-live.
• Birthday and anniversary flows: a weekly coach heads-up, a day-before nudge, a data-hygiene pass, and a daily anniversary check.
• Renewal alerts 30 days before maturity that resolve the assigned partner and tag them in the community, plus a monthly renewals mission for coaches.
• A daily offboarding sweep that catches students still active past their offboarding date and posts a safety-net alert.
• Onboarding and offboarding for team members and coaches, coach substitution intake, a welcome-call digest, failed payment follow-up, and duplicate deal alerts.

Result

The lifecycle now runs on its own from enrollment through renewal to offboarding, with a person stepping in only where a flag needs a decision. Every workflow reports into the same fleet-wide alarm, so a failure surfaces the same way it does anywhere else.

What it shows

Breadth handled consistently: the same conventions and alarm across every workflow that touches a student's lifecycle, instead of one big fragile script.