Loading
Because they start with a workshop. People describe their process from memory, the description is tidier than reality, and the automation handles the clean case and breaks on the rest.
The genuinely repetitive work — the eleven-times-a-week thing too small to complain about — never comes up.
Pulse watches for repetition in the record: the same sequence of actions, the same reply to the same question, the same manual correction after the same event.
A proposal names the pattern, how often it occurred and which specific instances it observed. You read the evidence before deciding.
Nothing switches itself on. A proposal is a suggestion; enabling it is a deliberate act by somebody accountable.
It also will not propose automating a judgement — where a step exists because a person decides something, it is left alone.
Automation targets what is actually costing time rather than what somebody remembered in a meeting.
Refusing a proposal is cheap and informative — usually the repetition exists for a reason, which is worth knowing before somebody automates it later.
Yes, with the specific instances it observed.
Yes, with a reason, and they stop resurfacing.
Whoever you nominate; it is a named right.
We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.