How it works

From conversation
to intervention.

TiQ is a five-layer system. Each layer is designed for one purpose: to surface the right insight at the moment it can still change something.

The pipeline

Five stages. One purpose.

Every suggestion TiQ surfaces has traveled this entire pipeline — in under five seconds from when you last spoke.

// 01
Audio capture
Chrome extension captures both sides of the conversation — your microphone and the meeting tab audio — merged into a single stream.
Chrome Extension
→
// 02
Transcription
Deepgram Nova-3 converts audio to final transcripts in real time. Only confirmed utterances enter the reasoning engine — interim results are discarded.
Deepgram Nova-3
→
// 03
Conversation buffer
A 120-second sliding window accumulates final utterances. A hybrid trigger gate decides when there's enough new signal to call the reasoning engine.
In-memory only
→
// 04
LLM reasoning
The reasoning engine receives the transcript window plus session context, memory, and radar state. It returns structured suggestions and the current conversation state.
GPT-4o / Claude
→
// 05
Private delivery
Confidence-gated suggestions appear on your dashboard only. Nothing is read aloud, nothing is visible to others. A strategic whisper, not an announcement.
Your screen only
Before the meeting

The briefing that makes suggestions surgical.

TiQ asks five questions before you start. The answers transform suggestions from interesting to precise.

1
Who are you in the room?
Your role shapes everything — which questions are relevant, which risks matter, what language to use. A software architect needs different prompts than a product leader.
→ Impact: Loads your persona configuration. Questions, risk types, and panel layout adapt to your role.
2
What kind of meeting is this?
An architecture review needs different intelligence than a stakeholder alignment or a client negotiation. Session type selects the Conversation Radar model.
→ Impact: Selects the radar model (Decision / Alignment / Relationship). Determines which conversation states TiQ watches for.
3
Meeting brief — goal, decision, strategy, stakes
Four inputs that prime the reasoning engine. This is where TiQ stops being a transcript analyzer and starts being a strategic advisor. Takes ten seconds.
→ Goal: gives TiQ a compass. Suggestions evaluate whether the conversation is moving toward it.
→ Potential decision: TiQ watches for forming signals, missing checkpoints, and blockers.
→ Strategy: Persuade / Defend / Explore / Align / Inform / Negotiate — shifts which suggestion types are prioritized.
→ Stakes: Critical meetings get higher confidence thresholds. Fewer suggestions. Each one more precisely timed.
4
LLM provider and API key
Bring your own OpenAI or Anthropic key (BYOK), or use TiQ-managed access with no configuration. Your key is held in browser memory only — never stored.
→ BYOK: Key held in React component state for session duration. Cleared on session end. Never written to localStorage, database, or logs.
5
Privacy acknowledgement and launch
One sentence confirming your conversation stays yours. Chrome is primed to ask tab audio permission. Everything is ready before you click Start.
→ On Start: Session token issued. WebSocket established. Audio capture begins. Dashboard goes live.
What TiQ surfaces

Four types of intelligence.
Each earned at a different threshold.

Questions to Ask
The highest-value panel. Surfaces questions the conversation hasn't answered — clarifying, probing, risk-oriented. Ranked by relevance. The question that could change the meeting outcome appears at the top.
Confidence ≥ 0.70
// Example
RANK_01 // SLA_BOUNDARY
"Has the inter-service latency been validated against the 99.9% SLA already committed to customers?"
A deployment decision is forming but the SLA impact hasn't been confirmed.
Risk Flags
Unaddressed assumptions, gaps in coverage, decisions being made without essential information. Maximum three active flags at any time. Auto-dismisses when the topic is addressed in subsequent conversation.
Confidence ≥ 0.78
Decisions Log
Captures explicit decisions as they are made — with a session-relative timestamp. Tracks the forming and confirmation lifecycle. You walk out with a permanent record of everything decided, without taking a single note.
Confidence ≥ 0.80
Action Items
Commitment language detected in real time — who said they'd do what. An interactive checklist that you can check off during the session. Copy the full list with one click when the meeting ends.
Confidence ≥ 0.75
Conversation Radar

TiQ knows where the meeting
is heading, not just what was said.

On every reasoning call, TiQ classifies the conversation state. Three models — each mapped to a meeting type.

Decision Model
Architecture review · Vendor selection · Scope discussion
Exploring Progress
Aligning Progress
Decision forming Progress
Commitment Progress
Objection Interrupt
Drift Interrupt
Alignment Model
Team meeting · Cross-functional · Stakeholder
Misaligned Progress
Converging Progress
Aligned Progress
Tension Interrupt
Stalled Interrupt
Relationship Model
1:1 · Coaching · Discovery · Negotiation
Guarded Progress
Opening Progress
Trust building Progress
Resolution Progress
Resistance Interrupt
Breakdown Interrupt
Quality gate

Silence is better
than a bad suggestion.

Every suggestion type has its own confidence threshold. Lower stakes allow more exploration. Higher stakes demand precision. Below threshold — nothing is surfaced.

Suggestion type Minimum confidence Rationale
Question
0.70
Questions are low-risk. Being slightly off is acceptable — the user can discard the question. Exploration has value.
Action Item
0.75
Commitments matter. A false action item creates confusion about who owns what. Higher bar than questions.
Risk Flag
0.78
False risk flags erode trust quickly. If TiQ cries wolf, users stop reading flags. High bar protects credibility.
Decision
0.80
Highest stakes. A wrong decision log entry causes confusion, disputes about what was agreed, trust breakdown.
🔒
Everything described above stays in memory.
The audio, the transcripts, the LLM prompts, the suggestions — none of it touches a database or log file. When your session ends, the pipeline clears. The full privacy architecture is documented separately.
Read the privacy architecture →
Ready to use it

See the pipeline
in your next meeting.

Start with a single session. No commitment. The whole pipeline, live, in your next high-stakes conversation.

Start your first session Privacy architecture →