Application pipeline
Every applicant in stages from enquiry to enrolled, with owners, notes, tags and automatic emails at each step.
Coding schools: from first application to graduation day. Teach more code, write less admin.
Applications land in three inboxes, coding challenges get marked from email attachments, the cohort lives in a spreadsheet and somebody is chasing week six instalments by hand. We build admissions, cohort, payment and student portal systems for coding schools and bootcamps, then we host them and look after them.
A coding school is an admissions office, a classroom, a finance team and a careers service all running at once. Applicants fill in a Typeform, the take-home challenge comes back as a GitHub link in an email reply, the interview gets booked over four messages and the offer goes out from someone's Gmail. Once the cohort starts it gets worse: attendance in one sheet, project marks in another, instalments in Stripe and Slack holding everything else together. Run kids' term classes and holiday camps on top and the spreadsheets start breeding.
Wollopit builds custom software around how your school actually runs. Applicants move through a proper pipeline with challenges reviewed in one place. Offers turn into enrolments with payment plans that bill themselves. Students get one portal for schedules, resources and project submissions. Mentors mark against a rubric and you can finally show graduate outcomes without a week of digging. We connect the tools you already like, replace the ones holding you back and look after the lot on our own servers.
What we hear from coding schools
Most coding schools we talk to are brilliant at teaching and run the business on forms, inboxes and spreadsheets. It holds up fine until intake week.
Solutions
Pick the one that's hurting most or join the whole lot up. Everything is built around how your team works, not the other way round.
Every applicant in stages from enquiry to enrolled, with owners, notes, tags and automatic emails at each step.
Take-home challenges sent automatically, submitted as links or files and scored against a rubric.
Self-booked interview slots, Zoom or Google Meet links, reminders and interviewer scorecards.
Offer letters with your terms, e-signature and the deposit taken in one step.
Upfront, deposit plus instalments or custom plans that bill themselves with retries and Xero sync.
Intakes, start dates, groups, mentors, capacity, deferrals and waitlists.
Schedules, resources, recordings, announcements and payments for each student in one login.
GitHub links or files submitted per project, rubric marking, mentor feedback and resubmissions.
Class check-ins, project progress and at-risk flags so nobody quietly drifts off.
Rosters, marking queues, office hours bookings and student notes for every mentor.
Graduate check-ins, job placements, employer contacts and outcome reports.
Term and camp bookings for parents, sibling discounts, medical notes and pickup details.
Webinar and open night bookings, lead tracking and follow-ups tied to enrolments.
Completion certificates issued automatically and an alumni list you can actually keep in touch with.
Hand-built, quick on mobile, with course pages, upcoming intakes, apply buttons and built to rank for 'coding bootcamp' and your city.
The big ones
These are the systems coding schools ask us about most. Each one works on its own and they get properly useful when they're joined up.
Admissions
Applications from your website, info sessions and referrals land in one pipeline. Challenges go out automatically, submissions come back into the applicant's record and interviews book themselves. Offers go out with e-signing and a deposit, so a yes turns straight into an enrolment.
Cohorts & payments
Intakes, groups and mentors all live in one place, with capacity and waitlists that manage themselves. Payment plans bill on schedule, failed cards retry and you see who's behind before it becomes a problem. Everything reconciles into Xero.
Student portal
Students see their schedule, resources, recordings and project deadlines for their cohort without hunting through Drive and Slack. They submit projects, get feedback, book office hours and check their payment plan in the same place.
Marking & progress
Every project submission lands in a mentor's marking queue with the rubric attached. Attendance and progress roll up per student, so at-risk flags appear early and you can step in before a withdrawal.
Careers & outcomes
Track every graduate from portfolio review to first job with scheduled check-ins and employer contacts. When someone asks what your grads actually do, you've got real records instead of a vague guess.
Before and after
Here's how intake week could change. Every coding school runs differently, so we map yours first.
Everything under one roof
Whether you're starting fresh or upgrading what you've got, it's one team from the first sketch to the support call.
Built around how your coding school actually runs: application pipeline, coding challenges and the admin in between, in one system you own.
Fast, hand-built websites that rank for the searches your customers make and turn visits into enquiries, bookings or orders.
Running on spreadsheets, old software or a platform you've outgrown? We move your data across and upgrade in stages so the business never stops.
Interview booking and offers & e-signing: customer and staff portals that work on any phone without an app store.
We connect Google Workspace, Microsoft 365 and GitHub so information moves on its own and nobody retypes it.
Managed hosting, updates, backups and security for your coding school, looked after by the people who built it.
Connections
We connect to the tools you rely on, work alongside platforms you're happy with or replace the ones holding you back.
The process
We get properly below the surface of your coding school: the systems, the busy days and the jobs everyone hates. Then we fix the bits that matter most first.
We sit in on an intake, a class and your admin day, then work out what's actually slowing admissions and cohorts down.
We plan it before writing code: your pipeline stages, challenges, cohorts, payment plans, portal, hosting and cost.
Real engineering, shown to you early and often. Usually the most painful bit first, so you get a win before your next intake.
We host it, maintain it and keep improving it. When something breaks you call the people who built it.
FAQ
Something else on your mind? Ring 0423 011 252 and ask the people who'd build it.
Yes. Applicants submit GitHub links, deployed URLs or files straight into the pipeline. Reviewers score them against your rubric and the applicant moves to the next stage automatically.
Yes. We set up upfront, deposit plus instalments or custom plans through Stripe or GoCardless. Failed cards retry on their own, you get alerted and everything reconciles into Xero or MYOB.
No. If your learning platform is doing its job, we build around it: admissions, payments, cohorts and outcomes on top, with single sign-on so students aren't juggling logins. If it's holding you back, we'll show you what replacing it would involve first.
Yes. Students can sign in with GitHub, submit repos for marking and new cohorts can be added to the right Slack or Discord channels automatically.
Yes. Parent bookings for terms and camps can live alongside the bootcamp, with their own pricing, medical notes and attendance, all in one back end.
Yes. Scheduled check-ins collect job details from graduates and the reports group them by cohort, so your outcomes are based on real records.
It depends on what you need, so we quote up front once we understand it. No surprise invoices, no lock-in and you own what we build.
Smaller pieces like an application pipeline or payment plans can be quick. Bigger systems are planned in stages so you get the first win early, ideally before your next intake.
We do. We host it on our own managed servers and keep it updated and secure. When you need something you ring the people who built it.
Usually, yes. Most coding schools we work with keep what's working and upgrade the rest in stages. We move your data across, connect the old and new while we switch and retire the old system only when the new one is proven.
Contact
Tell us what's slow, broken, manual or missing. You don't need a spec, just describe what's going on.