3 runs/ 10Thin
The automation is new and has only run three times.
Then
The automation has finished regularly for weeks.
Rough estimate · keep watching
Peak Automations · Analytics
What your automations get done.
Honestly labelled as an estimate.
Analytics sums up what is backed today: how often each automation ran, how many runs finished, how healthy it is and roughly how many minutes of manual work it saves. Attributing revenue to an automation is planned and not part of analytics today.
See what your automations achieveIllustrative example · sample data · no real numbers
EXAMPLE / LIVE PREVIEWOne check.
One check.
The fitting step.
01 / Example value
How many runs is the estimate based on?
02 / What Peak Automations showsThe automation is new and has only run three times.
Rough estimate · keep watching
Change the example value. The next step follows the check.
Sample data · nothing runs
One example. Two paths.
The check
decides the next step.Compare both paths below ↓
decides the next step.Compare both paths below ↓
Two example bases
How many runs is the estimate based on?
Schematic example. Peak states for every estimate how many runs it rests on.
120 runs/ 10Broader
The automation has finished regularly for weeks.
Read minutes saved · still an estimate
Trust needs clarity
What analytics can do today, and what not.
01 / The existing evidence
An example, not a measurement
The numbers on this page are made up. Your analytics come only from your own runs.
- 3 runs/10The automation is new and has only run three times.Rough estimate · keep watching
- 120 runs/10The automation has finished regularly for weeks.Read minutes saved · still an estimate
02 / Your check
Revenue attribution planned
Peak does not show today which revenue goes back to an automation. That attribution is planned.
4 / 1010 / 10
Compare both paths and their reasons.
03 / The clear limit
Minutes are an estimate
Time saved rests on assumptions per step. It is a guide value, not measured working time.
Example│Nothing runs
The next step
See which routine pays off.
Start Peak Automations and let your first runs fill in the analytics.
See what your automations achievePeak Automations · AnalyticsHow often did it run?
Illustrative example · sample data · no real numbers
Frequently asked questions
Are the minutes saved measured?
No. They are an estimate from assumed times per completed step and always labelled as such.
Does Peak show what revenue an automation brings?
Not yet. Revenue attribution is planned and not part of analytics today.
Where do the numbers come from?
From the run history and the health status of your own automations.