Skip to main content
Yuzu turns GTM activity into deal signal. A signal is an observed event with enough context to affect a deal, a trigger, or a generated follow-up artifact.

​
Signal sources

Yuzu can collect signal from:
  • Notetaker transcripts and manual transcript uploads
  • Gmail sends, opens, clicks, and replies
  • Google Calendar meetings, created invites, and scheduled buyer follow-ups
  • LinkedIn post reactions and comments
  • Public Yuzu Link views
  • Rendered-video views, completions, and CTA clicks
  • Manual deal events and notes
  • LinkedIn and company enrichment from verified profile or company-signal sources

​
How signal reaches a deal

When a new event lands, Yuzu tries to resolve the workspace, user, deal, contact, and source artifact. If it can attach the event to a deal, the deal activity feed updates and the deal agent can re-evaluate the next actions. Signals are normalized before they reach the deal agent. That keeps the model focused on what happened instead of making it infer event meaning from raw webhook payloads. Enrichment jobs are treated as supporting evidence. LinkedIn, company, and PredictLeads-style signals can improve routing, people matching, company context, and deal briefs, but buyer-facing claims still need to be grounded in calls, emails, calendar events, public engagement, or saved deal material.

​
Triggers

Triggers are recurring patterns or conditions that should change the seller’s behavior. Examples:
  • Buyer asks for a timeline and pricing.
  • A meeting is scheduled with a buyer contact.
  • A stakeholder engages with a LinkedIn post.
  • A public page is viewed after a period of silence.
  • A video is watched to completion and the CTA is clicked.
  • A contact replies with a concrete objection or request.
Triggers can feed next actions, content suggestions, and agent-generated work. Signals can also feed GTM digests. Digests package active buyer deals, buyer-package review work, and stale opportunities into email so sellers can get pulled back into Yuzu without treating the inbox as the system of record. For deal next actions, Yuzu keeps buyer-package work visible when it exists: TLDR recap, business-case page, and follow-up email, with LinkedIn included when there is a relevant post. The trigger decides the current path-to-close move, such as drafting a procurement email, preparing a LinkedIn post, sending a calendar invite, or asking for missing context through an email draft. Not every signal should trigger a new TLDR render. Meeting intake and explicit seller actions create or refresh the package. Later opens, clicks, replies, or LinkedIn engagement should usually update signal and next actions without reprocessing the same video unless the deal has materially changed.

​
Deal signal level

Deal pages show signal level and reasoning when the agent has enough context. The current levels are:
  • High: recent multi-party motion, direct engagement, or urgent buyer action.
  • Medium: normal active motion with a clear next step.
  • Low: stalled, silent, or waiting on seller action without strong buyer engagement.

​
Regeneration

Click Regenerate on a deal when you want the deal agent to re-read the current state. Rapid clicks coalesce so a double-click does not create duplicate agent runs. When multiple events arrive close together, Yuzu queues one follow-up agent run instead of dropping the later signal or creating duplicate traces.

​
Tasks are not signal by default

Tasks is the seller work queue. Creating or moving a personal task does not automatically mean the deal changed. If a task represents real buyer activity, add the activity to the deal or let the connected source, such as Gmail or Calendar, create the signal.