LegalPresence

Product

Feature map · scorecard · build plan

LegalPresence is a litigation command and counsel-approval workbench: CRM as source of truth, dependency-aware clock, fail-loud citation and role gates, sealed package when clear.

Request access Title WorkBench interview For firms

Capability map

Twelve partner needs

#Partner needProduct capabilityLP statusBuild
1What is due and who owns it?Deadlines + owners + alerts + dependencies● StrongNext 3 · Assign owner · UNOWNED flag
2Don’t miss the hearing / filingCritical path / calendar integrity● Strongpath-ics export · DAG · critical path
3Find the exhibit / dep page nowMatter file + search + evidence links● StrongMatter search · fact pins · evidence rail
4Draft fasterResearch + drafting AI◐ PartialModule gen · Workbench · Word loop
5Don’t invent law or misstate the recordCite check + fact pin + good-law● StrongGood-law stamp · pins
6I work in WordWord add-in or one-click clean DOCX● StrongDOCX export/import · Word bridge page · Office.js later
7I need to e-file this packageFiling-clean export / court pack● StrongPackage recipe · Gate · hard seal ZIP
8Who approved this?Role sign-off / audit trail● StrongLedger stamp on clear (LP:APPROVAL)
9What’s the theory and is it ready?Strategy / elements / gaps● StrongHome one-pager
10Keep client texts and docs in the caseComms + docs on the matter◐ PartialPull mailbox UI · SecureVault IMAP (config required)
11Secure and privilegedAccess control + no silent data leak◐ PartialClean-export default
12ROI / don’t drown me in UISimple next actions, not 15 accordions● StrongNext 3 · Matter gate · Advanced collapsed

Shipped engines

What is live in the product

Clock

Procedural clock

  • Critical-path hero + dependency DAG
  • HARD_BLOCKS / SOFT / SHARE edges
  • Task board status (list view of the same clock)
  • Next 3 actions + Assign owner
Gate

Counsel approval

  • R6 citation gate + Citations Next/Prev + inspect
  • SIGNOFF + structured [[LP:NOTE]] reveal codes
  • Filing clean · dual view Work product | Filing
  • Matter Gate · approval ledger · good-law stamp
Strategy

Readiness

  • Theory readiness (elements · composite)
  • Motion viability · strategy radar
  • Top blocking gaps (severity / deadline)
  • Evidence ↔ assertion heatmap
  • Discover: precedent rank + party patterns (Advanced)
Package

Delivery

  • Court pack plan · gates · sealed ZIP
  • CRM SoT · email delivery only
  • Export PDF from Workbench
  • Filing-clean DOCX · Package recipe · Word bridge

Product UI

Shipped surfaces (live captures)

Command, Workbench, Discover, Word bridge — from the running Legal Studio, not design comps.

Command home with critical path and Next 3
Command — Clock + Next 3 + Matter gate on the partner home.
Workbench with Gate and Package recipe
Workbench — Citations, Gate, Package recipe, DOCX, Word bridge.
Discover ranked precedents and plaintiff profiles
Discover — On-matter precedent rank + plaintiff patterns. Advanced research seat.
Word bridge instructions page
Word bridge — Supported Word / Google Docs loop until Office.js ships.

Advanced · research seat

Discover is useful — not under Title WorkBench

Two different things share similar words. Confusing them mis-sells both.

Public · Title WorkBench interview

legalpresence.com/research

Partner discovery interview for product priorities (Clock / Gate / Word / pain). Answers email research. No case data. No AI research run.

Open interview →

Studio · Discover

/studio/discover (after access)

Precedent research dashboard: rank on-point cases, profile serial litigants, optional workspace spin-up for a docket. Fail-loud: web hits are UNVERIFIED until counsel citates. Not the front door — Advanced behind Command.

Verdict: Discover is useful and shipped. Keep it in the product map as an advanced research engine (feeds Draft + strategy). Do not put it under the marketing Title WorkBench page — that page is the partner interview (what you need from a workbench), not legal research AI. In-product Discover is separate: ranked cases, party patterns, verify-before-file.

UX redesign

Matter command home (target IA)

Information architecture change — not a cosmetic rebrand. Partner spine first; Advanced last.

MATTER · as-of · [Search evidence…] ──────────────────────────────────── 1 NEXT 3 ACTIONS 2 GATE (FILE / NO-FILE) 3 PROCEDURAL CLOCK (path + expand DAG) 4 Theory top3 · Gaps · Drafts · Package 5 Console (collapsed for partners) 6 Advanced ▾ (heatmap, radar, team…)

Build waves

How we close the gaps

Wave 0–1 · Trust · shipped

Home spine + pre-file

  • Next 3 · Theory/Gaps on home · Advanced
  • Matter Gate · DOCX export/import
  • Approval ledger · hard-block seal
Wave 2–4 · Seat · shipped

File + Word + package

  • Matter search · fact pins · evidence rail
  • Good-law stamp · Package recipe · path-ICS
  • Native Office.js task pane (Word bridge stands in)

Non-goals: Filevine billing/SMS clone · Westlaw corpus · auto-approve AI · more peer accordions.

Position

Complement, don’t clone

vs CoCounsel / Harvey

They accelerate drafts and research. We control what can become a filing and keep the clock honest.

vs Clearbrief

They finish the brief in Word. We own matter gates and package — export clean DOCX into Word.

vs Filevine

They run case volume ops. We run litigation readiness: path, theories, cites, seal.

Next step

Pilot one matter or shape the roadmap

Partners: request access. Product leaders: complete the Title WorkBench interview — answers go to research.

Request access Title WorkBench interview
Enlarged screenshot