Specialist training school — Education
When enrolment grew and the spreadsheet gave out
Enrolment, payment, class access and support each lived in a different tool. We connected them into one path.
- Year
- 2024
- Industry
- Education
01Challenge
Every term, two full-time people reconciled the payment list against the access list. Every term, a few students either did not get access or got the wrong one.
02Analysis
- 01The gap between payment and accessNothing connected payment confirmation to access activation; a person had to check it by hand.
- 02Repetitive supportMost tickets said the same thing: "I paid but I have no access."
03Solution architecture
01 — Solution architecture
Enrolment
- Course form
- Payment gateway
- Transaction confirmation
02 — Solution architecture
Orchestration
- Account creation
- Course assignment
- Welcome email
03 — Solution architecture
Support
- Automatic ticketing
- Class reminders
- End-of-course survey
04 — Solution architecture
Reporting
- Completion rate
- Payment status
- Feedback
04Results
- Payment to accessup to a daya few minutes
- "I have no access" ticketsthe most common ticketexceptional cases
- Manual work per term2 full-time peoplespot checks
Toolsn8nPostgreSQLPayment gateway APILMS APIMetabase
Next step
Does your project look like this?
If any part of that story felt familiar, we can probably help.