Sample output
One meeting in. This report out.
Below is a real run: a demo client meeting on the left, and everything Whaler produced from it on the right — extracted facts with the exact words that back them, compliance flags, action items, and a follow-up email the advisor can edit and send.
Generated on 2026-07-28 by running the production pipeline over this transcript and writing the output straight to a file. Nothing on this page was hand-edited — including the parts a careful advisor would still want to fix before hitting send.
15.9s
Transcript → report
4.8s
Follow-up draft
3
Planner iterations
1099
Output tokens billed
Review portfolio performance and update personal circumstances following client's recent marriage, including beneficiary changes and discussing concentration risk.
Key decisions
2Plan to trim Apple holdings to reduce concentration risk
Apple has grown to almost a third of the account, creating concentration risk that the client is nervous about
“That's a concentration risk. We don't have to act today, but I'd suggest we look at trimming it next time.”
Update beneficiary designation to add Emily
Client recently married and wants to ensure his spouse is taken care of
“Absolutely. We should update your beneficiary designation to add Emily.”
Action items
3Send beneficiary designation form to John
advisor · due this week
“I'll send you the form.”
Send full fee breakdown to John
advisor · due this week
“I'll include the full fee breakdown with the beneficiary form.”
Revisit Apple position at next review
advisor
“I'll send both this week, and we'll revisit the Apple position at our next review.”
Compliance review
3Beneficiary change
highBeneficiary-related change discussed. Ensure required forms and signatures are completed.
key_decisions[1].decision“Update beneficiary designation to add Emily”action_items[0].task“Send beneficiary designation form to John”KYC update needed
mediumLife event mentioned that may require KYC profile update.
key_decisions[1].rationale“Client recently married and wants to ensure his spouse is taken care of”Fee disclosure
mediumFee or commission discussed. Confirm disclosure documentation is on file.
action_items[1].task“Send full fee breakdown to John”Flags come from a deterministic rule engine reading the extracted facts — zero tokens, and every flag names the exact field and phrase that triggered it. The planner decides whether a meeting warrants review at all; the rules decide what specifically is flaggable.
Follow-up email draft
Subject: Follow-up from our meeting on April 21 Hi John, Thank you for meeting with me yesterday. It was great to catch up and hear about your recent marriage — congratulations again. Here's what we discussed and decided: We reviewed your portfolio performance and talked about the concentration risk from your Apple holdings, which have grown to nearly a third of your account. You mentioned feeling nervous about this, so we agreed to trim that position. We also discussed updating your beneficiary designation to add Emily now that you're married. Next steps: My action items: - Send you the beneficiary designation form (this week) - Send you the full fee breakdown (this week) - Revisit the Apple position at our next review Please let me know if you have any questions or if I missed anything from our conversation. Best regards, Sarah
Drafted from the extracted facts only — never the raw transcript — so it can't cite anything the advisor hasn't already reviewed above. It's a draft: the advisor edits and sends, nothing goes out automatically.
Run telemetry
- Stop reason
- end_turn
- Planner iterations
- 3
- Tool calls
- extract_structured_facts ×1, flag_compliance_issues ×1
- Input tokens
- 940
- Output tokens
- 914
- Cache read
- 3525
Token accounting is tracked per planner turn and per tool call, cache hits included — the same telemetry the product surfaces on every meeting. How the whole thing is built →
This is what lands seconds after you say goodbye. Whaler is in early access, free, and onboarding independent advisors now.
Get early access →