Scheduling the Analyst
Each analysis question runs on a cadence you set. Choosing which questions run, how often, and how to read the answers they produce.
A governed library of questions
The Analyst is a library of business questions, each of which resolves to a prepared answer with charts, reasoning and evidence. The library is governed rather than open-ended. Questions are a defined set, which is what makes the answers comparable over time and auditable when someone disputes one.
Cards carrying a red dot have new or updated results. That is the signal worth acting on: it tells you which answers have changed since you last looked, so a weekly pass is a short list rather than a re-read of everything.
What configuration actually controls
Analyst Configuration tunes when the analyses run: cadence, run time and status, per question. It does not change the Analyst view itself, since the same cards appear either way, and being clear on that saves a confusing half hour looking for a display setting that lives somewhere else.
What it does change is freshness and cost. Every scheduled run consumes credits, and an analysis scheduled daily is being paid for daily whether or not anyone opens it.
Matching cadence to the decision
The useful rule is to schedule each analysis against the decision it feeds rather than against how interesting the question is. A pipeline-health analysis that informs a weekly forecast call should run before that call. A churn-driver analysis that informs a quarterly planning conversation does not need to run nightly to be current enough.
The failure mode in both directions is common. Everything on daily produces a bill and a set of results nobody has time to read. Everything on monthly produces answers that are stale exactly when a meeting needs them.
- Run time matters when an analysis feeds a recurring meeting — schedule it to land before, not during
- Status lets you stand an analysis down without losing its configuration
- Review the schedule when your operating cadence changes, not on its own timetable
Reading what comes back
Every analysis opens with a quick answer: a concise summary that directly answers the question, with a short analysis under it. Full Analysis opens the structured write-up of executive summary, root cause and recommendations, and below the quick answer sit the KPI cards, charts and breakdowns the answer rests on.
The habit worth building is opening the supporting data once for any number you are about to carry into a decision. The quick answer is designed to be quotable, which is exactly why it should not be the only thing you read before quoting it.
What to take away
- Cadence is configuration. An analysis that runs daily and is read monthly is credits spent on nothing.
- Match the schedule to the decision it feeds, not to how interesting the question is.
- A red dot means new or updated results — that is the signal to re-read, not the whole library.
- Configuration changes when analyses run. It does not change the Analyst view itself.
Try the demo.
See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.
Explore the demo