VADIXCaptain — product tour
Products · Guided tour

Captain — the meeting assistant that never sends your audio anywhere

Eight steps through a live meeting: two-sided transcript, real-time suggestions, risk and deadline alerts, and a final summary with action items — with transcription and the language model running on your own machine.

Captain UI recreated faithfully
Meeting content is a scripted sample
No real customer data is shown
Captain — AI Meeting Assistant
Sample meeting data
Live Meeting
Meeting title…
🎙 Start Listening⏸ Pause⏹ Stop
Device:System audio (Speakers — WASAPI loopback)⟳
✓Also capture my microphoneMicrophone Array
Template:Sales CallParticipants (comma-separated, optional)…
Not listeningInput level:
LIVE TRANSCRIPT
🎙
No meeting running

Press Start Listening (Ctrl+L) to begin transcribing.

AI RECOMMENDATIONS
✨
Recommendations appear here

During a meeting the AI suggests responses, questions, and strategies, ranked by priority.

IMPORTANT ALERTS
Live Meeting
Pilot kickoff — Northwind Logistics
🎙 Start Listening⏸ Pause⏹ Stop
RECORDING — transcribing live  ·  04:12Input level:
LIVE TRANSCRIPT
[10:03:48] Them: Understood. The other question from our ops lead is timing.
[10:03:55] Them: Can your team ship the integration by the twenty-eighth?
[10:04:02] Me: That is tight, but workable if scope is locked this week.
[10:04:09] Them: That date matters because the warehouse go-live is the first of next month,
[10:04:12] Them: so the integration has to land before it.
AI RECOMMENDATIONS
❓ QUESTION· Request DetailHigh priority
Which systems does the integration have to cover — WMS, ERP, and the carrier API, or a subset?
Scope has to be locked this week for the twenty-eighth to be realistic.
💬 RESPONSE· SummarizeMedium priority
So the integration needs to be live before the warehouse go-live on the first — the twenty-eighth gives us three days of buffer.
Restating the constraint confirms you understood the real deadline.
IMPORTANT ALERTS
⏱ Deadline — integration before go-live on the 1st📋 Action — confirm systems in scope
Transcript
Pilot kickoff — Northwind Logistics
🔍 Search transcript…
🔍 Find next
[10:02:31] Them: Thanks for making time. Quick recap from our side.
[10:02:38] Them: We are ready to move on the pilot, but pricing needs sign-off from finance before anything starts.
[10:02:49] Me: Understood — I will send the revised pricing with the scope attached.
[10:02:57] Them: Right, and legal wants the master services agreement finalized first. That is the gating item.
[10:03:48] Them: Understood. The other question from our ops lead is timing.
[10:03:55] Them: Can your team ship the integration by the twenty-eighth?
[10:04:02] Me: That is tight, but workable if scope is locked this week.
[10:04:09] Them: That date matters because the warehouse go-live is the first of next month,
[10:04:12] Them: so the integration has to land before it.
[10:04:31] Me: There is some risk on our side.
[10:04:36] Me: The inventory system is still being upgraded, so the API may change mid-stream.
[10:05:02] Them: Agreed. So the decision today is: we proceed with the pilot, pending the MSA,
[10:05:09] Them: and we target the twenty-eighth for the integration.
[10:05:24] Them: Action items. We will send the revised MSA by Wednesday.
[10:05:31] Them: You send the updated proposal with the pilot scope and pricing by Friday.
[10:05:44] Me: And we still need to confirm which systems the integration has to cover.
[10:05:58] Them: Perfect. Let us regroup next Tuesday to review.
Suggestions
Pilot kickoff — Northwind Logistics
❓ QUESTION· Request DetailHigh priority10:04:14
Which systems does the integration have to cover — WMS, ERP, and the carrier API, or a subset?
Scope has to be locked this week for the twenty-eighth to be realistic.
💬 RESPONSE· SummarizeMedium priority10:04:14
So the integration needs to be live before the warehouse go-live on the first — the twenty-eighth gives us three days of buffer.
Restating the constraint confirms you understood the real deadline.
❓ QUESTION· ClarifyHigh priority10:04:41
If the inventory API changes mid-upgrade, who owns the interface contract — your team or ours?
You just raised a risk; naming the owner now prevents it becoming a dispute later.
🧭 STRATEGY· ChallengeMedium priority10:05:12
The MSA is the gating item, not the integration date. Ask what specifically is outstanding in legal review.
The date cannot be committed to while the contract that authorizes the work is unsigned.
💬 RESPONSE· Request detailMedium priority10:05:33
Happy to send the proposal Friday — can you confirm the MSA is with legal now, or still with procurement?
Ties your commitment to theirs, so both dates move together.
AI Chat
Private conversation with the AI — other meeting participants never see it. During a meeting, answers use the recent transcript as context.
You
What did they commit to, and what did I commit to?
Captain
They committed to sending the revised MSA by Wednesday and confirming which systems the integration must cover. You committed to sending the updated proposal with pilot scope and pricing by Friday, and to targeting the twenty-eighth for the integration. Their pricing sign-off from finance and the signed MSA are both still open.
You
What is the biggest risk to the twenty-eighth?
Captain
Your own inventory-system upgrade — you flagged that the API may change mid-stream. Nobody assigned an owner for the interface contract, so that ambiguity is the most likely cause of a slip.
Ask the AI anything privately…
➤ Send🗑 Clear
Summary
Pilot kickoff — Northwind Logistics
⭳ Export Markdown
✓ Final summary — generated when the meeting ended.
Tone: 😊 Positive — collaborative and constructive; both sides converged on a shared date and named the blocking item without friction.

The call confirmed intent to proceed with the pilot, gated on two open items: finance sign-off on pricing and a finalized master services agreement, which the client identified as the true blocker. Timing was anchored to the warehouse go-live on the first of next month, making the twenty-eighth the integration target. One material risk was raised on the vendor side — an in-flight inventory-system upgrade that may change the API mid-stream — and no owner was assigned for the interface contract.

Key points
  • Pilot is approved in principle; pricing awaits finance sign-off
  • The MSA is the gating item, ahead of any technical work
  • Integration must land before the warehouse go-live on the 1st
  • Inventory API may change mid-upgrade — unowned risk
  • Systems in scope for the integration are still unconfirmed
Decisions
  • Proceed with the pilot, pending execution of the MSA
  • Target the twenty-eighth for the integration delivery
  • Regroup next Tuesday to review both open items
Action Items
Pilot kickoff — Northwind Logistics
✉ Follow-up email
Send the updated proposal with pilot scope and pricing
Explicitly committed on the call; ties to their finance sign-off.
OwnerMeDue Friday
Send the revised master services agreement
Named as the gating item for all downstream work.
OwnerThemDue Wednesday
Confirm which systems the integration must cover
Scope must be locked this week for the 28th to hold.
OwnerThemDue this week
Assign an owner for the inventory API interface contract
Raised as a risk; left unassigned on the call.
OwnerUnassignedBefore the 28th
Regroup to review MSA status and pricing
Agreed close-out of the call.
OwnerBothNext Tuesday
Settings
✨ AI Provider📶 Local AI⚙ Profile🎙 Transcription📋 Templates🌙 Appearance✓ Privacy
Where suggestions, summaries, and chat come from. Transcription is always local — only transcript text is sent to the provider.
ProviderLocal AI
PresetOllama (local)
API keyEnter API key…
Local server URLhttp://127.0.0.1:11434/v1
Local modelqwen3:1.7b
Suggestion interval20.00 s
📶 Test connection🔍 Detect local AI💾 Save settings

Captain is free — yours to keep, no trial, no expiry

  • Audio never leaves your machine — transcription runs on-device with Faster-Whisper
  • Point it at a local model (Ollama, LM Studio, llama.cpp) and nothing leaves at all
  • Or bring your own OpenAI-compatible or Azure OpenAI endpoint — only transcript text is sent
  • Two-sided transcript: system-audio loopback for them, your microphone for you
  • Consent gate, retention auto-delete, and per-meeting delete built in

Windows installer. The meeting shown in this tour is a scripted sample — no customer data, real or otherwise, appears anywhere in this demo.

Download Captain — free Captain overview Talk to VADIX

Under the hood