Loading...
← All work
Case study · SkillroomDelivered
Running everything around a live class, so creators only have to teach.
A marketplace where creators publish live classes and learners enrol, pay and join. Behind it: session generation, scheduled reminder emails, attendance summaries, creator payouts and a full admin console.
- Sector
- EdTech & Creator Economy
- Our role
- Marketplace design, full-stack build, scheduled automation
- Capabilities
- Platforms · Automation
- Status
- Delivered
The challenge
Live teaching fails on logistics.
Live teaching fails on logistics: people forget, sessions clash, and creators wait to be paid. Skillroom automates the parts nobody wants to do by hand, so creators only have to teach.
What made it hard
- 01
Time-bound reliability
Reminders have to fire at the right moment, whether or not anyone is logged in.
- 02
Schedule expansion
Recurring classes must generate and manage their sessions without manual work.
- 03
Money movement
Earnings must be calculated and paid out correctly, or creators leave.
The approach
Automate the logistics on schedules, and make every admin action explicit.
Approved classes expand into sessions from their schedule. Reminders run as cron jobs with a test route, so they fire independently of user activity. Approvals, cancellations, payouts and broadcasts are explicit, audited endpoints, and account flows were hardened against written checklists.
System map
- AI step
- Person in the loop
- Service or store
How it works
- 01
Publish
A creator submits a class; an admin approves it and sessions are generated from its schedule.
- 02
Enrol
Learners browse by category, check out and get a confirmation.
- 03
Remind
A scheduled job emails each learner before every session.
- 04
Teach
Attendance is captured and a summary goes to the creator.
- 05
Pay out
Earnings are calculated and payouts released, with an email to the creator.
Key decisions
Decisions that keep it running on its own.
Decision 01
Cron, not memory
Reminders run on a scheduled job with a test route, so they fire whether or not anyone is logged in.
Decision 02
Admin actions are routes
Approvals, cancellations, payouts and broadcasts are explicit, audited endpoints.
Decision 03
Hardened account flows
Password reset and admin access were reviewed against written checklists.
What shipped
A live-class marketplace, with an operations room behind it.
Publishing workflow
Class submission, admin approval and automatic session generation.
Checkout and enrolment
Category browsing, payment and confirmation.
Scheduled reminders
Cron-driven transactional email before every session.
Attendance capture
Per-session attendance, summarised for the creator.
Creator payouts
Earnings calculated and released, with notification.
Admin console
Audited approvals, cancellations, payouts and broadcasts.
Architecture
A cross-section of the system.
Every layer, from what people touch down to where it runs, and the one job each layer does.
L1Interface
Next.js 14+TypeScript+Tailwind+Framer Motion
Marketplace, creator studio and admin console.
L2Automation
Cron jobs
Scheduled reminders and summaries, independent of user sessions.
L3Data & auth
Firebase
Accounts, classes, sessions, enrolments and payouts.
L4Messaging
Transactional email
Confirmations, reminders and payout notices.
Our scope
Marketplace design/Web application/Payments/Scheduled automation/Admin console
Client view
“A wonderful experience. The collaboration was seamless.”
The team was professional, clear and highly supportive throughout the project. Communication was smooth, expectations were well-defined, and feedback was constructive and timely. I would be happy to work with SYNKSPACE again.
Where it is now
Delivered, and running on schedule between classes.
Skillroom is delivered. Reminders, attendance summaries and payouts run on schedule, and account flows were hardened against written security checklists.
Something like this in mind?
Tell us the problem. We will tell you honestly if we are the right team to solve it.