- nametext
- account leadperson
- term enddate
- retainermoney
Contacts link to the organization.
Vyre / For / Marketing and creative agencies
For marketing and creative agencies.
Copperline Studio is an invented eight-person agency with three offers: a social retainer, paid media and website builds. Work moves in rounds, so the Flows count rounds, the agents draft and check, and the client’s yes is a signed record.
The client journey.
Copperline Studio 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 or an email starts the Flow. It creates the Contact and a Prospect, and the intake agent drafts the discovery questions.
A call’s notes land on the Prospect. The brief agent turns them into a written brief with goals, audience and budget. The account lead edits it.
The proposal is filled from the brief and the price list, then sent for signature. The client signs without an account and the signed copy files on the client record.
The signature creates the client record and the campaign. The access checklist runs: ad accounts, analytics, brand files. Logins go in the Vault, and agents use them without seeing them.
The offer picks the Playbook: social retainer, paid media or website build. Each has its stages, tasks and doers, side by side over the same client records.
Each deliverable is a record with a round number. The reviewer agent checks it against the brief and brand rules, then it goes to the account lead. Round three asks a partner.
The approved asset is sent to the client for sign-off. A yes moves the record to Approved and starts production. Publishing a page or a post waits at the Gate.
Each month the report agent assembles the numbers into the report template. The account lead approves, and a renewal Flow starts sixty days before the term ends.
Copperline Studio 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. A board by stage for deliverables and a calendar by due date are saved views. Money fields total across a client’s campaigns.
Contacts link to the organization.
The offer picks the Playbook and the stage set.
A Flow counts the rounds.
Points at a Vault item, never holds the login.
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.
Proposal signed
Each offer is its own track with its own Playbook.
Review round
Round three, by the firm’s rule, asks a partner instead.
Monthly report
The numbers come from the records or a Connection. The agent does not invent any.
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.
Drafts discovery questions and files the call notes on the Prospect.
Drafts plans, copy and variations from the brief and brand rules.
Checks each deliverable against the brief and the brand rules and names what it checked.
Builds a landing page or a site, previews it at a private address and asks to go live.
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.
Proposals, statements of work and approval sheets are the agency’s own templates, filled from the client and the campaign. The client signs without an account.
Ad accounts, social logins and hosting sit in the Vault, shared as Can use. The content and site agents work with them and never see the values.
Landing pages and whole sites for clients are built by the Site agent from the client’s records and brand, previewed privately and put live on one yes. Every version stays in the history.
Connect your stack.
Copperline Studio 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 marketing agency. We use Zoho, RingCentral, Google Workspace, Microsoft 365, Dropbox. 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.