Cross Suite Advisory — N M E D1 · What you receive — the technology
The delivery system is the Cross Suite Tools Plugin — a Claude Code plugin (current version v1.6.0) containing the entire firm: the Cross Suite 00 orchestrator and 104 specialist agents & Lab tools across 12 suites — 105 agents and their slash commands. Engagements produce client-facing deliverable documents.
2 · The two delivery models
A · SaaS-Hosted (managed by Cross Suite)
- Cross Suite Advisory runs the agents; the client needs no infrastructure.
- Model access runs on Cross Suite's own single Anthropic / Claude account — the firm does not buy a separate Claude license per client. The per-engagement usage is a small cost of goods, folded into the fee. The client needs no AI license of their own.
- The client connects only the data named in the brief; data is handled under the engagement agreement and never used to train models.
- Best for clients who want the result without standing up technology.
B · Client Self-Hosted (runs in client's environment)
- The agents run inside the client's own infrastructure for data-residency, regulatory, or vendor-isolation reasons.
- The client provides their own LLM API access (Anthropic / equivalent); Cross Suite does not resell model access here.
- Cross Suite supplies the reviewed agent specifications and quarterly updates.
- Best for regulated institutions whose data must not leave systems they control.
Both models: every client-facing deliverable passes through senior-practice review and the Principal's signature before release. Hosting changes where the agent runs — never whether a senior advisor signs.
3 · Files — which ones are included
| Component | Contents |
|---|---|
| The plugin file | cross-suite-tools.plugin (v1.6.0) — the single installable bundle. |
| Manifest | .claude-plugin/plugin.json — declares the plugin, version, and agent/command paths. |
| Agents | agents/ — 90 agent definitions (system prompt + guardrails per agent). |
| Commands | commands/ — 90 slash commands (/cs-tools:…). |
| Index | CLAUDE.md — the workspace index: every suite, agent, and when to invoke it. |
| GTM & delivery docs | gtm/ — install, runbook, qualification, approval workflow, 90-day deployment, SOW template. |
| Samples & templates | samples/, templates/ — reference deliverables and output templates. |
| Per-engagement output | The deliverable documents the agents produce for that engagement (.docx / .html / .pdf), saved in the client's engagement folder. |
4 · Instructions — how it's used
- Install the plugin in Claude Code (Section 5).
- Create a folder for the client/engagement and work from inside it so deliverables save there.
- Either type the slash command for the agent you need (e.g.
/cs-tools:uni-enrollment), or describe the decision to Cross Suite 00, which scopes it and routes to the right specialist(s). - Answer the agent's intake questions (scope, decision-maker, deadline, the data to read).
- The agent drafts the deliverable; Cross Suite 00 synthesizes multi-agent work into one cabinet brief.
- The draft returns to the Principal for senior review and signature, then is delivered.
5 · Load procedure (installation)
Prerequisite: Claude Code installed and signed in.
- Install the plugin — drag
cross-suite-tools.pluginonto Claude Code's plugin drop zone, or run/plugin install /path/to/cross-suite-tools.plugin. - Verify — run
/plugins list(you should seecross-suite-tools); type/cs-tools:to confirm the commands appear; run/agentsto confirm the agents load. - Set the working folder — create a per-client folder and run from inside it.
- Smoke test — run one command in test mode; it should produce the deliverable's structural shell. If it does, install is complete.
6 · What type of computer
| Model | Computer / hardware |
|---|---|
| SaaS-Hosted | No client hardware required. A standard computer with Claude Code (or browser access) is enough — Cross Suite runs the system. |
| Self-Hosted | A Linux or Windows host the client owns and administers · Python 3.10+ or Node 18+ runtime · ~5 GB free storage · outbound HTTPS to the chosen LLM API · a client-issued service account. Runs on a standard business workstation or server — no specialized hardware. |
7 · What type of license
| Item | License |
|---|---|
| The plugin / agents | Cross Suite Advisory intellectual property, licensed to the client for the engagement (internal-use). The firm's reviewed specifications; updated on a quarterly minimum cadence. |
| Model access (SaaS-Hosted) | Provided by Cross Suite — the client needs no separate AI license. |
| Model access (Self-Hosted) | The client provides their own LLM API license (Anthropic / Claude or equivalent); model relationship and usage costs sit with the client. |
8 · How long installation takes
| Plugin install | ~10 minutes (install + verify + smoke test). |
| Self-hosted setup | Add host provisioning + the client's LLM key + service account — typically the same day for a prepared environment. |
| Engagement onboarding | Data connection, calibration to the institution, and the first senior-reviewed deliverable run inside the engagement's first cycle (the full path to standing operation is covered by the 90-day deployment plan). |
Maintenance & currency: agent specifications are updated on at least a quarterly cadence. SaaS-hosted clients receive updates automatically; self-hosted clients receive the updated specs and apply them, so the agent always reflects the firm's current reviewed standard.
Note: technical facts above are drawn from the plugin's install guide and each agent's Client-Self-Hosted, SaaS-Hosted, and Technical-Requirements documents. Pricing is a separate working document and is not final.