Case study · Papare Academy
We ran a real coding bootcamp before we built the platform for it.
Before betaPlan was a product, it was a problem we lived. Papare Academy was a real bootcamp, a 12 sprint path from HTML and CSS through JavaScript, React and Next.js, taught live over Zoom and Google Classroom by a volunteer mentor team.
Historical evidence, not current-product proof
This case applies to the named engagement and period. It does not prove outcomes from betaPlan current microcourses, training, workshops, qualification or human-evaluation work.
500+
Registrations
231
First-cohort students
12
Sprints, HTML to Next.js
247
Unique learners
8
Completed all 12
The operational reality
Run by hand, on Classroom and spreadsheets.
The interest was immediate. More than 500 registration responses came in, and 231 students filled the very first cohort. But every sprint had its own Google Classroom, its own roster and its own pile of assignments to grade. Attendance, progress, project links and mentor notes lived across half a dozen spreadsheets that we updated by hand, week after week.
Coordinating 231 learners that way meant chasing the same questions on repeat. Who is in which room, who submitted, who still needs access to the next classroom, who is quietly falling behind. The very tools that let us launch fast soon became the thing slowing us down.
The course is good, but the structure can get complicated. There are several groups, and since it was my first online course, it was easy to lose track of which room to join.
The vetting funnel
Every step down is the filter working.
Attrition on a free, self-paced, online cohort is expected. We read it as signal. The people who remained had shipped real, working software, sprint after sprint, under deadline and review.
Registered
500+ (100%)
Raised their hand
Started sprint one
231 (46%)
First live cohort
Reached the React sprints
43 (9%)
Still shipping weekly
Completed all 12
8 (2%)
Proven end to end
Overall it has been a very positive experience. It is genuinely helping me improve my coding skills.
Talent deliverables
Real applications, shipped by vetted talent.
A functional React application built during the programme. Create, complete, edit and delete, with state handled cleanly. All identifying details removed.
The outcome
What it proved.
The 8 who completed all 12 sprints had shipped real, working software under deadline and review, sprint after sprint. That is not a certificate of attendance. It is a record of what each person built, unaided.
Papare Academy shows a historical method: sustained work, deadlines and recorded deliverables produced stronger evidence than attendance alone. Applying that lesson to a different profession still requires current professional rules, human assessment and authorised evidence.
What this historical record supports.
It supports betaPlan experience running sustained learning and keeping work evidence. It does not establish a ready current professional bench or prove current human-evaluation outcomes.