shivam.
Open to roles
View work Résumé
Summer Associate · Product & Strategy (AI) · Stealth AI Startup · May → Dec 2025

Voice AI Coaching

Voice AIMVPProduct strategy
MVPInitial product scope
VoiceConversation workflow
FeedbackIteration with users
Inside the workflow

From a conversation to a useful follow-up.

Post-call reviewIllustrative view
01 · Conversation excerpt

“I’ll send the revised plan after our next meeting.”

Synthetic example of a commitment expressed during a session.

02 · Commitment to check

Send the revised plan

Timing: after the next meeting. A calendar date has not been confirmed.

What was captured → What was inferred → What to verify
  1. Capture

    Bring the live conversation into the workflow.

  2. Reflect

    Turn the session into feedback the user can examine.

  3. Clarify

    Separate stated commitments from AI interpretation.

  4. Follow up

    Make the post-call report useful for the next step.

The product judgment

Treat transcription, feedback and commitment accuracy as separate quality questions. A fluent report still needs to represent the conversation faithfully.

Illustrated from this case study. Examples are synthetic and contain no customer data.

The short version

Product work on a real-time coaching MVP. From conversation capture to feedback, commitments and a useful post-call report.

The full story

A coaching product has to earn its place in a conversation. Capturing everything is not enough; the experience needs to help people understand what happened and what to do next.

The product

During my Product & Strategy internship at a stealth AI startup, I was the sole PM on an early voice AI coaching product. The MVP brought together transcription, conversation feedback, commitment tracking and post-call reports.

My contribution

I worked from the initial concept through the MVP and an initial paying customer. My focus was to define the core use case, prioritize the features that supported it and use conversations with users to guide the next iteration.

That meant treating scope as a product decision. A useful first release needed a coherent path from the live session to the follow-up, before expanding into more channels and integrations.

What good looks like

A transcript can be accurate while a summary misses the point. A report can sound confident while misrepresenting a commitment. I think about those as separate quality questions: what was captured, what was inferred and what the user can verify.

What I learned

Being the sole PM taught me to make tradeoffs explicit. The roadmap is only useful when the team understands the customer problem behind each decision and what evidence would change it.

Next case studyAin Center