Loading
Because the consequences of a stage change are real work — a legal review, a kickoff, a credit check — and they are remembered reliably right up until the week somebody is busy.
Stage automation runs a defined action when a deal enters or leaves a stage: create a task, draft a quote, notify a person, open a Loop phase or raise a flag for review.
Each automation is a readable rule attached to a stage: on entry, do this. Runs are logged on the deal, so a missing task can be traced to a rule that did or did not fire rather than argued about.
Deals entering Negotiation at Harlow Logistics now open a credit check task for finance automatically. The check used to happen after signature about a third of the time, which is where the two bad debts came from.
It will not send external email on its own. Anything a customer receives goes through a person or through sequences, where the stop rules and consent state are explicit.
It writes into Loop for delivery tasks, Books for credit and billing steps, Desk for onboarding queues, and the platform notification layer for alerts.
Yes, and each is logged separately so a partial failure is visible rather than silent.
You choose. Rules can fire on entry, on exit, or only on forward movement.
Yes. Rules are attached to stages, and stages belong to a pipeline.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.