Using Neon Law Navigator

This workshop uses one local matter from start to finish: Cruller v. Prine. The matter code is sample-litigation, its portal application is the litigation sample project, and its local data is synthetic. Every attendee sees the same matter through the role assigned to their local account.

The fixture seeds two more matters beside it — sample-transactional and sample-estate — so the participation-scoped project list has something in it. The exercises stay on one matter on purpose; the other two are there to be seen from /app/projects, not worked.

Start →View all slides View as Markdown

Chapter 1

Why do this

Today, a matter often lives across a practice-management suite, email, a document store, and a signature tool. The client sees none of that coordination and calls for an update. The firm pays per seat for the glue between systems.

Navigator changes the work in four ways:

Same-day engagement: a services page leads to a questionnaire, a drafted document, lawyer review, and a send in one system.
A bill the firm owns: the firm runs the software with a repository per matter, rather than a per-seat licence.
Security by assignment: participation gates every door, refusals are logged, and a lawyer approves before anything leaves.
A client surface per matter: the matter's repository publishes its client portal.

You leave with a litigation matter walkthrough and a three-minute demo you can run at your firm. You can also identify which outcome your firm would buy first and what it would need to see.

Navigator does not yet provide a client-facing case dashboard or timeline.

18Verify the room