Skip to content

For government & public sector

Delivery at system scale, with evidence you can publish.

Public-sector STEAM programmes succeed or fail on three questions: whether existing teachers can deliver them, whether cost per learner survives contact with scale, and whether outcomes can be measured by someone who does not work for the supplier. This page answers all three.

The binding constraint

Specialist teachers cannot be hired at district scale

Any model requiring a robotics specialist in every school is undeliverable across a district, let alone a province. This one is designed around in-service teachers and shared infrastructure, because that is the only variable a department actually controls.

Delivery constraints compared across models
ConstraintConventional modelThis model
Teaching capacityRecruit a specialist per schoolCertify existing science and IT teachers in post
Hardware costOne kit per studentSimulator-first; shared kits at cluster level
ConnectivityAssumes stable broadbandLow-bandwidth delivery, offline-tolerant content
MeasurementAttendance and enrolment countsAssessed outcomes and per-learner evidence
VerificationSupplier-reported figuresPublic certificate verification, checkable by any third party
ContinuityEnds with the contractLearner records persist beyond the programme

Accountability

What you can report, and how it is verified

Each of these is designed to be defensible without our involvement — which is the only kind of evidence worth having in a public programme.

01

Cost per learner

Modelled at district and provincial volumes with the assumptions stated openly, including what happens to unit cost if enrolment lands below forecast. The sensitivity is published, not hidden in a footnote.

02

Monitoring & evaluation

Baseline, midline and endline framework aligned to standard public-sector reporting, designed so a third-party evaluator can run it without our participation.

03

Independent verification

Every learner certificate carries a public verification link. An auditor, a journalist or a successor administration can check any individual claim directly.

The M&E framework, cost model and data-protection documentation are available as a single pack for procurement review.

Existing public-sector work

Delivered, not proposed

Programme documentation — cleared for publication

Provincial partnership programme

In-service teacher enablement delivered with a provincial education department, structured so the capability remains with the department after the engagement closes.

Districts
Confirmation required
Learners reached
Confirmation required
Teachers certified
Confirmation required
Evaluation status
Confirmation required
Launch-state gate — This case does not publish until scope, districts, learner numbers and outcome data are confirmed and cleared by the partner department. A public-sector case study with unsourced figures is a liability for both parties, not an asset.

Procurement

Documentation prepared for public process

Available on request, ahead of any commercial conversation.

Compliance

Registration, tax status and standard vendor documentation

Safeguarding

Child protection policy, staff vetting and incident escalation

Data protection

Learner data handling, retention, residency and minor-specific rules

Financial

Audited statements, cost model and payment structure

Start with a briefing, not a proposal.

A single session covering the delivery model, the cost structure at your volumes, and how outcomes would be measured and published.