---
name: growth-outcomes
description: Complete a signup activation packet, customer winback draft or weekly GTM brief with the customer's saved Growthub team, then reopen the saved result and carry accepted work into existing Routines.
---

# Finish a useful growth outcome

Choose the customer's requested outcome below. Use get-started to resolve the
existing identity, Project, Character and exact Brand Kit version. Read
execute-growth-work before dispatching. These are methods over existing tools,
not promises that a connector, send route, plan or schedule is available.

## Check readiness before dispatch

Resolve the selected Character's saved version and execution bindings; do not
infer provider readiness from the calling chat's model. Read the relevant tool
inventory and brand context through authorized tools or the existing Growthub
selector. A Brand Kit identifier/hash alone is not its content. If content was
supplied by the user, label that provenance instead of claiming a direct read.
Never request credentials in chat or change grants to pass a readiness check.

Native Growthub execution can materialize an approved Brand Kit snapshot and
manifest into the provider workspace. Read only the exact host-supplied references
when that is the selected context path; a blanket ban on file reads prevents this
supported brand workflow. Do not search unrelated files or export host credentials.

Establish one destination for the reviewable output: the Character conversation,
an existing authorized Knowledge record, or a named business-tool draft. Report
missing inputs before dispatch. A draft in the conversation can still be useful
when external delivery is unavailable; state which outcome remains incomplete.

## Activate a signup

Read the actual signup's current setup and last completed step within the user's
scope. For a test use an explicitly labelled QA case, never fabricate customer
behavior. Return: the observed obstacle; a concise support message; up to three
concrete next steps using verified product paths; the first useful result the
customer should obtain; and the exact evidence needed to mark activation complete.
Do not equate a sent message or installed plugin with customer activation.

## Prepare a customer winback

Use the actual relationship, last relevant interaction, current offer and known
eligibility. Return one grounded opening and follow-up draft, a useful reason to
return, and the proposed next action. Preserve unknowns. Before any authorized
send, the existing delivery owner must verify recipient, sender, suppression,
consent where applicable, bounce/DND state and duplicate absence. Do not invent
discounts, product capabilities, guaranteed results or a new campaign sequence.

## Prepare a weekly GTM brief

Read the requested Project and date range. Summarize completed outcomes, current
blocks and the next three actions with owners. Cite exact source records and
separate pending work from delivered work. Carry unavailable metrics as unknown,
not zero. Posting to Slack requires the actual destination and send authorization;
otherwise save the brief in the selected Character conversation for review.

## Close the loop and continue across providers

Dispatch once with a retained operationId, retrieve the exact messageId result,
and independently reopen the saved conversation or actual destination record.
Return the deliverable first, its link/record ID, source versions, review state,
and one useful next step. Do not call a prepared delegation brief an execution.

To continue in Claude or Codex, give the existing Growthub thread link and exact
message/artifact ID. The other provider must retrieve that same saved result,
not regenerate it from a summary. Preserve the target Character's provider and
grants. A link alone does not establish cross-provider continuation.

For repeat use, apply repeat-growth-work only after a useful result is accepted.
Use current Routine controls with the same output contract and frozen context;
never install a second scheduler. Verify an actual run and its saved output.

## Measure meaningful use

Use existing analytics/lifecycle owners for source attribution. Track only
observed transitions: directory visit, connected plugin, first saved completed
outcome, accepted result and repeat completed outcome. Keep QA traffic separate.
Persist the operation/message/run references needed to deduplicate these events;
do not create parallel CRM records or public client-content telemetry. Referrals,
crawler origin renders and verified citations are separate observations. Revenue,
activation and retention require their own canonical evidence.