30-day GTM review

Review monthly spend, campaign results, failed-run causes, and one verdict per live motion.

Use this month_1 play after 30 days of activity to decide whether to scale, change, or stop each live GTM motion. Do not use it for empty workspace with no runs or campaigns in review window.

Needs and produces

Needs at least one started campaign or run in last 30 days. Prerequisites: at least one run or started campaign in last 30 days, sequence analytics and worksheet evidence, and credit history for same review window.

Produces monthly spend split, campaign results, failed-run causes, and one scale, change, or stop decision per live motion. Leading metric: every live motion has one recorded monthly verdict.

Ordered steps

  1. 1

    Read runs and campaign evidence

    Use runs.list to read completed and failed runs from last 30 days with causes. Use sequence.sequences.analytics_get to read campaign results and delivery metrics. Use tables.cells.read_page to read qualification and outcome evidence from campaign worksheets.
  2. 2

    Read monthly spend

    Use workspace.usage.history_list to read monthly credit and spend split.
  3. 3

    Synthesize and record verdicts

    Use tables.columns.run to optionally synthesize evidence under explicit credit cap. Use tasks.tasks.review to record one scale, change, or stop decision for each live motion.

Credits and controls

Run, analytics, worksheet, ledger, and task reads are free. Optional synthesis uses bounded table-column run and must state credit cap before execution.

Dreamstate documentation

Start

Guides

Surfaces

Workspace

Knowledge

Data

Execution

Providers

Plays and templates

Safety and cost

API reference