For SpaceXSI's higher-education team · one page · October 2026

Phase 0a: one semester of Grok Bot Team Bots in a 150-student Iowa State course

One course, one semester, on products and plans that exist today. No new features, no student data in the bot, and a public write-up of what we learn. SpaceXSI can count it as one of its pilot classes. The Cursor section (DS 2010) goes through Cursor's own campus credits program, not through this request.

Term Spring 2027, late January to early MayCourse AI 2010, Introduction to Applied AI, 150 non-major studentsSeats 156: 150 students, 2 instructors, 4 TAsPlan Grok Bot on Teams, one course teamYour time my estimate, under 20 hours

The ask

Education credit for 156 Grok Bot seats for one semester, in whatever form is simplest on SpaceXSI's side, plus one named contact. Everything else below is what Iowa State brings.

Scope

  • One course team, one named ISU admin. Students join with institution accounts.
  • Synthetic systems only: a sample CRM, a mailbox of synthetic tickets, a demo storefront. No LMS connector, no student email, no submissions, no grader bot.
  • Team Bots published by the instructor: a Socratic tutor, a lab partner on the sandbox, and one weekly routine. Connector policy set at the team level.
  • Controls in scope on Teams: template sharing team-only, connector policy, per-bot Auto Review rules. Noted where an Enterprise-only control would have helped, so you learn which one a department would want next.

Usage, so nobody is surprised in week 9

Plan of record: two bot sessions per student per week plus one shared weekly routine, 14 weeks. Usage counts against each seat, so I will track consumption weekly from week 2 and report where a seat runs out. If a seat exhausts before term end, the remaining labs run instructor-side; the exhaustion point is itself a result.

What Iowa State brings

  • Two instructors and four TAs who have taught the course for years, and a 150-student section to run it in.
  • The course material: outline, labs, assessments and the three class bots, written and tested here (course outline).
  • A comparison section: the same course taught in fall 2026 without the bots.
  • Weekly usage tracking and a mid-term note.
  • A public write-up at the end, with a factual review by SpaceXSI before release.

What SpaceXSI gets back

  • Usage per seat per week across a real 150-student section.
  • Whether Teams-tier controls are enough for a course, and which control a department would want next.
  • What students learn with a class bot, against the section taught without one.
  • A case study for the higher-education session series, if you want one.
  • A tested course template, the first of the catalogue on the full page.

Timeline

WhenMilestone
NovemberAgree the shape of the credit and the named contact. Instructor starts building the three bots on the sandbox.
DecemberCourse team created; bots published; TAs onboarded.
January to MayTerm runs; weekly usage tracking from week 2; mid-term note in March; draft write-up to you in May for factual review, published two weeks later.

Beyond this course

If the semester goes well, the natural next steps are on the full page: an educator community that gives SpaceXSI a standing channel to the people who choose classroom tools, and a catalogue of complete course templates that make adopting Cursor and Grok Bot the easiest option an instructor has. This page is only the first class. adisaksukul.com/spacexsi-education

Adisak Sukul · Teaching Professor of Computer Science, Iowa State University · adisaksukul.com · linkedin.com/in/adisaksukul · Full proposal and evidence: adisaksukul.com/spacexsi-education. Independent; not affiliated with SpaceX, SpaceXSI or Cursor.