Routines

The questions worth asking shouldn’t need asking twice.

Set up recurring investigations across the business systems you have connected. Each run uses Lytically’s analytical tools and the context recorded for the account, so you can see what changed and what deserves attention next.

Platform add-on · priced separately

Illustrative runEvery Monday
Google Analytics, Google Search Console, Google Ads
  1. Instruction

    Review last week's acquisition performance and explain what deserves attention.

  2. Connected systems

    Analytics, Search Console, and Ads, from the resources selected on the account.

  3. Report

    Organic sessions and search clicks fell. Paid held. The page change is a possible explanation, not a confirmed cause.

Illustrative. The full investigation is below.

Illustrative investigation

Monday morning. The investigation is already done.

Sample figures for a weekly acquisition review. This is not a customer result.

Someone would usually open Analytics, Search Console, and Ads, line up the weeks, and write the summary. A Routine runs that investigation on the schedule you set. The example below is one way to configure it.

An example Routine named Weekly marketing performance, scheduled every Monday at 9:00, with an illustrative report covering evidence, context, and a reading.

Example Routine

Weekly marketing performance

Every Monday at 9:00

Schedule
Weekly, on Monday. 9:00 is an example time, in the timezone saved on the Routine.
Instruction
Review last week’s acquisition performance across Google Analytics, Google Search Console, and Google Ads. Identify meaningful changes, investigate which channels or campaigns contributed, and explain anything that deserves attention.

Resources selected on the account

  • Google Analytics
  • Google Search Console
  • Google Ads

A Routine uses the resources already selected on the account.

Evidence

Prior week → last week

Google Analytics

Traffic sources

Sessions

8,400 → 7,620

−9.3% overall

Bars show the prior week, then last week, on one scale.

  • Organic−14.9% · Moved

    5,180 → 4,410

  • Paid+0.9% · Steady

    2,240 → 2,260

  • Direct−3.1% · Steady

    980 → 950

Google Search Console

Search performance

Clicks

4,860 → 4,120

−15.2% · Moved

Impressions
162,400 → 158,900−2.2%, steady
Click rate
3.0% → 2.6%

Google Ads

Campaign performance

Paid acquisition

Clicks
2,180 → 2,210+1.4% · Steady
Cost
$6,240 → $6,410+2.7% · Steady
Conversions
71 → 68−4.2%
Cost per conversion
$87.89 → $94.26

Organic sessions and search clicks fell together. Paid clicks and cost barely moved.

Context

Pricing page replacement

The pricing page was replaced on Wednesday. The recorded note says the previous URL redirects to the new page. That note can be incomplete, and it can be wrong.

Source
Operational note on the account
Status
Supplied context, open to correction

Reading

The page change is worth investigating. These figures do not establish it as the cause.

Organic sessions and search clicks fell together, while paid acquisition stayed nearly flat. Compare Search Console queries and pages across the two weeks, and see which landing pages lost organic sessions. Then check that the old pricing URL redirects, and whether the replacement changed tracking, before drawing a conclusion.

How a Routine works

Set the investigation. Lytically takes it from there.

You describe the question and the schedule. Lytically runs the investigation and saves the report where you can read it.

  1. 01

    Define the question

    Name the Routine and describe the investigation. The instruction is the boundary for the run.

  2. 02

    Choose when it runs

    Pick a supported schedule, then set the time and timezone. You can edit it, turn it off, or run it once.

  3. 03

    Investigate connected systems

    The run uses Lytically's analytical tools for the resources already selected on the account, and loads account context before it interprets the figures.

  4. 04

    Review the findings

    Open the written report on the Routine. Each run keeps its status, and a completed run keeps the report.

Schedules you can set

  • Every day
  • Every weekday
  • One weekday each week
  • The first of the month

Each schedule also has a time and a timezone.

Examples

The investigations your business should be running regularly.

These are questions you can write into a Routine. Lytically does not ship them as ready-made templates. Each one depends on the systems selected for the account.

  • Weekly marketing performance

    See how acquisition moved, and which channels account for a change in sessions, clicks, or conversions.

    Review last week's acquisition across Google Analytics, Search Console, and Google Ads. Which sources moved, and what deserves a closer look?
  • Paid advertising efficiency

    See whether spend, conversions, and cost per conversion moved together, and which campaigns or search terms to inspect.

    Review last week's Google Ads spend, conversions, and cost per conversion. Which campaigns or search terms account for a material change?
  • Organic search performance

    See whether clicks, impressions, and landing pages moved, and where visibility changed.

    Review last week's Search Console clicks, impressions, and landing pages. Which queries or pages account for the change?
  • Sales pipeline health

    See whether open pipeline or recent deal outcomes changed in a way that needs attention.

    Review the open pipeline and recent deal outcomes in HubSpot. Where did the mix or the results change, and what is still uncertain?
  • Business performance review

    Bring the connected systems into one recurring investigation, and read the figures against the definitions on the account.

    Investigate last week's performance across the connected systems. What changed materially, which recorded definitions affect the reading, and what deserves attention?

A different kind of repeat

Not another scheduled dashboard.

A conventional scheduled report typically repeats a fixed set of metrics. A Routine starts from an instruction and writes a fresh reading each time it runs.

A scheduled report

  • Repeats a predefined set of metrics or a dashboard export.
  • Sends the same shape of result on each run.
  • Leaves the comparison, the definitions, and the follow-up to whoever reads it.

A Routine

  • Follows the investigation you wrote, using the connected systems that question needs.
  • Weighs the account context on record, including objectives, terminology, and analytical notes.
  • Explains what changed, what is uncertain, and what deserves attention next.

The instruction, the selected resources, and the available tools still bound the run. A reading is an interpretation of the evidence. It is not a guaranteed cause, and other reporting tools can investigate as well.

MCP and Routines

The same analytical foundation. Running on your schedule.

Lytically’s analytical tools and account context are available through MCP, so a compatible assistant can investigate while you are in the conversation. A Routine uses that same foundation on a schedule. The Lytically Platform is where those capabilities are described.

Interactive investigation

You ask, and the assistant calls Lytically.

ChatGPT, Claude, or another compatible client starts from your question and calls the analytical tools through MCP. You are in the thread for that run.

Routine

The configured investigation runs when it is due.

Lytically starts the run, uses the selected resources and account context, and saves the report on the Routine. You do not have to open the question again for that scheduled run.

What each run can see depends on the connections and context available to that way of working. A Routine is Lytically’s scheduled investigation. Other products can automate analysis too. The difference here is the analytical tools, the connected systems, and the context kept with them.

Availability

A separate add-on for recurring investigations.

Routines are part of the Platform and priced separately. They are not included in Starter, Growth, or Business. Investigating from ChatGPT or Claude does not require a Routine.

Price and allowances are not published on this site. The free Blueprint Call is the conversation for whether a Routine fits the questions you want repeated.

Book a free Blueprint Call

Questions

Schedules, reports, and what a Routine includes.

What is a Lytically Routine?

A Routine is a named investigation with written instructions and a schedule. When it is due, Lytically runs it against the resources already selected on the account and saves a written report on the Routine.

How is a Routine different from asking ChatGPT or Claude a question?

Asking ChatGPT or Claude is interactive. You start the question, and that assistant calls Lytically's tools through MCP. A Routine is an investigation you have already configured. Lytically runs it when it is due, without you starting it each time.

Both can use the connected systems and the account context available to that way of working. A Routine runs in Lytically. It is not a scheduled task inside ChatGPT or Claude. See the Lytically Platform for how MCP access works.

Can a Routine investigate multiple integrations?

Yes, when those systems are connected and selected on the account. A Routine uses that selection. It does not keep a separate list of integrations. One investigation can include Analytics, Search Console, Ads, and HubSpot where they are available. See the live integrations.

How often can Routines run?

You can schedule a Routine for every day, every weekday, one weekday each week, or the first day of each month. You choose the time and the timezone.

You can edit the instruction or the schedule, turn the Routine off so the schedule stops, turn it back on, or run it once without waiting.

Does a Routine use my business context?

Yes. Each run loads the account context on record before it interprets the numbers. That can include objectives, terminology, and analytical notes, along with account details such as timezone and currency.

That context is weighed with the measurements. It is not treated as automatically true. A run can also read a few recent completed reports as prior analysis, and those reports are not a fresh measurement.

Where can I see previous results?

In Lytically, on the Routine. The run history lists each run, its status, and the written report when one was produced.

What happens if a connected system is unavailable?

The run can fail, and that failure is saved with the run. Temporary problems are retried. You can start the Routine again from Lytically once the system is available.

Are Routines included with the Lytically Platform?

Routines use the Platform, and they are priced separately. They are not included in Starter, Growth, or Business. You can investigate from a compatible assistant without a Routine.

Price and allowances are not published on this site. The Blueprint Call is where to discuss whether a Routine fits.

Does Lytically retain Routine reports?

Completed reports are stored with the Routine so you can open them later. A later run can look at a few recent completed reports as prior analysis. Deleting a Routine deletes its run history. This site does not state a further retention period.

The next investigation could run itself.

Tell us which questions your business needs answered regularly. We'll explore how Lytically could investigate them using your connected systems. A Blueprint engagement, if you choose one, is scoped separately.

Book a free Blueprint Call