How to run client work in Hyperagent

Before client work goes live, decide who can change the agents, who pays for runs, and who maintains the setup. This guide outlines the standard operating architecture for AI agencies and automation consultancies deploying custom agent fleets for SMB clients.

---

Overview and operating model

Running client work as an AI automation agency requires clear boundaries around data, liability, compute costs, and permissions. You cannot mix Client A's context, customer records, and internal prompts with Client B's. At the same time, your agency team needs central oversight to monitor agent performance, tune prompts, and jump in when an agent needs human help.

Hyperagent supports this agency workflow out of the box through Workspaces, role-based governance, workspace-owned agents, and flexible billing models.

---

Workspace architecture and isolation

The golden rule: one workspace per client

Always create a dedicated Workspace for each client engagement (Workspaces).

A workspace isolates resources by default:

• Agents: Agents created in or transferred to this workspace belong to its team. (Note: A personal agent explicitly shared into the workspace remains runnable by members, but stays under its author's ownership).
• Skills and custom tools: Reusable procedures and scripts added to the workspace stay scoped to this client.
• Memories and knowledge: Workspace memories and agent-owned memories stay inside the workspace perimeter. (Note: An agent explicitly shared from Personal retains access to the personal memories configured by its author; keeping client agents workspace-owned prevents personal context crossover).
• Documents and artifacts: Research reports, plans, generated tables, and files remain within the client perimeter.
• Conversations and threads: All client runs, chat logs, and execution histories are contained in that workspace.

Navigating client workspaces

Agency operators navigate between client accounts using the workspace switcher at the top of the sidebar.

• Personal: Reserved for your own internal agency operations, private research, and skill prototyping.
• Client Workspaces: Each client has its own named workspace (for example: "[Client] Acme Logistics", "[Client] Apex Dental").
• Switching workspaces immediately re-scopes the sidebar, thread history, agent directory, and knowledge base.

---

Roles and access governance

Hyperagent provides three distinct workspace roles: Owner, Editor, and Member (Workspace roles). Use them to separate who administers the environment, who maintains prompts and tools, and who merely runs the agents.

Role allocation matrix

Invitation strategy

• When inviting client team members, use Email Invites rather than the reusable workspace link (Create a workspace and add people).
• Reusable workspace links default everyone to Editor.
• Sending individual email invites lets you explicitly select Member as the starting role, ensuring client staff can use the agents without permission to modify the underlying agent configurations.

---

Billing and financial architecture

A workspace in Hyperagent is an organizational boundary, not a billing unit. Adding a credit card to an administrator's account does not automatically pay for other members in that workspace.

Who pays for which run

Charges attach to the account that starts a run or saves a schedule:

The three operational rules

Setting up client billing correctly

1. Client Setup: The client creates their Hyperagent account and signs up for a paid plan.
2. Enable Shared Billing: The client Owner navigates to Settings → Billing, enables Shared Billing, and invites client team members who need to run agents.
3. Usage Limits: The client Owner sets monthly spend caps under Settings → Billing → Control Costs.
4. Agency Role: The client invites agency personnel into the workspace as Owners or Editors. Agency staff remain on their own agency billing profile.

---

Agent deployment and multi-agent architecture

Hyperagent supports two agent ownership types: Workspace-Owned and Shared Personal (Workspace agents).

Always choose workspace-owned agents for client engagements

When deploying agents for clients, always build or transfer them as Workspace-Owned:

• Collaborative Maintenance: All agency Editors and Owners can inspect and tune the agent's system prompt, tools, context files, and model settings together.
• Multi-Agent Delegation: Workspace-owned agents can delegate tasks to other workspace-owned agents (Agent delegation). Shared personal agents cannot receive delegated work.
• Configuration Persistence: The agent definition, prompt, model settings, and linked memories belong to the workspace. If an individual agency builder leaves your firm, the agent configuration remains intact in the workspace.
• Schedule Ownership Separation: Editing an agent's configuration does not automatically transfer or reassign existing schedules created by another user. Scheduled invocations remain owned by the user account that saved them, and unattended runs continue to bill to that schedule owner (Schedules). To transfer schedule ownership and billing to the client, the client Owner must explicitly save the schedule.

Moving an agent from personal R&D into a client workspace

If you prototype an agent in your Personal workspace first:

1. Open the agent's configuration and click Share....
2. Select Transfer to a workspace (do not select "Share with a workspace", which only grants run-only access).
3. Select the target client workspace.
4. Review the transfer screen to confirm that associated tools, skills, and memories move cleanly into the workspace.

Managing agency templates across multiple clients

1. Maintain an Agency Golden Template Base: Keep master agent configurations, prompt specifications, and toolsets in your internal agency workspace.
2. Export and Import Configurations: Export agent configuration JSON files from your master template. When spinning up a new client engagement, import the configuration into the client's workspace.
3. Packaging Standard Fleets: Package functional clusters (for example: Inbound Lead Triage, Meeting Prep, and Content Operations) as proven templates, then customize the final 20% (integrations and company tone) for each client.

---

Tooling, credentials and integrations

Client agents frequently require access to third-party services: Google Workspace, Slack, CRMs, data warehouses, and custom APIs. In Hyperagent, tool connections attach to user accounts, not abstract workspace identities.

1. Native integrations (OAuth and MCP)

• Integrations are authorized via Settings → Integrations inside the client workspace.
• Connection Identity: An OAuth integration (for example, Slack or Google Drive) is authorized under the specific user account that connected it.
• Unattended Run Safety: Scheduled runs and Live Mode heartbeat checks run unattended. Confirm in the schedule settings whether "Integration writes during this schedule's runs" should be enabled (read/write) or kept read-only (Schedules).
• Account Independence: If an agency engineer connects an integration using their personal or agency login, that connection depends on their continued account state. For client production workflows, have a client administrator authorize the integration so ongoing access remains under client control.

2. Workspace Skills (custom scripts and API credentials)

When deploying custom scripts through Workspace Skills (Workspace skills), choose the credential mode based on who owns the tool:

• "Use my credentials": The skill executes using the API credentials provided by the person who shared or configured the skill. Useful when the agency supplies shared utility tooling (such as a web-scraping API key or proxy). If the sharer's stored credentials are missing, the next run prompts for credentials.
• "Each member adds their own": Each user running the skill is prompted to enter their own credentials. Essential when an agent acts on behalf of individual client staff members (such as personal calendar access or individual CRM seats).

Best practice for client work

For client infrastructure, have a client Owner connect native integrations and enter production API keys. Keep agency-provided utility tools under "Use my credentials". This ensures client production workflows remain stable regardless of agency personnel changes.

---

Knowledge curation and quality governance

One of the primary ongoing responsibilities of an automation agency is ensuring that client agents continuously improve without hallucinating or drifting from business reality (Workspace memories).

The agent learning workflow

Hyperagent agents learn continuously from interaction, but agency governance is required to maintain accuracy:

1. Set Initial Save Destination: In the agent's Knowledge settings, configure the save destination to This agent's memories rather than the shared workspace library.
2. Enable Suggestions: Set learning behavior to Suggested for review rather than autonomous auto-save (Manage learning behavior).
3. The Three-Step Curation Sequence:
   • Step 1 (Review Suggestion): Agency operators open the suggestions queue in Learning to review proposed learnings surfaced from client runs.
   • Step 2 (Accept to Agent): Accept and save accurate, verified lessons. This persists the lesson as an agent-owned memory (This agent's memories), ensuring it assists that specific agent without prematurely altering shared context.
   • Step 3 (Promote to Workspace): When a saved memory represents broad company policy, brand guidelines, or shared operational rules, open the memory's actions menu on the Workspace memories page and select Promote to Workspace memories.

This three-step sequence guarantees that unvetted agent suggestions never enter the client's shared organizational truth without deliberate human approval.

---

Client delivery, monitoring and handoff lifecycle

Deploying client agents follows four operational phases from initial provisioning to long-term operations or eventual client handover.

Phase 1: Workspace and billing provisioning

• The client creates a dedicated Workspace (for example, "[Client] Acme Corp").
• The client Owner enables Shared Billing under Settings → Billing to cover client employees on a shared company card, and sets monthly spend caps under Settings → Billing → Control Costs.
• The client Owner invites the Agency Account Lead as an Owner via email.

Phase 2: Agent configuration and context definition

• Agency builders import agent configurations into the client workspace as Workspace-Owned agents (Workspace agents).
• Agency operators define multi-agent delegation paths between workspace agents (Agent delegation).
• Essential client standard operating procedures, schemas, and brand guidelines are pinned as Context Documents.
• Knowledge settings are configured: save destination set to This agent's memories and learning behavior set to Suggested for review (Workspace memories).

Phase 3: Integration binding and operational launch

• Client native integrations (Google Workspace, Slack, CRM) are connected under client credentials.
• Recurring automated schedules are saved under the client Owner account so unattended runs bill to the client (Schedules).
• Client staff are invited via email as Members to run agents without permission to edit prompts or tool configs (Workspace roles).
• The client team is onboarded to Inbox to handle approvals, answer agent clarification questions, and view finished outputs.
• Agency operators use Command Center to monitor fleet health: active operations, recent runs, and compute spend.

Phase 4: Long-term retainers vs. full client handover

Operating on a retainer

The agency remains in the workspace as an Owner or Editor to maintain agent prompts, add new skills, and review suggested memories weekly, while day-to-day runs bill to the client's Shared Billing organization.

Full handover audit (if the client takes over entirely)

If an agency offboards and removes its accounts, avoid assuming automatic continuity. Follow this transition checklist before stepping down:

1. Audit Production Dependencies: Identify agency-dependent connections, skill credentials, and schedules. Move production dependencies to client-controlled accounts and test them before removing agency access.
2. Native Integrations: Confirm that all third-party integrations (Slack, Google Drive, CRM) are authorized by an active client account.
3. Custom Skills & API Keys: For skills set to "Use my credentials", confirm that the stored credentials belong to a client administrator account so runs do not hit a "Credentials missing" state.
4. Scheduled Invocations: Confirm that every active schedule is owned and saved by a client Owner account.
5. Ownership Transfer: Promote a client administrator to Owner before agency accounts step down. A workspace must always have at least one active Owner (Create a workspace and add people).

---

Client kickoff checklist

The verified setup sequence for launching a new client engagement.