- nametext
- industrychoice
- ownerperson
- billing contactlink
Contacts link to the organization.
For consulting firms.
Northfield Advisory is an invented six-person firm that sells diagnostics, programs and retainers. The work is judgment, so the agents carry the research, drafts and status writing, and the partners keep the calls.
The client journey.
Northfield Advisory 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.
A form, an email to a shared mailbox or a referral entered by hand starts a Flow. It finds or creates the organization and the contact, and creates an Opportunity.
The research agent reads the company’s public material and drafts a one-page brief. The partner reads it before the scoping call.
The proposal agent assembles the draft from the firm’s past work and price list. The reviewer checks scope and price against the rules in its AGENTS.md. The partner edits and approves.
Documents fills the statement of work from the Opportunity and sends it for signature. The signed copy files on the engagement.
The signature starts the Playbook for the kind of work: diagnostic, program or retainer. Phases, tasks, owners and due offsets arrive together.
Every Friday a schedule asks the status agent to read the week’s tasks and decisions for each engagement and draft the client update. The partner approves each one.
A new request is a record. The Flow asks the partner, updates scope and fee on a yes, and drafts the change note for the client.
The last phase fills the report template, sends it for the client’s sign-off and opens the renewal Opportunity ninety days later.
Northfield Advisory is invented. Names, dates and amounts on this page are sample data.
Records.
Each type has fields in named groups, links to other types, views and sealed values. Fields sit in named groups, and views are boards, calendars and dashboards. The partner’s dashboard of open Opportunities and live engagements is a saved view.
Contacts link to the organization.
Board by stage. A won Opportunity starts an engagement.
The offer field picks the Playbook.
A yes updates the engagement.
Playbooks.
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.
Flows.
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.
Opportunity won
The Flow reads the offer field and branches. In 0.5 the caller names the Playbook, so the Flow does.
Friday status
One run per engagement, each with its own page.
Change request
The Flow stops at the question until a person answers.
Agents with roles.
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 public material on a company and writes a one-page brief with sources.
Assembles a proposal from past work and the price list.
Checks scope, price and claims against the firm’s rules before a partner sees a draft.
Reads the week’s tasks and decisions and drafts the client update.
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.
Paperwork, secrets and pages.
Statements of work, change notes and final reports are the firm’s own Word templates, filled from the engagement. The client signs without an account.
Client data-room logins and survey tools sit in the Vault. Agents use them for one job and never see them. Each consultant has a private vault.
An agent builds a page for each offer and the inquiry form from the firm’s records and brand. It previews at a private address and goes live on one yes.
Connect your stack.
Northfield Advisory 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.
*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.
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.
Read https://vyre.run/llms-full.txt and https://vyre.run/docs/for-agents/MAP-YOUR-BUSINESS.md. I run a consulting firm. We use Zoho, QuickBooks, Xero, RingCentral, Google Workspace. 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.
Give this to your AI agent
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.
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.