Retrieval

Keyword vs semantic

Left is the OpenSearch ceiling: keyword only, no embeddings. Right is Elastic + Jina: meaning as numbers, so different wording can still surface the same deals.

Keyword — OpenSearch ceiling

9 hits

  • Call notes — Acme general counsel

    Unstructured notes / S3 · notes

    4.00

    GC: we cannot accept perpetual commitments. Legal concerns around switching costs if we standardize on one collaboration stack. They used the phrase 'we are worried about being stuck' more than 'lock-in'.

    • Exact token “legal” in Unstructured notes / S3
    • Exact token “concerns” in Unstructured notes / S3
    • Exact token “about” in Unstructured notes / S3
  • QBR recording — Acme collaboration owners

    Webex recording transcript · webex

    4.00

    Transcript excerpt: 'We like Webex quality but legal is nervous about being unable to unwind. Same conversation as the slide deck they sent — vendor lock-in fears, not product complaints.' Multimodal: deck screenshots + audio + notes should share one vector space.

    • Exact token “legal” in Webex recording transcript
    • Exact token “about” in Webex recording transcript
    • Exact token “vendor” in Webex recording transcript
  • Umbrella Corp — legal hold on email archive

    Salesforce (via MuleSoft) · crm

    4.00

    This deal is about e-discovery legal hold, not collaboration lock-in. Keyword 'legal' matches loudly. Semantic ranking should demote it when the query is about vendor lock-in fears on a Webex renewal.

    • Exact token “legal” in Salesforce (via MuleSoft)
    • Exact token “about” in Salesforce (via MuleSoft)
    • Exact token “vendor” in Salesforce (via MuleSoft)
  • Acme Corp — Webex Calling + Control Hub renewal

    Salesforce (via MuleSoft) · crm

    3.00

    Legal flagged exclusive multi-year terms. Counsel described vendor lock-in fears and asked for exit clauses. Similar to last year's Acme campus Wi-Fi refresh. Notes mention procurement wants price-hold and FedRAMP evidence.

    • Exact token “legal” in Salesforce (via MuleSoft)
    • Exact token “vendor” in Salesforce (via MuleSoft)
    • Exact token “lock-in” in Salesforce (via MuleSoft)
  • Acme counsel slide — 'switching costs'

    Presentation deck (image + text) · webex

    3.00

    Slide OCR: Switching costs · exclusive term · data escrow. Image of a lock icon. No occurrence of the words 'legal concerns' — only 'switching costs'. Jina v5 multimodal is why this matches a text query about legal concerns.

    • Exact token “legal” in Presentation deck (image + text)
    • Exact token “concerns” in Presentation deck (image + text)
    • Exact token “about” in Presentation deck (image + text)
  • Globex — Meraki + ThousandEyes overlay

    Salesforce (via MuleSoft) · crm

    1.00

    Network refresh for 140 branches. Buyer is infrastructure, not legal. Price sensitivity on AP density. No counsel involvement yet.

    • Exact token “legal” in Salesforce (via MuleSoft)
  • Initech — Webex for Government

    Salesforce (via MuleSoft) · crm

    1.00

    FedRAMP High path. Security questionnaire references data residency US Gov East + West. Counsel wants audit trails on who searched what. Similar motion to Acme but security-led rather than commercial legal.

    • Exact token “legal” in Salesforce (via MuleSoft)
  • Acme invoice pack — Q2 professional services

    S3 · lifecycle

    1.00

    Large unstructured payload (~10 MB equivalent in lab). Line items: Webex Calling migration, number porting, analog adapter replacements. Hidden in XML: 'counsel requested termination for convenience'. Keyword search on invoice ID misses this; semantic search surfaces legal language inside the payload.

    • Exact token “legal” in S3
  • Order orchestration log — ACME-4419

    Elastic · lifecycle

    1.00

    Elastic log: MuleSoft flow order-create retried 3x. Downstream CCW reservation delayed. Not a legal document — ops signal that the deal is stuck in provisioning, not in counsel.

    • Exact token “legal” in Elastic

Semantic — Elastic + Jina

11 hits

  • Call notes — Acme general counsel

    Unstructured notes / S3 · notes

    16.45

    GC: we cannot accept perpetual commitments. Legal concerns around switching costs if we standardize on one collaboration stack. They used the phrase 'we are worried about being stuck' more than 'lock-in'.

    • Shared concept · legal-review
    • Shared concept · vendor-lock-in
    • Shared concept · switching-cost
  • QBR recording — Acme collaboration owners

    Webex recording transcript · webex

    16.30

    Transcript excerpt: 'We like Webex quality but legal is nervous about being unable to unwind. Same conversation as the slide deck they sent — vendor lock-in fears, not product complaints.' Multimodal: deck screenshots + audio + notes should share one vector space.

    • Shared concept · legal-review
    • Shared concept · vendor-lock-in
  • Acme counsel slide — 'switching costs'

    Presentation deck (image + text) · webex

    16.30

    Slide OCR: Switching costs · exclusive term · data escrow. Image of a lock icon. No occurrence of the words 'legal concerns' — only 'switching costs'. Jina v5 multimodal is why this matches a text query about legal concerns.

    • Shared concept · vendor-lock-in
    • Shared concept · legal-review
  • Umbrella Corp — legal hold on email archive

    Salesforce (via MuleSoft) · crm

    16.15

    This deal is about e-discovery legal hold, not collaboration lock-in. Keyword 'legal' matches loudly. Semantic ranking should demote it when the query is about vendor lock-in fears on a Webex renewal.

    • Shared concept · legal-hold
  • Acme Corp — Webex Calling + Control Hub renewal

    Salesforce (via MuleSoft) · crm

    15.30

    Legal flagged exclusive multi-year terms. Counsel described vendor lock-in fears and asked for exit clauses. Similar to last year's Acme campus Wi-Fi refresh. Notes mention procurement wants price-hold and FedRAMP evidence.

    • Shared concept · legal-review
    • Shared concept · vendor-lock-in
  • Acme invoice pack — Q2 professional services

    S3 · lifecycle

    14.30

    Large unstructured payload (~10 MB equivalent in lab). Line items: Webex Calling migration, number porting, analog adapter replacements. Hidden in XML: 'counsel requested termination for convenience'. Keyword search on invoice ID misses this; semantic search surfaces legal language inside the payload.

    • Shared concept · legal-review
    • Shared concept · vendor-lock-in
  • Globex — Meraki + ThousandEyes overlay

    Salesforce (via MuleSoft) · crm

    14.15

    Network refresh for 140 branches. Buyer is infrastructure, not legal. Price sensitivity on AP density. No counsel involvement yet.

    • Expanded synonym / embedding neighborhood (workshop replica of Jina ranking)
  • Initech — Webex for Government

    Salesforce (via MuleSoft) · crm

    14.15

    FedRAMP High path. Security questionnaire references data residency US Gov East + West. Counsel wants audit trails on who searched what. Similar motion to Acme but security-led rather than commercial legal.

    • Shared concept · legal-review
  • Acme — 6 month transaction rollup

    Snowflake · lifecycle

    14.15

    Snowflake fact table: 14 Webex Calling seat expansions, 2 Control Hub add-ons, 1 professional services SOW. Payload pointers to 8.4 MB XML invoices in S3. Account id ACME-4419.

    • Expanded synonym / embedding neighborhood (workshop replica of Jina ranking)
  • Order orchestration log — ACME-4419

    Elastic · lifecycle

    14.15

    Elastic log: MuleSoft flow order-create retried 3x. Downstream CCW reservation delayed. Not a legal document — ops signal that the deal is stuck in provisioning, not in counsel.

    • Expanded synonym / embedding neighborhood (workshop replica of Jina ranking)
  • CCR + local search — US Gov East / West

    Internal runbook · infra

    14.15

    Cross-cluster replication keeps Webex and CRM indices in both gov regions. Search locally with the same synonyms and ranking. Do not send queries across the US-Gov boundary at query time.

    • Expanded synonym / embedding neighborhood (workshop replica of Jina ranking)