Meeting scorer — live demo

Select an industry below. The transcript and scoring rubric load automatically. Click Run to see a scored output.

Industry

💻

Tech consulting session

A technical mentor reviews a scholar's accessibility glasses project with a counsellor and a parent liaison. Scored on project clarity, evidence, and next steps.

Transcript input

~680 words · Tech consulting

Sarah Mitchell: Hello, Mrs. Green! Good to have you join today.
Mrs. Green: Hi Sarah, good to see you. Shall we wait for James?
Sarah Mitchell: He's just joining now. James, are you there?
James Carter: Yes, I'm here. Sorry, just got off another call.
Sarah Mitchell: No worries. So today we wanted to loop you in on Alex's accessibility glasses project — the competition forms are due soon and we need some of the technical detail filled in.
James Carter: Sure, I've gone through the two documents the team shared. A few things weren't clear to me. Specifically — how do the glasses actually communicate with the user? The documents describe what the product does but not how it does it.
Mrs. Green: Yes, so they have haptic feedback and also audio feedback. Go left, go right, that kind of thing.
James Carter: Right. But as a user, how do I learn what the haptic means? Is there an instruction manual? If I feel two taps, does that mean turn left? There needs to be a user onboarding document.
Sarah Mitchell: That's a great point. Mrs. Green, I think what we should do is create a Google Doc with specific comment threads — exactly what information we need and where — and share that with Alex's team. They can address each comment and send it back. Once we have all of it, we can edit and submit.
Mrs. Green: Yes, that works. So you'll send me that document?
Sarah Mitchell: Exactly. We'll have it ready within a few hours after this call.
James Carter: I also want to flag the scalability question. The form asks about next steps for the product. My view is — don't touch manufacturing now. That's a money and time sink. The right move is to get validation first. Make five units, go to a nonprofit, run real tests, collect feedback.
Mrs. Green: That makes sense. And cost-wise, they've mentioned around fifty dollars per unit right now.
James Carter: That's manufacturing cost, not distribution cost. Those are different things. When you produce at scale, the cost per unit drops significantly. If they secure a small grant, distribution cost can come down to something a nonprofit can actually afford.
Sarah Mitchell: Exactly. And for context — a similar project last year, smart glasses for the visually impaired, came in at around fifteen dollars per unit at scale. If Alex targets the same bracket — under twenty-five dollars at distribution — that's a compelling number for competitions and nonprofits alike.
James Carter: Agreed. Let's keep that as the benchmark.
Sarah Mitchell: Alright. So to close — James and I will share the comment document with you by this evening. You forward it to Alex's team. Once they respond, we edit and submit. Alex and James will sync as soon as he's back from his trip — probably day after tomorrow.
Mrs. Green: Perfect. Thank you both.
James Carter: Thank you. Good session.

Scored output

Ready

◎

Select an industry and click Run to score this transcript

Rubric: Technical Project (Type H)

ℹThis demo uses pre-scored synthetic examples — no real client data is used and no API calls are made. In production, transcripts are processed in memory and never stored. The scored output is what gets emailed to each team member and shown on their dashboard.