VirtualawOS
What’s inside

Everything a firm runs on, in one place you own.

Core and the supervised agent are the base. Four modules add the rest of a practice. They are separate plugins, but they all read from and write to the same matters, so nothing is copied between tools.

yourfirm.com/wp-admin › Virtualaw OS
Okafor v. Delmar Freight
MTR-2291 · active · opened 12 Feb
Discovery response
document · drafted, awaiting approval
Review
Deadline: production due
calendaring · in 4 days, court days
Due soon
Client intake form
intake · converted to matter
Done
00 · Always on

Core and the supervised agent

The matter is the center of everything. Around it, an approval queue and an append-only record. The agent proposes work and waits.

  • Matters, tasks, and a full event trail
  • Risk tiers: routine runs, novel waits, high-stakes is blocked outright
  • Bring your own model key; the agent never touches our servers
  • Every agent action logged, nothing editable after the fact
Approval queue
Draft discovery responseauto
Send novel client emailapprove
Close matterblocked
Form to matter
Web form submitted0:00
Contact synced to CRM0:01
Conflict checkclear
Matter proposedyou approve
01 · Module

Intake

A lead fills out a form. It becomes a contact, runs a conflict check, and lands as a proposed matter, without anyone copying fields between systems.

  • Fluent Forms in, a matter out
  • Contacts synced to FluentCRM
  • Conflict check against your existing adverse parties
  • New matters always wait for your sign-off
02 · Module

Documents

The agent drafts from the matter, you approve, and it generates the document and sends it for signature. Every draft traces back to where it came from.

  • Draft, review, generate, send for e-signature
  • The document lifecycle, visible on the matter
  • Sending is always an approve step, never automatic
  • No document URL stored that could leak or expire
Document lifecycle
Draftedby the agent
Pending approvalyou
Approvedgenerated
Sent for signaturetracked
Deadline rules
Filing acceptedtrigger
+30 court daysresponse due
-7 calendar daysreminder
Weekends, holidayscounted
03 · Module

Calendaring

Set a deadline template once for a matter type. When the trigger event happens, the deadlines and reminders populate themselves, counting court, business, or calendar days correctly.

  • Court, business, and calendar-day counting
  • Templates you approve; only active ones populate
  • Off-template changes by the agent wait for you
  • Deadlines confirmed by a human, on the record
04 · Module

Communications

Message clients on their channel, under playbooks you have approved. Routine updates go out on their own; anything novel asks first.

  • Text and message clients from the matter
  • Playbooks gate what the agent can send unattended
  • Inbound replies land back on the matter timeline
  • Every message on the record, both directions
Message timeline
Filing accepted updatesent, playbook
Client replyinbound
Novel answerwaits for you
How they connect

One matter, start to finish.

The modules are separate plugins, but there is one spine: the matter. A lead becomes a matter, the matter carries its deadlines, documents, and messages, and the agent works across all of it under your approval.

01

Intake

A form becomes a matter, conflict-checked.

02

Matter

The center. Tasks, events, the agent.

03

Calendar

Deadlines populate from the rules.

04

Documents

Drafted, approved, sent to sign.

05

Messages

The client kept in the loop.

See it running on your matters.

Start the full suite free for two weeks. Every module unlocked, your data on your site.