wollopit Got a problem? →

Coding bootcamp applications, cohorts & payments

Coding schools: from application to cohort, automated. Applications, challenges and payment plans.

Applications by email, challenges marked by hand and payment plans tracked loosely. We build admissions and cohort systems for coding schools.

Looking for coding bootcamp admissions software?

Bootcamps run admissions, cohorts and payments. We build application flows with challenges, cohort management and payment plans.

Wollopit builds enrolment systems, parent and student portals, booking tools and websites for coding schools around how you actually teach and run things. We connect the tools you already use, replace the ones holding you back and look after the lot on our own servers, so you can spend more time teaching and less time on admin.

01The problems

What we hear from coding schools

Does your coding school have these problems? Here's how we'd fix them.

Most coding schools we talk to spend their evenings on enrolment emails, invoices and spreadsheets instead of the work they love.

  • The problemApplications by emailHard to review.
    How we fix itApplication pipeline.
  • The problemCoding challengesMarked by hand.
    How we fix itChallenge submissions.
  • The problemCohortsSpreadsheets.
    How we fix itCohort management.
  • The problemPayment plansTracked loosely.
    How we fix itInstalment plans.
  • The problemStudent portalResources scattered.
    How we fix itStudent portal.
  • The problemCareer outcomesTracked loosely.
    How we fix itOutcome tracking.
02What we build

Solutions

What we build for coding schools. Usually all talking to each other.

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.

01

Application pipeline

Reviewed in stages.

02

Challenges

Submitted and reviewed.

03

Cohort management

Start dates and groups.

04

Payment plans

Instalments.

05

Student portal

Resources and schedules.

06

Outcome tracking

Graduate results.

03How it changes

Before and after

A new cohort, wolloped.

Here's how a typical day could change. Every business is different, so we map yours first.

Before

  1. Applications in inboxes
  2. Challenges emailed
  3. Spreadsheet cohort
  4. Payments chased

After

  1. Pipeline reviewed
  2. Challenges submitted
  3. Cohort set
  4. Instalments automatic
04Services

Everything under one roof

Software, websites and systems for coding schools.

Whether you're starting fresh or upgrading what you've got, it's one team from the first sketch to the support call.

Custom software for coding schools

Built around how your coding school actually runs: application pipeline, challenges and the admin in between, in one system you own.

Websites for coding schools

Fast, hand-built websites that rank for the searches your customers make and turn visits into enquiries, bookings or orders.

Coding school system upgrades

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.

Apps and portals for coding schools

Cohort management and payment plans: customer and staff portals that work on any phone without an app store.

Integrations and automation

We connect Google Workspace, Microsoft 365 and Stripe so information moves on its own and nobody retypes it.

Hosting, support and care

Managed hosting, updates, backups and security for your coding school, looked after by the people who built it.

05Integrations

Connections

Plays nicely with what you already use.

We connect to the tools you rely on, work alongside the ones you're happy with or replace the ones holding you back.

  • Google Workspace
  • Microsoft 365
  • Stripe
  • Xero
  • Zoom
  • Mailchimp
  • Twilio SMS
  • Google Calendar
  • Canva
  • YouTube
06How we work

The process

Some people dip their toe in. We turn up in a rebreather.

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.

  1. 01

    Think

    We spend time with the people doing the work, see where the hours go and work out what's actually slowing you down.

  2. 02

    Archi-tech

    We plan it before writing code: your data, customers, payments, the tools you keep, hosting and cost.

  3. 03

    Build

    Real engineering, shown to you early and often. Usually the most painful bit first, so you get a win quickly.

  4. 04

    Look after

    We host it, maintain it and keep improving it. When something breaks you call the people who built it.

07Questions

FAQ

Things coding schools ask us.

Something else on your mind? Ring 0423 011 252 and ask the people who'd build it.

Can applicants submit code challenges online?

Yes. Applicants can submit links or files for review in the pipeline.

How much does it cost?

It depends on what you need, so we quote up front once we understand your coding school. No surprise invoices, no lock-in and you own what we build.

Can families pay and enrol online?

Yes. Enrolments, payments, payment plans, sibling discounts and reminders can all run online without anyone chasing them.

How do you handle children's information?

Carefully. Access is restricted to the people who need it, connections are encrypted and we only collect what's actually needed, following the Australian Privacy Principles.

Who looks after it once it's built?

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.

We already have systems. Can you upgrade them instead of starting again?

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

Got a coding school problem? Consider it wolloped.

Tell us what's slow, broken, manual or missing. You don't need a spec, just describe what's going on.

I've got