{
 "schema": "aiblocks-page/1",
 "id": "weekly-product-funnel-watcher",
 "type": "agent",
 "name": "Product funnel steps and experiment review",
 "summary": "Review where user progress drops. Compare sign-up groups, keep causes as hypotheses and propose one experiment for the weak step.",
 "headline": "Product funnel steps and experiment review",
 "subhead": "Share dated events, sign-up dates, the tracking plan and known changes. It checks step rates and group patterns against prior weeks, then investigates repeated gaps. You get a funnel review and one proposed test. Short history limits comparisons, and a before-and-after change or chain of why questions does not prove a cause.",
 "job": {
  "id": "build-product",
  "name": "Build a product people want"
 },
 "level": "intermediate",
 "thinking": "high",
 "tested": true,
 "updated": "2026-11-03",
 "first_published": "2026-10-21",
 "inputs": [
  {
   "type": "spreadsheet",
   "required": true,
   "label": "Spreadsheet",
   "what": "a spreadsheet with its data, formulas and charts"
  },
  {
   "type": "performance_sheet",
   "required": false,
   "label": "Performance sheet",
   "what": "ad or store performance export for a closed date window, with definitions"
  },
  {
   "type": "plan",
   "required": false,
   "label": "Plan",
   "what": "a dated plan: what to do, in what order, with a decision rule for each step"
  },
  {
   "type": "question",
   "required": true,
   "label": "Question",
   "what": "the problem, decision or piece of work you want help with, and what a good outcome looks like"
  }
 ],
 "outputs": [
  {
   "type": "audit_report",
   "required": true,
   "label": "Audit report",
   "what": "findings with evidence, severity, missing inputs and next actions"
  },
  {
   "type": "plan",
   "required": true,
   "label": "Plan",
   "what": "a dated plan: what to do, in what order, with a decision rule for each step"
  }
 ],
 "you_give": [
  "Last week's event log or per-step counts with user id, event, time and sign-up date",
  "The numbers your team reports today (advised)",
  "What changed last week, with dates (advised)",
  "Your tracking plan and experiment log, once they exist"
 ],
 "you_get": [
  "A tracking plan with steps, groups, one main metric and the input metrics you control",
  "Conversion per step against its normal swing, with real moves marked",
  "Each sign-up week's path beside the changes that moved it",
  "A verdict on any experiment that reached its read date",
  "The cause behind a repeated loss, or \"unknown\" with the fact that would settle it",
  "One experiment with one change, one rate and a read date"
 ],
 "use_when": [
  "Your product tracks events and the weekly review is a dashboard and a debate.",
  "A rate moved and nobody can say which of last week's three changes did it.",
  "You report numbers that only go up and want the ones that show cause."
 ],
 "skip_when": [
  "Your product has no event tracking yet: set up a simple event list first, or review a plain dashboard with your team.",
  "Fewer than about 200 users reach the funnel each week: read two weeks together by hand, since one week swings too much.",
  "An experiment just ended and you want the full result: use the Experiment plan and results reviewer."
 ],
 "output_sample": {
  "input": [
   "Last week's events with user id, event, time and sign-up date",
   "The numbers your team reports today (optional)",
   "What changed last week, with dates (optional)",
   "Your tracking plan and experiment log, once they exist (optional)"
  ],
  "prerequisites": [
   "An AI that can read files, such as Claude Code, to keep the files between weeks",
   "An export of events from your analytics tool"
  ],
  "output": [
   {
    "name": "This week",
    "contains": "The main metric against last week, the inputs you control, and how many steps moved past their normal swing."
   },
   {
    "name": "The funnel",
    "contains": "Conversion per step, last week's rate, the normal swing, and a mark for noise or a real move."
   },
   {
    "name": "The groups",
    "contains": "Each sign-up week's path through the steps, beside the change that shipped that week."
   },
   {
    "name": "Experiments read",
    "contains": "Any experiment that reached its read date, with its rate, the move expected, the move seen and a verdict."
   },
   {
    "name": "The cause",
    "contains": "The chain of whys and the fixable cause, or unknown with the fact that would settle it."
   },
   {
    "name": "One experiment",
    "contains": "One change, the rate it should move, who gets it and the date to read it."
   },
   {
    "name": "Vanity watch",
    "contains": "Any reported number that only goes up, and the per-customer number to use instead."
   },
   {
    "name": "Files and missing",
    "contains": "Each step's saved file, every MISSING line and any checks that failed or could not run."
   }
  ]
 },
 "output_shape": "THIS WEEK\n  <main metric> <value> (<change>) | inputs: <input> <value>, <input> <value> | output check: <holds | drifting> | moves past swing: <n>\n\nTHE FUNNEL\n  <step> -> <step> | <%> (last week <%>) | swing <%> to <%> | <noise | MOVED>\n\nTHE GROUPS\n  week of <date> | <step %> | <step %> | <step %> | change that week: <release or none>\n\nEXPERIMENTS READ\n  <experiment> | rate: <name> | expected <move> | got <move> | verdict: <keep | stop | rerun>\n\nTHE CAUSE\n  <step> | why: <chain> | fixable cause: <what> | or unknown, settle with: <fact>\n\nONE EXPERIMENT\n  change: <one thing> | should move: <rate> from <%> by <amount> | who: <group> | read on: <date>\n\nVANITY WATCH\n  <number reported> | why it is vanity | use instead: <per-customer number>\n\nFILES AND MISSING\n  <each step's file> | MISSING: <every line>",
 "how_to_use": [
  "Start a chat with the agent. In Claude Code, add it as a skill or save it in .claude/agents, then ask it to run this week.",
  "Export last week's events in the same shape each week. Put the file in one folder, or attach it in the chat.",
  "On the first run, describe the product and the numbers you report. Approve the tracking plan it builds.",
  "Each week, paste what changed, with dates. Read the funnel and the one experiment. Run the experiment you agree with in your own tools.",
  "Run it again next Monday. It reads the new groups and judges any experiment that is due."
 ],
 "checks": [
  "Every move is compared with the step's swing before it is called a move.",
  "Groups are read as groups, not as an all-users average.",
  "A cause was sought only when a step moved past its swing or lost the most twice.",
  "One experiment at most, with one change and one rate.",
  "Nothing in the product or tracking was changed."
 ],
 "steps": [
  {
   "position": 1,
   "id": "event-tracking-planner",
   "name": "Event tracking planner",
   "summary": "Turn product steps and set goals into named actions, user rules, and a plan to track use.",
   "url": "https://useaiblocks.com/skills/event-tracking-planner"
  },
  {
   "position": 2,
   "id": "vanity-metric-fixer",
   "name": "Business metric quality reviewer",
   "summary": "Find the vanity metrics in your weekly report and swap them for per-customer rates you can act on, plus one main number to track.",
   "url": "https://useaiblocks.com/skills/vanity-metric-fixer"
  },
  {
   "position": 3,
   "id": "input-metric-picker",
   "name": "Business activity metric planner",
   "summary": "Pick input metrics you control from the numbers you report. Get three to six inputs, a proxy test for each and one output to check them.",
   "url": "https://useaiblocks.com/skills/input-metric-picker"
  },
  {
   "position": 4,
   "id": "conversion-funnel-analyst",
   "name": "Conversion funnel analyst",
   "summary": "Find where people leave your sign-up or checkout funnel. Give it an event log and your steps to get conversion per step and ranked fixes.",
   "url": "https://useaiblocks.com/skills/conversion-funnel-analyst"
  },
  {
   "position": 5,
   "id": "cohort-funnel-reader",
   "name": "Cohort funnel analyst",
   "summary": "Read your results by join week or month. See which changes moved which rates, and whether the report can be trusted.",
   "url": "https://useaiblocks.com/skills/cohort-funnel-reader"
  },
  {
   "position": 6,
   "id": "root-cause-finder",
   "name": "Root cause finder",
   "summary": "Find the root cause of a problem that keeps coming back. Get a chain of whys checked against facts, a fix and a prevention check.",
   "url": "https://useaiblocks.com/skills/root-cause-finder"
  },
  {
   "position": 7,
   "id": "one-change-experiment-planner",
   "name": "One-change experiment planner",
   "summary": "Plan a one-change experiment. Tell it what you want to learn and get a test plan that changes one thing and says what each result means.",
   "url": "https://useaiblocks.com/skills/one-change-experiment-planner"
  }
 ],
 "next": [
  {
   "name": "First-use onboarding designer",
   "url": "https://useaiblocks.com/skills/first-use-onboarding-designer",
   "why": "Shape the product"
  },
  {
   "name": "New app project planner",
   "url": "https://useaiblocks.com/skills/new-project-planner",
   "why": "Shape the product"
  },
  {
   "name": "In-app tour designer",
   "url": "https://useaiblocks.com/skills/in-app-tour-designer",
   "why": "Shape the product"
  }
 ],
 "source": null,
 "credits": [],
 "files": [],
 "links": {
  "page": "https://useaiblocks.com/agents/weekly-product-funnel-watcher",
  "markdown": "https://useaiblocks.com/agents/weekly-product-funnel-watcher.md",
  "json": "https://useaiblocks.com/agents/weekly-product-funnel-watcher.json",
  "instructions": "https://useaiblocks.com/skills/weekly-product-funnel-watcher/SKILL.md",
  "api_item": "https://useaiblocks.com/api/v1/items/weekly-product-funnel-watcher",
  "api_document": "https://useaiblocks.com/api/v1/documents/agent/weekly-product-funnel-watcher",
  "mcp": "https://useaiblocks.com/mcp"
 }
}
