We arrive knowing what TSR, OEE and bucket-1 roll-forward mean

Sector experience is claimed by every supplier and means very little on its own, so it is worth being specific about where it changes an outcome and where it does not. It makes almost no difference to the quality of the code. It makes an enormous difference to the specification, which is where projects are actually won and lost.

A team that has built for a cement plant before knows to ask about the difference between the weighbridge reading and the despatch note before designing the despatch module, because that discrepancy exists at almost every plant and determines the whole reconciliation design. A team that has not built for one will design something reasonable, discover the discrepancy in week nine, and rework it. The cost of that rework, repeated across a dozen small domain facts, is the real cost of hiring a generalist.

The same applies to what gets left out. Experience tells you which requested features are genuinely used and which are asked for in every requirements workshop and then never touched. Being able to say that a particular report has never once been opened in three previous implementations saves a client money and saves us building something that will be maintained forever for no reason.

Where we have no sector experience, we say so. Domain knowledge is learnable and we have learned several, but the learning takes weeks and somebody pays for those weeks. Pretending otherwise on a first call is the most common form of dishonesty in this industry, and it is the reason so many enterprise projects arrive at their go-live date with a system that models the industry rather than the business.