Skip to main content

PortfolioCase study

TS-01Live pilot · Twilio sandbox

TeachSpark

Ready-to-use worksheets, on WhatsApp.

A WhatsApp bot that helps a time-poor Indian K–12 teacher use AI for real classroom work — a differentiated worksheet in about two minutes.

TeachSpark's live landing page on a phone: “Ready-to-use Worksheets on WhatsApp”, a smiling green mascot and a Get started button.
  • 17

    teachers joined the pilot on WhatsApp

    Measuredas of 24 Aug 2026

    first week, test handsets excluded

  • 47%

    activated (8 of 17)

    Measuredas of 24 Aug 2026

    12 of 17 onboarded first (71%)

  • 37.5 min

    median time saved

    Self-reportedas of 24 Aug 2026

    as reported by activated teachers

Evidence keyMeasuredSelf-reported

The teacher’s problem

Generic AI doesn’t transfer into a teacher’s real week.

Teachers want AI to give them time back, but what exists is generic, fragmented and disconnected from their subject, grade and board. It started with one real teacher: Tushar’s mother, who teaches Sanskrit.

When I’m overwhelmed by prep and grading, help me solve this week’s specific teaching task with AI, so I get real time back… without having to become a techie first.

— Job-to-be-done of “Meera”, the Discovery PRD persona

The WhatsApp experience

One two-minute chat, from “where do I start?” to a worksheet.

No new app, no prompt-writing. The teacher answers a few questions in WhatsApp and gets a ready-to-use worksheet as a PDF, plus the reusable prompt behind it.

The loop, as specified in the Final PRD
  1. Welcome + value
  2. Grade, subject, board
  3. 30-second micro-lesson
  4. Pick the topic
  5. Worksheet PDF + reusable prompt
  6. Minutes saved
  7. Share with a teacher
An illustrative WhatsApp chat: the teacher asks for fractions, answers grade 5, Mathematics and CBSE, gets a micro-lesson, picks equivalent fractions and receives a worksheet PDF.
The loop as drawn in the Final PRD (illustrative chat)

Product decisions

Capability, not dependency.

  • Could have
    Do the task for her: a worksheet-vending service
    Chose
    Teach the reusable skill, then show the time saved
    Because
    Problem-led, applied, capability-building learning with impact feedback was the corner nobody occupied.
  • Could have
    A standalone app with a new install and login
    Chose
    WhatsApp, where teachers already are
    Because
    Distribution, not a new destination — through a Twilio sandbox for the pilot cohort.
  • Could have
    Reposition it as an AI-learning course
    Chose
    Lead with the worksheet; teach inside the product
    Because
    The mentor’s challenge: “A teacher buys a worksheet that is good enough to give to her students tomorrow.”

How it works

A pure state machine behind one chat.

  1. Teacher on WhatsApp
  2. Twilio webhook
  3. Express server
  4. Pure state machine(teacher, message, now) → next step
  5. ClaudeSonnet 5 default; Haiku 4.5 switchable
  6. PDF / DOCX render
  7. Back to WhatsApp
One message’s trip through TeachSpark

Activation funnel

A real first week: 17 teachers joined, 8 activated.

32 event types were instrumented, and Tushar’s own test handsets are excluded from every number. The pilot came in under the targets it set for itself.

  1. 72Landing views
  2. 17Signed up · 23.6%
  3. 17Joined on WhatsApp
  4. 12Onboarded · 71%
  5. 8Activated · 47%
  6. 5Question papers exported
First-week pilot, Final PRD snapshot, test handsets excluded Measured as of 24 Aug 2026
  • 3

    referrals

    Self-reportedas of 24 Aug 2026

  • 1 of 4

    re-engaged by a nudge

    Measuredas of 24 Aug 2026

What isn’t measured

  • Under target: joined 40–50 and activation ≥ 60% were the goals.
  • D1 retention couldn’t be measured: the window was shorter than 24 hours.
  • No teacher interviews were recorded and no LLM output-quality evals exist.

What I learned

Three lessons from the first week.

  • Sell the worksheet, not “AI”

    Lead with the artifact a teacher can use tomorrow; deliver the learning inside it.

  • Green tests aren’t correctness

    335 passing tests still shipped a city map that placed zero sign-ups: teachers typed “Bangalore” four ways.

  • Smaller, honest numbers

    Excluding my own test handsets the day before submission made every number smaller — and true.

Sources

Everything here is backed by a real artifact.

  • PRD
  • Design
  • Architecture
  • Code
  • Test run
  • Feedback
  • Post
  • Deck
  • Live data

Evidence behind the TeachSpark case study

Private working documents are listed with what they support; only public sources link out.

  1. Discovery PRD

    PRD19 Aug 2026

    Supports: The problem statement and the “Meera” persona

  2. Solution-Space PRD

    PRD19 Aug 2026

    Supports: Capability, not dependency; the WhatsApp wedge

  3. Final PRD

    PRD26 Aug 2026

    Supports: The pilot funnel (snapshot 24 Aug 2026) and the targets

  4. 2-minute WhatsApp loop

    Design

    Supports: The seven-step product loop

  5. Runbook

    Architecture

    Supports: WhatsApp → Twilio → Express → state machine → Claude → PDF/DOCX

  6. Question-paper adapter

    Code

    Supports: Structured outputs, vision and the QC pass

  7. QA phase-6 gate

    Test run21 Aug 2026

    Supports: 335 passed / 2 skipped

  8. Mentor feedback

    Feedback29 Aug 2026

    Supports: Sell the worksheet; WhatsApp is not the whole differentiation

  9. 9-day build series

    Post

    Supports: The excluded test handsets, the city lookup, D1

  10. Pitch deck

    Deck

    Supports: It started with one teacher: a mother who teaches Sanskrit

  11. Live pilot (Railway) (opens in a new tab)

    Live data

    Supports: The live landing; uptime after 9 Sep 2026 is unverified

Links and next steps

Solo buildAug 2026Live pilot · Twilio sandbox