This started life as a comparison between two products, and comparisons like that go stale in about a year. The useful version is not which vendor. It is which kind of step you are looking at, and that answer holds no matter what anybody ships next quarter.
It is the same deterministic versus judgment line, pointed at a tooling decision instead of at a workflow.
Say the unpopular half first
Rule based automation is the right answer for a large share of the work in your agency. Not the leftover share. A large one.
If you can draw the flowchart in advance and it is not going to change, a rule is cheap, reliable, and boring in the best possible way. Form submitted, so create the record. Policy bound, so open the onboarding ticket. Renewal at ninety days, so send the notice. That work is enormous in volume, it runs perfectly, and pointing anything cleverer at it is a downgrade.
I am putting that first because the rest of this is not credible without it. There is a lot of noise right now that treats rules as obsolete. They are not obsolete. They are finished, which is a different thing and a better one.
Where a rule runs out
A rule needs the branch described in advance. That is its whole nature and also its whole limit.
“Find the household, work out whether this is the same person as the lead from March, look at what is expiring, and set up the right follow up” is four judgment calls stacked on top of each other. You cannot write a rule for it, not because rules are weak, but because nobody can enumerate the branches ahead of time. The moment you try, you are back to writing a rule for every exception, which is exactly how agencies end up buried.
There is a second limit that gets less attention. A rule does not check its own work. If the platform reports success on a write that did not land the way it was asked, the rule moves on happily and nothing tells you. Silence and success look identical.
| A rule wins here | Judgment wins here |
|---|---|
| The trigger is unambiguous and the response never varies. | Working out what happened is most of the work. |
| You can draw the whole flowchart today and it will still be right next year. | The branches cannot be enumerated in advance, and new ones keep appearing. |
| High volume, identical every time. Hundreds a week. | Lower volume, different every time, expensive to get wrong. |
| The input arrives in a fixed shape you control. | The input is a document, an email, or a carrier report whose format moves. |
| Cheap to build, and you want it to just sit there working. | Worth supervising, because the alternative is somebody reading it all by hand. |
Most agencies want both
This is the part the original version of this argument got right and I am keeping it.
You are not choosing a side. A working agency has a large layer of rules handling the predictable volume, and a thin layer of judgment based work handling the parts that were always getting done badly or not at all. The rules are the floor. The judgment work is what you add on top of a floor that already holds.
Reversing that order is the expensive mistake. Judgment based work layered onto a foundation nobody has mapped does not compensate for the missing floor. It just moves faster across a floor with holes in it.
The cost nobody prices in
Here is the connection back to why these projects fail.
So the question is not only “can a rule do this.” It is also “do I want to own one more rule forever.” Sometimes the answer is yes and it is obvious. Sometimes you are about to write your fortieth exception handler, and the honest read is that the underlying step was never deterministic and you have been pretending it was for two years.
Judgment based work has its own version of that bill, and it is a different shape: it needs supervision, it needs a boundary around what it is allowed to finish, and it breaks when a vendor changes an interface. That is worth counting honestly too.
Neither of these replaces your management system. Your AMS stays where it is, it stays the system of record, and anything that cannot write back into it is building you a second silo whatever else it claims to be doing.