For Hello PM
Your curriculum is built around three pillars: Learn, Practice, Career Support. Learn teaches the frameworks. Career Support connects students to opportunities. In Practice, students write PRDs, strategy docs, and roadmaps as assignments.
Student writes → submits to your reviewer → gets corrections → revises.
Here's what that looks like
A student finishes their PRD assignment. They've covered every section: problem, solution, metrics, timeline. It looks complete. They submit it.
After a while, the feedback arrives:
“What happens if your primary metric moves but nothing else changes? Where's your counter-metric? What's your kill criteria?”
They didn't know to ask those questions. Not because they weren't capable, but because those questions come from experience they haven't built yet.
That gap is what SPM addresses. The moment the document is finished, SPM reads it, scores every section against expert-level expectations, and surfaces the questions a senior PM would ask, before it ever reaches an instructor.
What if the student found those gaps themselves, before submitting?
Here's what happens with SPM
Same student. Same PRD. But before they submit, they click Analyze.
Analysis
SPM reads the full document.
Every section, every claim, every metric, mapped against what a senior PM would expect for a PRD. Not a generic checklist. A rubric customisable to match your curriculum's review criteria.
Gaps
Success Metrics: 30%
Not what's wrong, but what's absent. The assumptions they didn't state. The trade-offs they didn't weigh. The metrics they listed without baselines. Scored and surfaced before anyone reads it.
Clarifications
SPM asks what they didn't think through.
Each question comes from what the student actually wrote, not a template.
The student answers:
“We'll monitor engagement and see how it goes.”
SPM pushes harder:
The student thinks. Then writes:
“If weekly active usage drops below 15% within 30 days of launch, we kill the feature. Counter-metric: support ticket volume shouldn't increase by more than 10%.”
That answer didn't exist 60 seconds ago. SPM didn't teach it. The student reasoned their way to it.
Evaluation
SPM re-scores.
Every answer feeds back into the rubric. The student defined a north star and kill criteria, but baselines are still missing.
Scores can also go down. If an answer contradicts what they wrote in the document, SPM catches it.
Improve
SPM writes what they can paste directly.
Not generic suggestions. SPM takes what the student said (their north star, their kill criteria, their reasoning) and writes the actual Success Metrics section. Headers, baselines, instrumentation plan. Ready to paste into the PRD.
Typical improvement across three rounds of revision.
By the fifth time, they're already thinking about counter-metrics and kill criteria while writing their first draft.
The questions become theirs. The instinct to challenge their own thinking, before anyone else does.
And they start thinking like confident PMs.
SPM strengthens Practice layer, making it the differentiator HelloPM offers to students.
Who built this
Chiranjeevi Gunturi
Head of Product, Mapan at Gojek (2019-2023)
“I spent 15 years reviewing documents and coaching PMs, at Gojek, Ant Financial, Citi, DBS Bank. SPM automates the expertise I used to give one conversation at a time.”
SPM is available as a Chrome extension inside Google Docs and as a web app. Your students can use whichever fits their workflow.
We're open to customising the rubrics, the document types, and how SPM fits inside your curriculum. This is early. We want to build it with you, not for you.
hello@superproductmanager.com