LawVu as an ambient layer -
inside the tools people already live in
These integrations aren't just a pipe that pushes data into LawVu. They make LawVu show up where work actually happens - so people can see context, ask for knowledge, and take the next action without switching tools.
| Integration | Primary persona | Also reaches | Capabilities |
|---|---|---|---|
Outlook |
Legal Expert | - | SeeAskDo |
Gmail |
Legal Expert | - | SeeAskDo |
Salesforce |
Business User | - | SeeAskDo |
Teams |
Business User | Legal Expert | AskDo |
Slack |
Business User | Legal Expert | AskDo |
- Context-on-arrival speaks directly to how they work: reading the matter is something they do constantly and today requires leaving whichever tool they're in.
- Anything surfaced or actioned must require near-zero context switching; email and chat are where they live, not LawVu.
- Capture is the everyday behaviour; one-step matter/contract creation fits naturally into how they already triage email and messages.
- Their time is split across email and chat and the balance is shifting toward chat - so parity of experience across both surfaces matters; the needs don't change when they switch tools.
Commercial / contracts lawyers
High volume of counterparty correspondence across email and chat; surfacing the live contract version + key terms inline, and triggering approvals/redline workflows from wherever the message lands, is the hot path.
Litigation / disputes lawyers
Fewer but heavier, privilege-sensitive threads on long-running matters, so surfacing the correct matter's chronology/context and preserving thread integrity matters more than fast new-matter creation, and misfiling is costly. Upcoming milestones and obligations (court dates, response deadlines, filing windows) often arrive by email, so easy capture of these onto the matter as trackable key dates, and surfacing what's due when a related message lands, is high-value.
Broad generalists
Need fast disambiguation across many open matters, so smart matter-suggestion (for both surfacing and capture) pays off most.
Note on the Business Expert persona: We sometimes distinguish business users who aren't in Legal but frequently partner with it as a Business Expert. In LawVu, this might be someone like Nick Grady (finance) or Nick Breese (InfoSec) - people interacting with LawVu one way or another weekly, if not daily. For these integrations we treat them within the Business User card, since their needs are the same and they just engage more deeply.
- Structured-field capture at the point of request reflects how they want to engage legal: hand over the right detail once, without back-and-forth.
- Status visibility and knowledge answers are what they most want from LawVu showing up where they work - status stops them chasing legal; surfaced knowledge can answer the question before a request is even raised.
- No legal jargon - labels, guided steps and surfaced articles need to be plain-language for this audience.
- Engagement sits on a spectrum, from a low-friction default path to richer fields/collaboration, rather than two distinct experiences.
Sales-driven orgs
Requests from sales via Salesforce are overwhelmingly commercial/contract work, so template self-service (NDA/MSA etc.) and the ability to track approvals and signatures are the highest-volume paths.
Procurement-heavy orgs
Procurement-heavy orgs generate vendor-contract intake, a similar template and status fit.
What not to over-index on
Litigation/disputes work is rarely initiated by a business user through these channels - don't over-index intake or surfacing design on it.
Not the target audience for these integrations
These personas use LawVu meaningfully - but not through these integrations at a weekly+ cadence. Some are key champions for rollout and adoption, but they're not the daily users we're designing for.
Outside Counsel / LSPs
Very occasional LawVu users who default to their own private-practice tools. They're unlikely to expect value from - or even install - LawVu add-ins in their external email/chat tools. This may change in future as the collaboration capabilities of the product strengthen, but it's not a focus today.
Legal Operations
Their work is maintaining LawVu, reporting, adoption/training, and invoices - done inside LawVu, not via email/chat/CRM add-ins. They are a key stakeholder for rollout and adoption of the integrations, but not a daily user of them. Engage them as champions, not as a target persona.
Legal Leader / GC
Strategic/governance/ROI focus; little hands-on capture or intake. Any add-in use would be too infrequent to install or remember. Note too that to the extent they do pick up hands-on legal work, their needs align closely with the Legal Expert persona - so the Legal Expert card already describes them, a further reason to leave them on the periphery rather than treat them as a separate audience.