The system my firms run on.
Virtualaw OS is a working system, not a product for sale. This page describes what it is and what it does, because a firm considering an engagement deserves to see the reference.
One install holds the whole practice.
Matters, clients, documents, communications, and KPIs live in one place. A lead becomes a matter. The matter carries its documents, its signatures, and its messages. The numbers roll up to a dashboard the owner actually reads. Nothing is copied between tools, because the tools all read and write the same records.
The AI proposes. The attorney approves.
The agent works inside the practice under a risk framing that is architecture, not a setting.
Runs under playbooks
Routine actions run under playbooks an attorney approved. Every action is logged in an append-only record that cannot be edited after the fact.
Waits for the attorney
Anything novel or client-facing waits in an approval queue with the reasoning shown. Nothing goes out without a lawyer deciding it should.
Blocked outright
High stakes actions are blocked. It never moves money, because that capability does not exist. The agent runs on the firm’s own model key.
Each piece by name.
Each component is its own plugin, wired into the same spine.
- Fluent Forms: intake.
- FluentCRM: clients and pipeline.
- FluentBoards: matters.
- FluentBooking: scheduling.
- FlowMattic: the automation spine.
- Fetcher: document collection with a no-login client portal.
- Executer: document generation and e-signature.
- Dispatcher: two-way client SMS under playbooks.
- VirtuaVox: the voice line and AI attendant.
- Preparer: guided form-filling from government PDFs.
- Convener: client video meetings.
- Collecter: invoice collection, from sent to paid.
- Operater.
- The approvals queue: where the agent waits.
Built for my firms. Buildable for yours.
Every engagement is scoped individually, after a conversation about your practice. The build notes behind everything on this page live in the Nexus, the free community around the system.