Programs / AI, Technology & Entrepreneurship

Fellowship · AI, Technology & EntrepreneurshipONWARD

Future AI Leaders Fellowship

Three build weekends where your child ships a real AI product using Claude, Cursor, Lovable and Perplexity - ending in a live Demo Day and a public Builder Profile.

Apply for November →

Next cohort starts Sat, 14 Nov 2026 · early-bird USD 499

Decide by 4 NovCohorts of Small live cohort

Length3 weekends · 6 live build days
Cohort sizeSmall live cohort
EligibilityGrades 8–12 (13–17)
Live sessionsSat & Sun, 5:00 PM–7:00 PM GMT+4 (Sat & Sun, 9:00–11:00 AM ET) · live on Zoom

What your child will actually do

Live, mentor-led sessions - worked problems and real output, not lectures.

1
Find a problem worth solving

Start from something your child actually cares about, then scope it down to something buildable.

2
Build with professional AI tools

Claude, Lovable, Cursor and Perplexity used the way working builders use them - not toy exercises.

3
Ship a working product

A live link other people can use, iterated on with mentor feedback across the build days.

4
Present at Demo Day

A short founder-style demo to mentors and parents, with a recorded demo video to keep.

Skills your child will gain

Named, practised skills - grouped the way universities read them, tied to how each is used in this fellowship.

Building & doing

The hands-on craft that turns an idea into a finished artefact.

  • Python fundamentals

    Used directly on the work your child hands in across 3 weekends · 6 live build days.

  • Prompt and model evaluation

    Learnt by building the real artefact, not by following a tutorial.

  • Building with no-code and AI tools

    Refined through revision rounds until the output is portfolio-ready.

  • Product thinking and scoping

    Used directly on the work your child hands in across 3 weekends · 6 live build days.

  • Documenting work in a repo

    Learnt by building the real artefact, not by following a tutorial.

  • Demoing to non-technical adults

    Refined through revision rounds until the output is portfolio-ready.

Projects they finish with

Sample briefs from recent cohorts - the actual work that comes out of the programme, not a syllabus.

Project 1

An AI tool that solves your child's own problem

“What small, annoying task could a model do better than a human?”

What they hand inA working prototype with a public link or repo.

Weeks 2–6
Project 2

Model evaluation write-up

“Does it actually work - and how would we know?”

What they hand inA short evaluation report with prompts, failures and fixes.

Weeks 5–7
Project 3

Two-minute demo video

“Can a non-technical adult understand it in two minutes?”

What they hand inA recorded demo any university or family member can open.

Final week
A working AI build, with a repo and a demo

Your child ships something that actually runs - an AI tool or agent solving a problem they chose - documented in a public repository with a short demo video anyone can open.

What you end up holding
  • A working prototype with a public link or repo
  • A two-minute demo video
  • A written build log showing the decisions made

What they'll take away

Certificate of CompletionA live AI product with a public linkPublic Builder ProfileDemo video for applications

How this strengthens their university profile

The point isn't the certificate. It's the line a family can honestly write afterwards - and the artefact sitting behind it.

Before

"My child is interested in ai, technology & entrepreneurship."

Nothing an admissions officer can check.

After Future AI Leaders Fellowship

"My child completed Future AI Leaders Fellowship and finished a working AI build, with a repo and a demo."

A line with an artefact behind it.

Why this fellowship counts

Depth. A fellowship is the spine of a profile - several weeks with one mentor, one field and one finished piece of work at the end. This is what turns "interested in medicine" into evidence.

Builder evidence: something that runs, with a repo and a demo behind it.

What a university can verify
  • A working prototype with a public link or repo
  • A two-minute demo video
  • A written build log showing the decisions made
  • A finished capstone or research piece
  • Mentor feedback in writing

Upcoming cohorts

Starting soon
Sat, 14 Nov 20263 weekends · 6 live build days · Grades 8–12Batch 2
Sat & Sun, 5:00 PM–7:00 PM GMT+4(Sat & Sun, 9:00–11:00 AM ET)
USD 499USD 699early birdApply for this cohort
Sat, 20 Feb 20273 weekends · 6 live build days · Grades 8–12Batch 3
Sat & Sun, 5:00 PM–7:00 PM GMT+4(Sat & Sun, 9:00–11:00 AM ET)
USD 499USD 699early birdApply for this cohort

Session times shown in Dubai time (GMT+4) with US Eastern alongside. Fees are correct at time of publishing - confirm on the programme page.

A 1:20 Harvard mentor ratio on every build day

Build days are staffed so that no student sits stuck. Mentors are Harvard students who build with these tools themselves and review each product as it is shipped.

Parents usually ask

Does my child need to code?

No. The tools are AI-first, so students go from idea to working product without prior programming experience - though coders go deeper.

What will they have to show afterwards?

A live product link, a demo video and a public Builder Profile - all of which sit well in a university application.

Is a laptop required?

Yes, a laptop with a stable connection. Everything else runs in the browser.

Families looking at this also consider

USD 499USD 699Early bird · next cohort 14 Nov
Apply now →