How 40 Prompt Revisions Turned Claude AI Summaries Into a Product: A Tutoring Platform Case Study ($19K MRR)

A tutoring platform generating $19K MRR shared their 12-month journey of refining a Claude AI prompt for session summaries sent to parents. The founder documented every one of the 40+ revisions, demonstrating how prompt engineering is iterative, not one-shot.

The Prompt Evolution

Version 1 (Month 1): "summarize this tutoring session." Output was generic and vague, missing specific topics.

Version 12 (Month 3): Added structure requirements: "include: topics covered, areas for improvement, homework assigned, progress notes." Output became structured but robotic.

Version 25 (Month 6): Added tone requirements: "write as a caring educator speaking to a parent. be specific about progress. be encouraging but honest about areas needing work." Output improved significantly — parents started responding.

Version 40 (Month 12): Added context persistence: the prompt now references previous session summaries for that student. "this student previously struggled with factoring. note whether today's session showed improvement." Output became personalized and longitudinal.

Key Takeaways

• The quality of summary data determines the quality of downstream visual progress tracking — an AI presentation tool for parent-facing slide decks showing improvement over 10+ sessions feeds from these summaries.
• Prompt v1 is a starting point; v40 is a product. The iteration between the two is where the value lives.
• For developers building with Claude: expect to iterate heavily on prompts. Document every change.

Who This Is For

Developers building AI-powered features for products, especially in education, customer communication, or any domain requiring structured, personalized text generation.