---
title: Move a pitch into ongoing monitoring
description: Preserve pitch observations while reviewing client settings and
  capacity before starting ongoing monitoring.
canonical_url: https://orchestor.io/docs/en/cli/workflows/agency-pitch-to-client
markdown_url: https://orchestor.io/docs/en/cli/workflows/agency-pitch-to-client.md
contentType: how-to
---

# Move a pitch into ongoing monitoring

## When to use this workflow

> “Keep the pitch observations and move this client into ongoing monitoring.”

## Before fetching

Use the pitch workspace created in [Start monitoring a client brand](https://orchestor.io/docs/en/cli/workflows/agency-client-onboarding.md). Convert that same workspace to a client workspace; do not create a destination workspace.

Preserve pitch observations while reviewing client settings and capacity before starting ongoing monitoring.

## Prerequisites

Use an authenticated account with permission to manage client workspaces. The conversion cannot be reversed, so confirm that the target is a pitch workspace before the write.

Use npm CLI `0.6.0` (the `beta` tag) or later for this workflow. Follow the installation commands in [Agency and client management](https://orchestor.io/docs/en/cli/workflows.md).

## Quick reference

Replace placeholders with IDs returned by earlier operations. Use different idempotency keys for the dry-run and the committed request.

```bash
orc workspaces list --json
orc workspaces get YOUR_PITCH_WORKSPACE_ID --json
orc workspaces quotas get --workspace YOUR_PITCH_WORKSPACE_ID --json
orc prompts list --workspace YOUR_PITCH_WORKSPACE_ID --json
orc workspaces update YOUR_PITCH_WORKSPACE_ID --purpose client --dry-run --idempotency-key YOUR_DRY_RUN_IDEMPOTENCY_KEY --json
orc workspaces update YOUR_PITCH_WORKSPACE_ID --purpose client --idempotency-key YOUR_UPDATE_IDEMPOTENCY_KEY --yes --json
orc workspaces get YOUR_PITCH_WORKSPACE_ID --json
```

## 1. Inspect pitch scope and history

Read the brand, prompt IDs, answers, and available client workspace capacity. Do not recreate the workspace.

## 2. Review ongoing monitoring changes

Run `workspaces update --purpose client --dry-run` to read the resulting workspace and entitlement summary. Review any prompt or AI selection that exceeds the client limits. A dry-run does not change state.

## 3. Start monitoring with the same history

Run the same `workspaces update` command without `--dry-run`. The workspace ID does not change. Use `workspaces get` to confirm that the purpose is `client` and the lifecycle status is `active`. Existing prompt and answer IDs remain accessible.

## If the operation stops

If you do not receive the committed response, resend the same request with the same idempotency key. To inspect the state again, run `--dry-run` with a new idempotency key. If client workspace capacity is insufficient, do not commit the conversion; inspect the quota response.

[All workflows](https://orchestor.io/docs/en/cli/workflows.md)

If a failure remains, [report it and verify the fix](https://orchestor.io/docs/cli/workflows/workflow-feedback.md), including this workflow and the failed step.

---

[Documentation index](https://orchestor.io/docs/llms.txt)