Four jobs we are asked for most

That is the normal case, and it is what a custom coworker is for. These four are here because enough companies go looking for them by name that describing them properly is useful. The work of building one is the same either way: walk the process once, exceptions included, and we build against it.

A role page describes everything a coworker for that team owns; a flow page describes one job in the detail somebody evaluating it actually needs. Invoice matching and month-end close both belong to the finance coworker, and the same deployment runs both.

Yes, and most do eventually. Teams generally start with one job, because a coworker built for one job can be judged on whether it did it, and then add the next once the first has stopped needing corrections.

It depends on how many systems the job touches and how quickly access is issued, and we would rather give you a real answer on a call than a number on a page. The part that is always true: you walk us through the work once, we build it, and it runs beside your team until its output stops needing corrections.