Skip to content
शिक्षाby Grow10x
An Indian school courtyard and classroom block at break time
For schools

A clear scope.A confident launch.

Pilot one class first. Agree the timetable, kit and safety checks in writing. Review the evidence every twenty sessions. Grow only when you are satisfied.

  • Pilot firstOne class
  • 30 learnersTeams of three
  • 2 × 60 minEach week
  • Every 20 sessionsEvidence review
One school, four steps

A thoughtful launch, from first call to review.

  1. 01

    Discover

    We agree class groups, prior exposure, calendar, room, devices and the outcomes you want.

  2. 02

    Prepare

    Kit tested, staff trained, tool and account rules approved, families informed.

  3. 03

    Pilot

    One class runs the first project. We review the evidence and fix practical issues.

  4. 04

    Deliver & review

    Attendance, project evidence, safety and progress are tracked at every milestone.

  1. Agree scope
  2. Close kit gaps
  3. Rehearse
  4. Pilot one class
  5. Review evidence
The operating model

What one class needs. Nothing you will not see coming.

A planning baseline for 30 learners in teams of three. We adjust ratios for age, access needs and the room, and agree them in your proposal.

1 + 1
Lead trainer and a school adult

In every session, with roles adapted for access needs.

12
Kit positions per class

10 team kits, 1 spare and 1 trainer demo kit.

1
Computer per team

Plus a shared display and approved software.

2 × 60
Minutes a week

Two one-hour sessions, timetabled around exams.

Delivery team
  • Academic delivery

    Us:Class plan, project briefs, guided teaching and the rubric.

    School:Approves class groups, curriculum fit and the timetable.

  • Room & devices

    Us:Agreed technical requirements and test materials.

    School:Room, computers, display, power and network access.

  • Equipment

    Us:Only the items named in the quote, with a kit record.

    School:Ownership, storage and use rules for kits.

  • Safeguarding

    Us:Pre-reviewed demos, non-personal data, a clear escalation route.

    School:Accounts, consent, supervision and parent communication.

  • Classroom support

    Us:Leads instruction and practical guidance.

    School:A named, responsible adult in every session.

  • Review

    Us:Milestone evidence, and early flags on any delay or change.

    School:Reviews progress, approves changes, hosts exhibitions.

Checkpoints

Evidence on a calendar, not on request.

  1. 1

    Before launch

    The exact kit and every tool tested on your school computers.

  2. 2

    After project one

    A pilot review of evidence, timing and practical issues.

  3. 3

    Every 20 sessions

    An evidence and readiness review, with a short progress summary.

  4. 4

    At completion

    Portfolio handover and equipment reconciliation.

For school leaders

  • Programme prospectus
  • Class-wise plan for your duration
  • Implementation proposal
  • Project evidence and a showcase

Behind the scenes, for the delivery team

  • Academic blueprint
  • AI tools and permissions guide
  • Trainer handbook and forms
  • Project library and live planner

A curriculum system, not an isolated workshop: transparent counts, defined outcomes, labelled fallbacks and documented hardware checks.

What we tell families

Students build low-voltage classroom models, use code and explore AI through examples, testing and evidence checks. Some activities are teacher-led, and no personal online account is needed for the core programme. The school's own consent and safeguarding process governs participation, and photos or exhibitions need separate permission.

Questions & answers

Questions school leaders ask.

Timetables, scope, staffing and reporting.

No. It is an enrichment programme informed by recognised frameworks such as UNESCO's AI competencies and CBSE's CT & AI curriculum. It does not replace a prescribed subject or claim any board's approval.

Yes, and we recommend it. A pilot with one class runs the first project, we review the evidence together, and you expand only when you are satisfied.

It changes the maths. Twenty 45-minute periods give 15 hours, not 20. To keep a plan's full scope, schedule at least 27 periods, or agree a smaller scope in writing.

A room, one computer per team of three, a shared display, a named school adult in every session, and two one-hour sessions a week. Kits and equipment are agreed in your proposal.

It is planned for the board year. Build cycles are compact, sessions are timetabled around exams, and the capstone scope is agreed in writing at the start. A school can also choose the 3 or 6-month plan so the work ends before the pre-boards.

Every twenty sessions you receive an evidence and readiness review: projects completed, individual checks and a short progress summary. At the end you receive each learner's portfolio.

Two teachers guiding uniformed students as they build a robot car in a classroomFor school leaders

Choose a starting point.
Build from evidence.

Pick the classes and a plan. We map the timetable, kit and safety checks with you, then pilot one class first.

  • Prospectus and class-wise plan
  • Kit and readiness check
  • Pilot one class first
  • Evidence at every milestone
School enquiry

Let's plan your pilot.

Share a few details and we will send the right plan for your classes.

Classes you are considering

No spam. We reply within two working days. Prefer email? shiksha@grow10x.io