Who it is for, and what it does well
Lawmatics
Law firms that want intake, CRM and follow-up automation.
- Intake and follow-up. Forms, pipelines and automated outreach for prospects.
- Built for law firms. Terms and stages match the field.
- Automation. Workflows from prospect events.
Vyre
The agentic command center for AI-native teams: people and agents work in one Space on a server you own.
Industry-neutral. You shape the records, and Flows, Playbooks and a Gate run the work.
Works with Vyre.
How Vyre connects to Lawmatics today.
Today
Lawmatics publishes an API. A person adds a Connection in the Vault that declares the host, how the key is sent and which operations read, draft, change, send, spend or delete. A Flow then calls the service from a web step, or a custom module wraps it.
Where the vendor publishes an MCP server, a person can add it for agents to use.
Coming in 0.5.2
A packaged Integration, so the Connection and its operations arrive ready-made.
Vyre can be extended by integrating your Zoho, QuickBooks, RingCentral and the rest of your software stack*, Lawmatics included.
*Where the vendor provides an API.
Where Vyre replaces it.
What Vyre does natively.
Vyre does these parts of the job natively, so a team can drop a seat or a step. Lawmatics stays the better fit for what it was built for.
Records
Prospects and matters as records, with boards by stage.
Agents
An agent reads a new enquiry and drafts the reply for approval.
Flows
Flows react to a new record or stage.
Keep Lawmatics for its intake forms and campaigns if the firm relies on them. Vyre can read from it and prepare the work.
Why that helps.
What a team gets from it.
The intake form stays. Vyre does the reading, drafting and checking that follow it.
- Agents do the workAn agent takes the task and finishes it, hands it on or marks it stuck with a reason. A person is not moving data between tools by hand.
- Every outward action approvedAn email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes.
- One place for people and agentsPeople and agents are members of the same Space. They share the records, tasks, files and chat, so nobody carries data from one tool to the next.
Side by side
| Question | Lawmatics | Vyre |
|---|---|---|
| What it is | Client intake and marketing automation for law firms. | A shared working layer for people and agents: records, tasks, Flows, documents, sites and a Gate. |
| Where it runs | Hosted by the vendor. | On a server you own. |
| Connecting to the other | Lawmatics publishes an API. | A Connection in the Vault and a Flow web step or custom module. Coming in 0.5.2: a packaged Integration. |
| Parts of the job in Vyre | Set by the product. | Records, Agents and Flows. |
| Outward actions | Set by how the product is configured. | Held at the Gate until a person approves the exact words. |
The left column comes from the product’s public documentation or describes the kind of product. Where it differs, the vendor’s own documentation is the one to trust.
Questions people ask
Does Vyre replace Lawmatics?
For some parts of the job, yes. Keep Lawmatics for its intake forms and campaigns if the firm relies on them. Vyre can read from it and prepare the work.
How does Vyre work with Lawmatics?
Lawmatics publishes an API. In Vyre, a person adds a Connection in the Vault that declares the host, how the key is sent and which operations read, draft, change, send, spend or delete. A Flow then calls the service from a web step, or a custom module wraps it. Coming in 0.5.2: a packaged Integration, so the Connection and its operations arrive ready-made. Integrations work where the vendor provides an API.