- contactlink
- practice areachoice
- sourcechoice
- summaryrich text
- stageNew to Converted
Links to a Contact. Board by stage.
For law firms.
A law firm, run as an AI-native firm.
One client, one matter, from the first inquiry to the billing hand-off. Alder Row Legal is an invented two-practice firm, personal injury and estate planning. Every step below uses a piece of Vyre that exists today, and the people keep every decision that matters.
The client journey.
Eight steps, one record that carries them.
Alder Row Legal follows one client through the whole firm. Each step names the Vyre pieces behind it. Where a step sends something out, a person approves the exact words first.
- 01Inquiry comes in
A web form, a call to a Flow’s path or a new email in a watched mailbox starts the intake Flow. It finds or creates the Contact and creates a Lead.
- 02Screening and conflict check
The intake agent fills in practice area and summary, then searches existing clients and parties for the names in the inquiry. A hit goes to the responsible attorney under Needs you. No hit moves the Lead on.
- 03Consultation
A Lead entering “Meeting booked” creates an Appointment and drafts the confirmation. The email waits at the Gate until the attorney approves the words.
- 04Engagement letter signed
A Lead entering “Qualified” fills the engagement letter from the client record and sends it for signature. The client signs without an account and the signed copy files on the record.
- 05Matter opens from a Playbook
When the signature event arrives, a Flow reads the practice area, branches and starts the matching Playbook. The matter appears with its stages, its tasks and who does each one.
- 06Deadlines from a trigger date
The matter carries dates such as the accident date or the hearing date. A Flow waits until a date field plus an offset, then assigns the task to the attorney with a paralegal following. The reviewer agent checks each date against the rule the firm wrote down.
- 07Documents and client updates
The drafting agent completes missing fields and asks Documents to fill the firm’s own Word template. A stage change drafts the client update, and the attorney approves it before it leaves.
- 08Closing and billing hand-off
A matter entering “Closed” asks the responsible attorney, then assigns the billing task with the matter’s fields filled in. A Connection call can post the same fields to the billing tool.
Alder Row Legal is invented. Names, dates and amounts on this page are sample data.
Records.
The things Alder Row Legal tracks, as records you shape.
Each type has fields in named groups, links to other types, views and sealed values. The law-firm Kit starts you with lead, appointment and client types and an estate-plan Playbook. Everything else is a type you add in Customize.
- contactlink
- practice areachoice
- sincedate
- stageOnboarding, Active, Closed
Has many matters.
- nametext
- clientlink
- ownerperson
- practice areachoice
- accident datedate
- hearing datedate
Tokens such as {matter.client.email} reach across links.
- nametext
- rolechoice
- matterlink
- ID numbersealed ••••••
Searched by the conflict check. The ID number is sealed.
Playbooks.
Each kind of work is its own track.
A Playbook lists stages, the tasks in each stage and who does each task: a person, a role or an agent. A Flow reads the field that names the track and starts the matching Playbook. The tracks run side by side over the same records.
- IntakeOpen file, send records requestsParalegalConfirm no conflictReviewer agent
- TreatmentCollect medical recordsParalegalMonthly client check-in draftUpdates agent
- DemandDraft demand letterDrafting agentApprove demandAttorney
- ResolutionTrack offersAttorneyDraft settlement statementDrafting agent
- ClosingClose file and hand off billingBilling
- QuestionnaireSend questionnaireIntake agentReview answersParalegal
- DraftingFill will and trust templatesDrafting agentCheck against questionnaireReviewer agent
- Signing meetingSchedule signingParalegalAttorney reviewAttorney
- FundingFunding checklistParalegal
- ClosedClose and archiveBilling
Flows.
Work that runs the same way every time.
A Flow is written once and approved by a person. A trigger starts it, steps do the work, and it stops wherever a person has to say yes. Each run has its own page with a step timeline. In the chains below, outlined is the trigger, tinted is an agent, dashed waits for a person and dark is held at the Gate.
New inquiry
A form is submittedFind or create the contactCreate a LeadIntake agent screens itAsk the attorney if a name matchesConfirmation email held
A person approved this Flow once. Each run has its own page with a step timeline.
Engagement
A Lead enters QualifiedFill the engagement letterSend for signatureWait for the signatureStart the matter’s PlaybookAssign the first task
The signature event, documents.signed, starts the next step. A decline starts a different path.
Hearing watch
A hearing date is setWait until 14 days beforeAssign a task to the attorneyReviewer checks the dateReminder to the client held
The offset is the firm’s own number. The Flow only does the arithmetic.
Agents with roles.
The drafting is done. The decisions are yours.
An agent has a job in one sentence, an AGENTS.md that says how to do it and a list of projects it works in. Anyone in the Space can share it with a person or a role as use-only or full. A reviewer is an agent whose instructions say what to check, with a standing duty on an event. It marks a task stuck with a plain reason when it cannot decide, and that task waits under Needs you.
Reads each new inquiry, fills the Lead, and searches clients and parties for matching names.
- Works in
- The intake project
- May use it
- Everyone in the Space as Can use. Only the managing partner can edit it.
- Does not
- Send anything. It asks, and a conflict hit goes to a person.
Picks the template for the matter, completes missing record fields and asks Documents to fill the firm’s Word file.
- Works in
- Matters it is assigned to
- May use it
- Attorneys and paralegals.
- Does not
- Retype a firm document. A wrong value is fixed in the record or the template.
Checks a draft or a computed date against the rules written in its AGENTS.md before the attorney sees it.
- Works in
- Every matter project
- May use it
- Attorneys.
- Does not
- Approve. It marks a task stuck with a plain reason when it cannot decide.
Drafts the client update when a matter changes stage, in the firm’s tone.
- Works in
- Active matters
- May use it
- Paralegals.
- Does not
- Email a client. The draft waits at the Gate.
NEEDS YOU
One place for everything that waits.
Approvals, questions and stuck tasks land in one list, on the Mac, the web app and the phone. An agent can ask and cannot approve. The person sees the exact words, approves or edits, and only then does the email, the signature request or the page go out.
Conflict checkPossible match: the party “Holloway Freight” is a current client on another matter.
ReviewClearHeld emailEngagement letter cover note to Daniel Reyes. 84 words.
ApproveEditStuck taskIntake agent: the form has no practice area.
OpenPaperwork, secrets and pages.
Your own documents, your own logins, your own page.
01
Documents and Signing
Engagement letters, fee agreements and client letters are the firm’s own Word templates, filled from the matter and the records linked to it. The signed copy files on the matter and starts the next Flow.
02
Vault
The e-filing login, the bar portal and the court calendar sit in the Vault. An agent uses a credential without seeing it, and each attorney has a private vault the firm cannot read.
03
Sites
An agent builds the firm’s consultation page and intake form from its records and brand, previews it at a private address and puts it live on one yes. Every version stays in the history.
Connect your stack.
Vyre can be extended by integrating your Zoho, QuickBooks, RingCentral and the rest of your software stack*
Alder Row Legal keeps its tools. Vyre reaches them through the same checks as everything else: the key lives in the Vault, every call is marked read, draft, change, send, spend or delete, and anything that leaves the Space waits at the Gate.
- ClioComing in 0.5.2A planned packaged Integration. Today, a Connection and a Flow step, or a custom module.
- LawmaticsComing in 0.5.2A planned packaged Integration. Today, a Connection and a Flow step.
- Practice toolsConnectionDocument, calendar and e-filing tools with an API connect the same way.
- ZohoConnectionA Connection and a Flow step today. An Integration is the Next step.
- RingCentralConnectionA Connection and a Flow step today. An Integration is the Next step.
- Google WorkspaceTodayMail and calendar connect per member. Drive folders link as Files.
- Microsoft 365TodayMail, calendar and files connect per member.
- DropboxTodayFolders link as Files, read through each person’s own account.
- DocuSignConnectionVyre signs documents itself. A Connection reaches DocuSign if you keep using it.
*where the vendor provides an API
Today
A Connection plus a Flow step. A person adds a Connection: a declared host, how the key is sent and a list of operations, each marked by what it does. A Flow’s service step calls an operation, and a send waits at the Gate.
Or a custom module. A module is a folder with a module.json and an entry file. It registers tools, emits events and declares Flow steps under the same checks as the built-in modules. An agent can write one on your own server.
Coming in 0.5.2
Integrations, packaged. An Integration wraps an application’s API and ships its own Flow steps, triggers, Connection and agent tools. You install, verify, configure and remove it from one place. An agent can make one from an API.
Clio, Lawmatics, GoHighLevel and DecisionVault are the first planned. This is direction, not a date.
Your turn.
Ask your agent to map your business.
Paste this into Claude, Codex or any agent that can read the web. It interviews you, then draws your firm as a Vyre Space on paper. Nothing changes until you say so. The full prompt lives on the home page.
Copy this into Claude, Codex or any agent
Read https://vyre.run/llms-full.txt and https://vyre.run/docs/for-agents/MAP-YOUR-BUSINESS.md. I run a law firm. We use Clio, Lawmatics, Practice tools, Zoho, RingCentral. Interview me about my people, what we track, the kinds of work we do, our paperwork and our software. Then show my business as a Vyre Space: members and roles, record types, a Playbook for each kind of work, Flows, agents with roles, documents and signing, a client page, the apps to connect, and what waits for my yes. Mark what Vyre does today and what is Next. Design on paper and change nothing until I say so.
Connects to
- ArchitectureThe layers, how a call is checked and how the Gate holds an outward act.
- FlowsTriggers, steps, waits, failure paths and how a run is replayed.
- Records and PlaybooksTypes, fields, stage sets, sealed values and views.
- Documents and signingFill your Word templates from a record and send them for signature.
- The GateWhy nothing leaves the Space until a person approves the exact words.
- DirectionWhat comes next, including Integrations in 0.5.2.
- For accounting firmsThe same journey for another kind of business.
- For consulting firmsThe same journey for another kind of business.
Give this to your AI agent
Ask your AI how your business would run on Vyre.
Read https://vyre.run/agenthome.md and follow it to show me how my business would run on Vyre, the agentic command center for AI-native teams. Ask me what you need.
Tailor it to your business →
Paste it into ChatGPT, Claude or any agent that can read links. It reads vyre.run/agenthome.md, asks you a few questions and maps your team, records and Flows.