Who it is for, and what it does well
TaxDome
Accounting and tax firms that want a client portal, documents and billing together.
- A client portal. Clients upload documents and sign in one place.
- Built for the field. Workflows and templates for accounting and tax work.
- Everything in one system. CRM, documents and billing together.
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 TaxDome today.
Today
Check the vendor’s developer documentation for what it offers. Where there is nothing to call, a person can export a list and import the CSV into a Records type, and a custom module can wrap anything that has an endpoint.
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*, TaxDome included.
*Where the vendor provides an API.
Where Vyre fits.
What Vyre does around it.
Vyre does not replace TaxDome. These are the parts of the work Vyre does around it.
Documents and Signing
Your own Word templates filled from a record, with signing for people who have no account.
Agents
Agents prepare requests, reminders and summaries.
Tasks and Playbooks
Playbooks for each kind of engagement.
Keep TaxDome for its client portal and billing. Vyre does the preparation around it.
Why that helps.
What a team gets from it.
The portal stays where clients know it. The routine work behind it is done by agents.
- 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.
- Rules decide, not a modelA Flow follows stored steps and a person approves each version, so the same input takes the same path every run. A model is one step you place on purpose.
Side by side
| Question | TaxDome | Vyre |
|---|---|---|
| What it is | Practice management with a client portal for accounting and tax 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 | See the vendor’s developer documentation. | 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. | Documents and Signing, Agents and Tasks and Playbooks. |
| 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 TaxDome?
No. Keep TaxDome for its client portal and billing. Vyre does the preparation around it.
How does Vyre work with TaxDome?
Check the vendor’s developer documentation for what it offers. Where there is nothing to call, a person can export a list and import the CSV into a Records type, and a custom module can wrap anything that has an endpoint. Coming in 0.5.2: a packaged Integration, so the Connection and its operations arrive ready-made.