Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Explain why a metric moved by decomposing its definition, population, segments, timing, and data pipeline into testable hypotheses.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this for an ad hoc why did X move? question. Begin with the identity of X,
not a story about the business.
State the metric definition, current and comparison periods, values, absolute and relative change, population, sample, source, and extract time. Recalculate the result from the supplied detail when possible. Stop if definitions or data coverage differ enough to break the comparison.
Quantify how much of the total change each component explains. Avoid summing overlapping segments as if they were independent.
Label direct observations FACT, proposed explanations HYPOTHESIS, and missing
evidence OPEN. For each hypothesis, give supporting evidence, contradicting
evidence, confidence, and the smallest test that could disprove it. If the data
supports no cause, say so.
Never claim cause from timing or correlation alone. Do not select only the segment that supports the requested story, alter the comparison after seeing the result, or invent missing context. Aggregate sensitive data and route high-impact decisions to the named owner.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.