Cheatcode_
Feedback

Front page / By role / Pick growth metrics

Pick growth metrics

Choose the numbers for each stage and set targets.

For Growth marketer · Knowledge pack

What do you want to know from your data?

One line is enough. Step 1 asks the rest in your AI app, and nothing is done until you approve the brief it writes.

It never leaves this computer: not uploaded to Cheatcode, never used to train a model. Your AI app reads it from the case folder.

Add details (optional)
Start

Step 1 asks anything else it needs, in your AI app. Nothing you write here or put in the case folder comes to Cheatcode.

In the case folder's materials/: Your data exports (CSV or spreadsheets) and any metric definitions, or a connected warehouse.

The 3 steps

  1. 01

    Agree the definitions and plan

    Then you approve, before the next step starts.

  2. 02

    Compute with code

  3. 03

    Explain and write up

How it does this well

One analyst, every number from code. Not found and out of scope are valid answers here: it says so instead of guessing.

How the field does this well
  • Run brief, draft, edit, then brand review; the brief states audience, goal and the one message.
  • Make voice rules checkable: behaviors and banned phrases, not adjectives.
  • Verify every statistic, quote and brand reference before publishing.
  • Back attribution claims with an experiment, or label them as correlation.
Ground it first

Ask for, or look in materials/ for: the brand voice rules (positive rules and banned phrases), positioning, and past results. If there is none, say plainly that the result rests on general defaults, and name them.

What stays with the person

Positioning, claims approval, and the final publish decision. Prepare these; never decide them.

The check that makes it trustworthy

A lint pass against the voice rules and banned phrases, every factual claim linked, and attribution claims labeled.

The person's own data

If the person has connected HubSpot, Google Analytics 4, Google Drive / Docs / Sheets, Notion, Figma, read their data through that connector instead of asking for exports, and say which source each number or fact came from. Without one, work from materials/.

Also from data
  • Use the person's governed definitions; when a question falls outside them, say it is not defined rather than improvising a join.
  • Compute every number with code that reruns from the raw files; never type a number.
  • Write the plan first, run it step by step, and keep known data quality facts and statistical guardrails in one rules file.
  • Check numbers deterministically: a judge accepts near misses that code rejects.
  • What stays with the person here: choosing between competing definitions and deciding whether a result is decision grade.
  • The check here: every reported number traces to a named definition and a script that reruns, and out of scope questions are answered as not defined here.

Where things stay

On your computer
Your files in materials/, every result in outputs/, the work itself. It runs in your AI app, on the plan you already pay for.
With Cheatcode
The steps, the gates and how far each case has come, so a case survives closing the app. See your cases.