Skip to content

Use cases

Every team asks its own questions, and Leon answers from the same sources.

Leadership, sales, support, product, project managers and new hires look for different things in the same tools. Here is what they type into Leon, and what comes back.

In practice

What Leon does on an ordinary workday.

What Leon does today, at the moment it matters. People, companies and details are fictional.

  • Monday, 9 a.m.

    Resume where you left off

    Developer, 25-person SaaS company

    where was I on the billing repo?

    She left a migration half done on Friday. When her session starts, the repo’s morning briefing is already in her coding assistant: what she did, the review that came in since, the reopened issue, what is still open.

    Impact: She and her assistant start from the right place, without reopening three tabs.

    Her coding sessions
  • Before rewriting a module

    Check what the team already decided

    Developer, 12-person startup

    have we already tried generating PDFs in the browser?

    He has his coding assistant query Leon over MCP. Leon returns the PR closed in March, the review explaining why it was dropped (broken rendering of accented characters) and the decision record in Notion.

    Impact: The assistant doesn’t repeat a dead end the team already paid for, or it flags what has changed since.

  • Rerunning an analysis from last month

    Retrieve what you worked out with your AI assistant

    Product manager, 40-person company

    the cohort retention query without the test accounts

    In September he built the query with his AI assistant, edge cases included. The conversation, captured by the extension, comes back in one search next to the ticket that requested the chart. Only he can see it.

    Impact: The final, corrected query, with the reasoning that led to it.

    His AI conversations
  • 10 p.m., an error in an unfamiliar module

    Find out whether the incident has happened before

    On-call developer, 30-person SaaS company

    has this import error happened before?

    Leon returns the Sentry issue from March, the PR that fixed it, the incident ticket and the postmortem. The next day, a chat turns them into a first draft of the new postmortem.

    Impact: She applies the known workaround instead of paging the module’s author.

  • 30 days before a renewal

    Everything that went wrong with this account

    Customer success manager, 70-person SaaS company

    what went wrong with Nordia over the past year?

    He inherited the account in June. Leon cross-references support conversations, bugs linked to the client, recorded calls and CRM notes, then reports what is fixed, with dates, and what is not.

    Impact: He walks into the renewal meeting already knowing every complaint on record.

One search bar

Pick a team and see what it asks.

Each tab shows a team’s queries and the results Leon returns. The data is fictional.

Know exactly what you promised. Source included.

A meeting three months ago, a signed quote, an email thread. When a client disputes scope, Leon retrieves the record and cites it. When there is no record, it says so.

  • Cited answersEvery sentence links to the meeting, note or email it comes from. One click opens the original.
  • Departures without data lossAnything a person wrote in the team’s shared tools stays searchable after they leave.
  • The original wordingLeon stores every item verbatim, so you quote what was actually said.

Team tools: HubSpot, Outlook, Granola, Notion, Asana, Fathom

See the full use case
what did we promise ACME for V2?
Leon’s answer3 sources

At the Oct 3 monthly check-in, Julie committed to delivering V2 on Nov 15 source 1. The signed quote confirms the date but excludes the data migration source 2, and the migration ticket is still open source 3.

  1. [1]ACME monthly check-in

    Meeting · Julie Martin · Oct 3, 2026

    “We can commit to November 15 for V2, history migration excluded.”
  2. [2]Signed V2 quote

    Note · Karim Benali · Oct 7, 2026

    Delivery on 11/15/2026. The data migration is quoted separately.

Fictional example

Start with one team.

Connect its tools from 42 connectors and ask the first question.