Choose the trigger
Start from a meaningful event such as a stage or status change.
Automate the follow-up work your process already expects
Run routine handoffs automatically and keep a record of what happened.
The expensive failures are often ordinary steps that never happened
For operations-minded owners whose follow-up still depends on memory.
1
A won job waits for someone to create production work.
2
Customer follow-up depends on memory.
3
The same task list is rebuilt for every project.
4
Teams distrust automation they cannot audit.
One job action can start the next four.
A job event can email the customer, notify the PM, create the work order, and assign the follow-up task - with execution history showing what ran.
A visible trigger-to-action chain
Add conditions
Limit the rule to the jobs, people, or values where the action belongs.
Choose actions
Create assigned tasks, send notifications or email, and make the appropriate work order.
Read the history
See what ran, what it created, and why an action was skipped.
Questions shops ask us
What can start a rule?+
A job reaching a status, an estimate being accepted, a number of days passing, or a work order finishing a step.
What can a rule do?+
Create and assign tasks, send notifications or email, raise the next invoice on a payment schedule, and create work orders.
Can rules have conditions?+
Yes. A rule can be limited to a job type, a status, a person or a field value.
Can we see what ran?+
Yes. The job's activity feed shows every action a rule took and why a step was skipped.
How do people get notified?+
In the app, by email, and by push notification on the phone, according to each person's own notification settings.