We just raised $7M
→

Northwind Claims
⌄
Search
⌘K
AK

Northwind
Workspace
Overview
Ask Brief
Sources
Reviews
Admin
Ingestion
Members
Settings
Isolated workspace
Ask Brief
New question
What does our property policy say about water damage from a failed sprinkler?
Answer
Covered
Water damage from a failed sprinkler is covered under §7.3, subject to a $50,000 deductible and the maintenance condition in §7.5.
§7.3
§7.5
The exclusion applies only where maintenance was missed. Your last inspection was logged 14 days before the loss.
Ask a follow-up…
↑
The average adjuster touches four systems before writing a single note. Every handoff adds time, inconsistency, and risk.
01
Policies, endorsements, inspection reports, and internal memos live in systems that were never designed to answer a question.
02
A paragraph is not proof. Adjusters need the clause, the page, and the version before they can act.
03
Shared indexes and broad permissions turn a useful assistant into a new liability for every tenant.

Field note 01
Claims operations / 2026
No shared embeddings. No cross-tenant retrieval. No answer without a source.
01
Point Brief at the systems where claims knowledge already lives: policy admin, claims, SharePoint, and the warehouse.
02
Documents are parsed, versioned, and scoped to a single tenant. Every chunk carries its source, page, and date.
Clause-level retrieval
Every answer resolves to the exact section, not the whole document.
Versioned sources
Page numbers and effective dates travel with the quote.
Tenant-scoped access
Permission is checked at retrieval, before a single token is generated.
Open a sample answer
v4.2
Northwind Claims
Page 42
Section 7.3
This policy covers direct physical loss or damage caused by the accidental discharge or failure of a sprinkler system, subject to the deductible shown in the declarations.
§7.3
Water damage caused by the accidental discharge or failure of a sprinkler system is covered, subject to the deductible shown in the declarations and the maintenance condition in §7.5.
7.5
Maintenance condition
The insured must maintain the system in accordance with the inspection schedule.
7.6
Exclusions
Wear and tear, freezing, and damage caused by failure to maintain are excluded.
42 / 68
Accessed 14:32 UTC
Retrieved from Tenant 03 · access checked at query time
Brief keeps a complete ingestion record, so a source can always be traced back to its origin.
Connected
documents
Parsed
documents
Chunked
chunks
Embedded
vectors
Last sync 2h ago
0 failures
Tenant 03 only
No shared embeddings. No cross-tenant retrieval. No answer without a source.
Tenant boundary
enforced at retrieval
01
Northwind Claims
sealed
02
Meridian Mutual
sealed
03
Harbor Specialty
sealed
No shared index
0 cross-tenant paths
Separate indexes
Each tenant gets its own vector index, keys, and retention policy.
Access checked first
Permissions resolve before retrieval. A missing grant returns nothing.
No shared training
Prompts, documents, and citations never train a shared model.
cross-tenant reads
since inception
Read the security brief
The interface stays quiet. The evidence stays close.
Open the clause, the page, and the version before writing the note.
42%
faster first response
Trace every position back to the policy language and its effective date.
100%
source coverage
See what the team asked, what it cited, and where knowledge is missing.
1
tenant view

Maya Chen
VP Claims Operations, Northwind
Northwind Claims runs 12,000 property claims a year across six states. Brief is deployed inside their tenant, connected to policy admin and the claims system.
42%
faster first response
3.1h
saved per adjuster / week
0
cross-tenant reads
Connectors are read-only by default. Write-back is scoped and audited.
Read + write
Claims
Read only
Policy
Read only
Documents
SSO
Identity
Don’t see your system?
Build a connector with us
Ask us directly
Each tenant gets a separate index, encryption scope, and retrieval path. Permissions are checked before retrieval.
Every answer points to the exact document, page, and clause. If the source isn’t there, Brief says so.
No. Prompts, documents, and citations are never used to train a shared model.
Most teams connect their first sources in a week and roll out to a pilot group in two.
Pricing is per workspace, not per seat. Start with a pilot and expand when it sticks.
30-minute walkthrough · Your data stays yours.