The final leap of logic is that you are then free to distribute that class with its IF statements to ONE customer
But what if other customers need the same IF? Copy-and-paste? That is what we were trying to avoid to begin with.
This is one of the central tenets of OOP: "separate the things that change from the things that stay the same.
Task-ness tends to stay the same more than noun taxonomies or noun-based grouping.
By the way, rather than say "if customer==b then..." better indirection is "if customer.hasFeatureX then...". However, one should wait until about 3 customers use that feature before making it a column.