Workflows

Back office process automation across your existing tools

Explore back-office process automation for manufacturing, construction and property management, with ERP workflows, review steps and documented outputs.

  • 31playbooks
  • 3industries
  • 1,554processes in the catalog

What every playbook covers

Each playbook answers the same questions in the same order. Read one and you can find your way around the next in seconds.

  1. The job in one minute What it produces, who owns it, how often it runs.
  2. Why it hurts Where the hours go and where the mistakes cost money.
  3. Systems it touches The ERP screens, portals, spreadsheets and inboxes.
  4. The workflow, step by step Each step marked Action, Decision or Human review.
  5. Rules vs judgment What runs as an exact rule, what the model reads, what a person decides.
  6. When it stops The common exceptions and what happens to each.
  7. What you end up with The finished output and the record behind it.
  8. Questions The ones controllers and managers ask first.

How to pick your first playbook

Hours are one reason to automate. A legal or contractual clock is another. The best first agent usually has both.

Big hours

Daily reports, work order intake and shop floor reporting sit at the top of their catalogs.

A clock that cannot slip

Certified payroll, lien waivers, COI compliance, security deposits, adverse action notices, late fees, HOA violations, HUD recertifications and trust account reconciliation all run on dates set by law or contract.

Money out the door

Three-way match, sub pay app review and invoice coding guard every payment.

In every clock-driven playbook, the agent computes the date as an exact rule, and a person approves anything that leaves the building.

From playbook to running agent

A playbook is a head start, not a script. Your team's version will differ in places, and that is fine.

  1. Read the step-by-step workflow and mark what your team does differently.

  2. Pull ten recent real cases, including last quarter's three ugliest exceptions.

  3. Build the agent in the Studio with the person who runs the job: talk it through, show your screens, and watch the agent do each step live.

  4. Turn the playbook's rules into Rules and Tables, and its review points into review steps.

  5. Run supervised cycles until the exceptions look like the playbook's list.

  6. Schedule it.

How the Studio builds and verifies each step is on the Product page. Product →

Your workflow is not on the list?

Most are not. The other 1,500-plus processes in the catalog work the same way: write the steps down the way you would for a new hire, and the Studio turns them into an agent. Agent-Ready SOP →

Questions

Why these 31 and not the 31 biggest by hours?

The biggest jobs cluster in one area per industry, like shop floor work or maintenance. The playbooks spread across areas and pick jobs that combine hours, legal exposure and money at risk, which is how a controller picks a first agent.

Do the playbooks change by ERP?

The method does not. Screen names and menus do, so the agent is always shown your screens during the build.

Can one agent cover a whole playbook?

Usually one playbook becomes one workflow with branches, or a small chain of workflows that hand off through a shared table. Certified payroll, for example, splits into a one-time job setup and a weekly report.

How current are the rules?

Regulatory playbooks are reviewed every six months. When a rule changes, you edit one rule in the agent. It is versioned, reversible and live on the next run.

From a playbook to a running automation

Back office process automation connects the work between your ERP, inbox, spreadsheets and external portals. Each playbook identifies the inputs, rules, decisions and finished output so a process owner can decide what to automate.

Choose one recurring job, walk through it with its owner, and define the access and source documents it needs. Configure the routine actions and validation rules, then test both normal cases and exceptions. Agree which actions need approval before scheduling the workflow.

Keep ERP automation focused on the system of record while the agent handles the surrounding handoffs. Review the examples below, then bring your own workflow to a demo to confirm its scope.

Discuss your workflow in a demo →

No prompts. No babysitting. No Integrations.

Get a demo with our specialist team.

Get demo