Rules that do the follow-up for you.

On the Operator plan and up.

On the Operator plan, $399 a month. Put the whole crew on it. Nobody pays per person.

Event to action

Watch for the eventA measurement lands, an order goes out, a delivery comes up short.
Do the next stepDraft the proposal, book the visit, set the reminder, tag the job, notify the person who has to act.
Record the runEvery firing is logged with what it acted on, what it produced, and which rule ran, so a wrong outcome traces back to its rule.
Keep the receiptA rule that looked at the event and did nothing leaves a line in the log too.

Example workflowIllustrative flow of the shipped rule engine.

The same few steps your office repeats every week.

Each rule connects two things that already exist in the record, so nothing has to be re-entered between them.

Step 1
Measurement to proposal draft
A completed takeoff can open a priced proposal draft instead of sitting in someone's inbox.
Step 2
Supplier answers, office knows
When a supplier responds to a purchase order, a rule can tag the job or email a teammate about it.
Step 3
Receiving exception to a person
A short or damaged delivery can email a teammate who can act on it.
Step 4
Permit moves, the visit gets booked
A rule can put a site visit or a reminder on the calendar a set number of days out, on the job the event happened on.
Step 5
Permit moves, the answer is on file
A rule can read what the county has on file for that kind of work and write the answer into a queue for you to read.
Step 6
A rundown of where the jobs stand
A rule can write a plain rundown of your open jobs into that same queue, at most one a week. There is no timer, so the first thing recorded in a week writes it and a quiet week gets none.

The rule runs whether the office is slammed or not, and the log shows it did.