Mindvalley Stories
Case Study · AI Mastery

They turned per-student employer emails into one tracked request per employer

A manual emailing process became an automated one: 44 students, 35 grouped employer emails, close to 3 hours saved each cycle.

This student looked at a tedious emailing routine and saw a structure problem instead of a workload problem. By reordering the process on tools their team already used, they saved close to 3 hours a cycle and kept a person in charge of every send. It is a quiet, practical win that shows how much a clear way of thinking can change.

Barbara Yam
Someone who manages student placements and employer communication, working with everyday Microsoft tools.

Automated employer emails

Before

Employer emails went out one student at a time. For a 44-student cohort, that meant a separate message for each placement, followed by ad hoc chasing to get surveys back. It was a one-to-one email system trying to solve a many-to-one problem.

“Mapped where the process broke: a one-to-one email system used for a many-to-one problem.”

In their own words

The turning point

During the program they mapped exactly where the process broke. Instead of adding new tools, they grouped the placement data by employer contact first, so consolidated drafts simply fell out of the structure. They built it with Excel, Power Automate, Outlook, Microsoft Forms and Copilot, and vibe-coded a live browser demo in HTML and JavaScript with a Claude API layer for email tone.

“Kept the send manual - the system assembles, a person checks.”

In their own words

After

The cohort now needs 35 grouped employer emails instead of 44, saving about five minutes each and close to 3 hours a cycle. Each employer gets one tracked, auditable request, with a target of at least 90% survey completion. The send stays manual by design: the system assembles, a person checks.

What it lets people do

Staff can reach every employer with one clear, consolidated request instead of chasing messages one by one. Every request is tracked and auditable, and a human still reviews each email before it goes out.

What they learned

They came away convinced that many workload problems are really structure problems, and that the gain came from reordering the process rather than piling on tools. AI earned its place as a targeted layer, and the human review step became part of the design rather than a limitation.

“Most "workload problems" are structure problems in disguise - the gain came from reordering the process, not adding tools.”

In their own words

Automated employer emails was built during AI Mastery.

Read the full submission
Achievements Turned a manual, per-student employer emailing process into an automated one. Consolidated a 44-student cohort into 35 grouped employer emails (9 fewer), saving ~5 min each, close to 3 hours a cycle and replaced ad hoc chasing with one tracked, auditable request per employer, targeting ≥90% survey completion. Tools Excel, Power Automate, Outlook, Microsoft Forms, Copilot. Live browser demo vibe-coded in HTML/JavaScript, with a Claude API layer for email tone. Methodology Mapped where the process broke: a one-to-one email system used for a many-to-one problem. Grouped the placement data by employer contact first, so consolidated drafts fall out of the structure. Kept the send manual - the system assembles, a person checks. Minimum intervention, on tools already in use. Learnings Most "workload problems" are structure problems in disguise - the gain came from reordering the process, not adding tools. The AI is a targeted layer, not the engine, and the manual review checkpoint is the design, not a limitation.

Written 9 August 2026 Submitted by the storyteller

Every story is written by a Mindvalley student or by someone our teachers have worked with. How we collect and check stories

More from AI Mastery

Automated employer emails: a AI Mastery case study | Mindvalley Stories