All 18 modules
Work

Automations

Every firm runs on a busy-season playbook that lives in the owner’s head: when this moves to waiting, chase them in three days; when that comes back, tell the preparer. This is that playbook, written down once and then actually followed.

What it does

  • Rules that fire on what a status means, not on what you happened to call it
  • Sequences, so a follow-up cadence is a series rather than one email
  • Recipients resolved by role from the client record — no lists to maintain
  • Scoped to a pipeline, a client set or an engagement type
  • A rule that starts looping is stopped before it reaches anyone twice

How it works

Rules that survive you renaming a column

A rule fires on what a column means, not what it is called, or on a date — so many days before or after something. Rename “In review” to “Partner desk” in the middle of the season and everything keeps working.

It cannot run away with your client list

A rule that keeps firing on the same job inside a short window is treated as looping and stopped. An automation that runs forever is worse than one that never runs, because this one reaches your clients.

A follow-up cadence, not one hopeful email

Enrollments walk through a sequence a step at a time, so “chase at three days, again at seven, then tell me” is a thing you set up once rather than a rule trying to work out where it got to.

You can see which columns are armed

A column that fires automations is marked on the board, and hovering it tells you what it does. An automation nobody can see is a surprise waiting for the worst possible week.

The LedgerOS pipeline board: engagements in Not started, In progress, Waiting on client and In review columns, each card showing the client, the work, its owner and its due date.

It knows who the taxpayer is on every client

Address a rule to the taxpayer and it reaches the right person on all four hundred of them, because recipients resolve by role off the client record. No list to build and no list to maintain. Scope keeps a rule to the pipeline, client set or engagement type you meant.

  • Recipients by contact role rather than by hand-built list
  • Scope by pipeline, engagement type or client set
  • Unsubscribes are honored, and a client who has opted out stays opted out across rules

Next: RecurringThe monthly work turns up on its own, with its checklist and its invoice.

Read on →

Ready to retire the stack?

One plan for the whole practice — $129 per seat, every Practice module included. Start your free trial today; migration support from your current tools comes standard.

14-day free trial · No credit card required · Cancel anytime