Changes break things nobody expected

What it is

Automation written by several people over several years

Workflow rules, process builders and flows added one at a time, each sensible alone, now firing on the same record in an order nobody has traced. This is what makes a rebuild cost more than a greenfield build, and it is why a change that should take an hour takes a week and breaks something else.

Confirm it yourself

How do you confirm this yourself?

Open Setup and count the active flows, process builders and workflow rules on your Opportunity object. More than eight in total, from more than two authors, is the pattern.

You have this if more than eight pieces of automation from more than two authors. If your org comes back the other side of that line, this is not your problem, and nothing on this page is worth buying to you. Finding that out costs nothing and takes ten minutes.

If the check confirms it

Automation audit, consolidation onto Flow, documented order of execution

Fixed price on a written scope, 85 hours at fifty euro an hour, about 4 weeks elapsed. Documentation and sixty days of support after handover are in the price rather than an addition.

€4,250 · 85 hours · 4 weeks

When it is bigger than a repair

When is this the org rather than one fault?

This one travels with nobody being able to change anything, and the second is usually what the first turns into. If more than two of the six match at once, the pattern is usually one org that was never configured for how the company sells now, rather than several separate faults. That is an implementation, not a repair, and it is priced the same way: hours multiplied by fifty.

Asked often enough to answer here

Questions