- nametext
- entity typechoice
- year enddate
- tax IDsealed ••••••
- bank accountsealed ••••••
Contacts link to the organization.
For accounting firms.
An accounting firm, run as an AI-native firm.
A new client, then a year of work on a calendar. Brightwater Accounting is an invented firm with three tracks: monthly bookkeeping, individual returns and business returns. Each track is its own Playbook with its own Flows over the same client records.
The client journey.
Eight steps, one record that carries them.
Brightwater Accounting 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 and scoping
A form or a call starts a Flow that creates the prospect and a scoping task. The intake agent drafts the questions: entity type, software, volume, year-end.
- 02Proposal and engagement letter
The partner approves the scope. Documents fills the engagement letter from the client record and sends it for signature. The client signs without an account.
- 03Client onboarding
The signature starts onboarding. A Flow creates the engagement records, assigns the setup tasks and sends the first document request. Tax IDs and bank numbers go in sealed fields.
- 04Document collection
Each request is a record with a due date. A schedule inside business hours finds the overdue ones and drafts a reminder. The reminder waits at the Gate, and the reply starts the next step.
- 05Monthly close Playbook
On the first business day a Flow starts the close Playbook for every active monthly client: collect, reconcile, review, report, deliver. Each task has a doer and a checker.
- 06Tax season tracks
Individual and business returns each have their own Playbook and stage set. A field on the engagement names the track, and a Flow starts the right Playbook.
- 07Review and delivery
The reviewer agent compares the working papers against the firm’s checklist. The partner approves under Needs you, and the delivery email goes out only after a yes.
- 08Billing and renewal
Closed work assigns the billing task with fees filled in. A yearly Flow drafts the renewal letter, sends it for signature and moves the engagement to the new year.
Brightwater Accounting is invented. Names, dates and amounts on this page are sample data.
Records.
The things Brightwater Accounting tracks, as records you shape.
Each type has fields in named groups, links to other types, views and sealed values. These are types you define in Customize, or that an agent defines for you over MCP. Fields sit in named groups, and fields marked sealed show an agent a placeholder, never the value.
- clientlink
- servicechoice
- periodtext
- ownerperson
- duedate
- stageby track
The service field picks the track and the stage set.
- engagementlink
- itemtext
- duedate
- receiveddate
- stageOpen, Received
Overdue ones feed the reminder Flow.
- engagementlink
- kindchoice
- filefile
- approved byperson
Links to the file in the Space’s Files.
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.
- CollectCheck all requests receivedChaser agentChase missing itemsChaser agent
- ReconcileReconcile accountsBookkeeperFlag unusual itemsPreparer agent
- ReviewReview the closeReviewer agentApproveManager
- ReportFill the management reportDrafting agent
- DeliverSend the reportManager
- OrganizerSend the organizerIntake agent
- Documents inCheck the document listChaser agentChase missing itemsChaser agent
- PreparePrepare the returnPreparer
- ReviewReview against the checklistReviewer agentSign offPartner
- Client approvalSend for signatureManager
- KickoffConfirm entity detailsManager
- Documents inCollect year-end filesChaser agent
- PreparePrepare the returnPreparer
- ReviewReviewer passReviewer agentPartner reviewPartner
- FiledRecord the filing dateManager
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.
Close kickoff
First business day, 8:00Find active monthly clientsFor each: start the close PlaybookAssign the first task
A schedule reads the Space’s time zone and can skip holidays.
Document chase
Every day in business hoursFind overdue requestsChaser agent drafts the reminderReminder email heldWait for the reply or 3 days
The Flow carries its own limits on how many it sends. A hit limit stops for a person.
Engagement signed
documents.signedMove the client to ActiveCreate the engagementStart the track’s PlaybookAssign setup tasks
The same pattern renews each year.
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.
Turns a new inquiry into scoping questions and a draft proposal outline.
- Works in
- The prospects project
- May use it
- Partners and managers.
- Does not
- Send the proposal. A partner approves it.
Reads open document requests and drafts the reminder in the firm’s tone.
- Works in
- Active engagements
- May use it
- Managers.
- Does not
- Send a reminder by itself. Each one waits at the Gate.
Flags unusual items and fills the working-paper summary from the records.
- Works in
- Engagements assigned to it
- May use it
- Bookkeepers and preparers.
- Does not
- See a tax ID or bank number. Sealed fields show a placeholder.
Checks a close or a return against the firm’s checklist and marks what it could not verify.
- Works in
- Every engagement project
- May use it
- Managers and partners.
- Does not
- Approve. A partner does that.
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.
Held emailReminder to Marlow Dental: 3 items still missing for March. 61 words.
ApproveEditReviewMarch close for Marlow Dental is ready for the partner.
OpenStuck taskChaser agent: two clients share one contact email.
OpenPaperwork, secrets and pages.
Your own documents, your own logins, your own page.
01
Documents and Signing
Engagement letters, management reports and authorization forms are the firm’s own templates, filled from the engagement and the client. Signers need no account, and the signed copy files on the engagement.
02
Vault
Software logins, portal access and shared mailbox passwords sit in the Vault, shared as Can use. The chaser and reviewer agents use a login without seeing it.
03
Sites
An agent builds a page for each service that says what the firm needs each month and how to send it, plus the intake form. It goes live on one yes.
Connect your stack.
Vyre can be extended by integrating your Zoho, QuickBooks, RingCentral and the rest of your software stack*
Brightwater Accounting 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.
- QuickBooksConnectionA Connection and a Flow step today. An Integration is the Next step.
- XeroConnectionA Connection and a Flow step today. An Integration is the Next step.
- KarbonConnectionA Connection and a Flow step today. An Integration is the Next step.
- 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 an accounting firm. We use QuickBooks, Xero, Karbon, 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 law 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.