Reference solution for taking one recorded meeting or conversation through transcription, deterministic segmentation, discussion analysis, structured outcome extraction, optional insight and verification passes, and a written follow-up output.
Unit event
Meeting Analysis Request
MEETING_ANALYSIS_REQUESTOne recorded meeting or conversation processed into a transcript-derived understanding, decisions, action items, insights, and written follow-up output.
Design variant
A 60-minute recording, one transcription, deeper discussion analysis, structured-outcome extraction, a separate insight pass, a separate verification pass, and a detailed written follow-up.
Every value this design resolves, and who owns it. Change an editable value and the figures recalculate. The pricing engine answers, not this page: nothing here multiplies anything, and until it answers the figures beside you are the ones you were already looking at, labelled as such.
61 fields
How much context about the meeting travels with it into analysis.
How long the recording runs. The only quantity the audio meter reads, and the one that must never become a token count.
How many people spoke. Explanatory only: this catalogue has no diarization Rate, Service or model requirement, and §4 forbids inventing one.
How large the transcript is expected to be. A Scenario assumption, not a conversion from duration: §2 forbids inferring one from the other.
How long the recording runs. The only quantity the audio meter reads, and the one that must never become a token count.
How much of the transcript this step reads.
How large the formatted transcript is.
How many conversation segments were cut. Explanatory only.
How many people spoke. Explanatory only: this catalogue has no diarization Rate, Service or model requirement, and §4 forbids inventing one.
The instructions this step is given.
Input tokens eligible for cached-input treatment.
How much analysis the model is expected to write.
How much of the meeting metadata this step reads.
How much of the transcript this step reads.
Input tokens eligible for cached-input treatment.
How much of the discussion analysis this step reads.
How much structured outcome text is expected.
The instructions this step is given.
How much of the transcript this step reads.
Input tokens eligible for cached-input treatment.
How much of the discussion analysis this step reads.
How much insight text is expected.
The instructions this step is given.
How much of the extracted outcomes this step reads.
How much of the transcript this step reads.
Input tokens eligible for cached-input treatment.
How many verification notes are expected.
How much of the generated insights this step reads.
How much of the extracted outcomes this step reads.
How much of the transcript this step reads.
The instructions this step is given.
Input tokens eligible for cached-input treatment.
How much of the discussion analysis this step reads.
How much follow-up output is expected.
The instructions this step is given.
How much of the generated insights this step reads.
How much of the extracted outcomes this step reads.
How much of the transcript this step reads.
How much of the verification notes this step reads.
Where the direct unit cost comes from. Expand an operation for the activities inside it and how each one resolved.
Receive the recording and normalize it. No storage or network charge: this catalogue has no canonical authority for one.
Receive Meeting Recording
No pricing requestAccept the recording and normalize it for transcription. Ingestion only.
This activity does not price. No request was made, so there is no amount — not an amount of zero.
Recognize the speech, then segment and format the transcript locally.
Transcribe Conversation
PricedRecognize the recorded speech and produce a transcript.
A pricing request was made and returned an amount.
Normalize / Segment Transcript
No pricing requestFormat and segment the transcript and preserve whatever speaker and timestamp metadata already arrived with it.
This activity does not price. No request was made, so there is no amount — not an amount of zero.
Read the transcript and state what was discussed and decided.
Analyze Discussion
PricedRead the conversation and state its summary, topics, decisions and open questions.
A pricing request was made and returned an amount.
Pull decisions, action items, owners, dates, risks and open questions.
Extract Structured Outcomes
PricedPull decisions, action items, owners, dates, risks and open questions out of the conversation.
A pricing request was made and returned an amount.
Reason across the conversation, then check the result against it.
Generate Conversation Insights
PricedReason across topics for themes, implications, follow-up requirements, risks and unresolved issues.
A pricing request was made and returned an amount.
Verify Meeting Outcomes
PricedCheck whether the extracted outcomes and insights are supported by the transcript. A check, not a guarantee.
A pricing request was made and returned an amount.
Write the summary, the lists and the follow-up draft.
Produce Meeting Follow-up
PricedWrite the meeting summary, decision and action-item lists, and the follow-up draft.
A pricing request was made and returned an amount.
Direct unit total
0.7348 USDBars show each operation’s share of the stated direct unit total. An operation with no priced activity shows no amount, which is not an amount of zero.
Activity states not exercised by this configuration
The read model reports these so their absence reads as absence rather than as coverage.
Issues
The runtime reported none for this configuration.
Technical detail and reproducibility