Fit and priorities
We review the firm’s objectives, intended users, data boundaries, and the decisions the system must support.
Private briefing / Law firms
Put the right people in the room.
A useful first conversation should include the business case, the technical architecture, and the duties that govern client and firm information.
Architecture session
Your legal, security, knowledge, and technology stakeholders can examine deployment, retrieval, adaptation, governance, and ownership.
Diligence path
If there is a fit, we define the evaluation, security review, contracting, and implementation questions required for a responsible decision.
Request a conversation
Tell us what your firm is evaluating.
SOC 2GDPR
Do not submit client names, matter details, privileged communications, personal data, or other confidential information through this form. We can establish an appropriate review process before sensitive materials are discussed.
A diligence-first conversation
Trust should survive technical review.
The briefing is a starting point for evidence, accountable owners, explicit data boundaries, and clear contractual responsibilities.
Review securitySOC 2
Security controls
Review the organizational and technical controls used to protect customer systems and information.
GDPR
Privacy governance
Discuss processing boundaries, minimization, retention, access governance, and applicable customer obligations.
DILIGENCE
Evidence before commitment
Bring security, privacy, procurement, knowledge, and technology stakeholders into the evaluation process.
Before the briefing
A clear beginning to a serious review.
01Who should join the first briefing?+
The right group depends on the evaluation. Managing partners, innovation leaders, knowledge teams, CIOs, CISOs, privacy, legal operations, and procurement may all have relevant questions.
02Can our security and privacy teams participate?+
Yes. The page is designed to begin a diligence path, not avoid one. Architecture, data boundaries, access, retention, incident response, compliance, and contractual responsibilities can be addressed with the appropriate stakeholders.
03Should we send sample matters or client documents?+
No. Do not transmit privileged, client-confidential, personal, or matter-specific information through the contact form. An appropriate process should be established before sensitive material is reviewed.
04Can we discuss a firm-controlled deployment?+
Yes. Deployment requirements—including dedicated environments and firm-controlled cloud or VPC preferences—can be included in technical scoping.
05What happens after the form is submitted?+
The inquiry is reviewed for fit and the questions that need to be addressed. If there is a relevant next step, the conversation can expand into architecture, security, evaluation, contracting, and implementation diligence.