I think we should be careful about throwing around numbers when we have no idea of the actual situation. For example, if we look at the Total Cost of Ownership

I think we should be careful about throwing around numbers when we have no idea of the actual situation. For example, if we look at the Total Cost of Ownership of the project, it may turn out that after the ramp of onboarding and initial development has been climbed, it's relatively much faster and cheaper over time to add new features and maintain an existing OCaml or F# project, because its language features highly encourage maintainability and 'clean code'. It may also be the case that because of type system features like exhaustive pattern matching and abstract types or units of measure, or compile-time code generation, F#/OCaml prevent and save the project from many bugs and incidents which might have plagued the C# project. Also it may happen that the fact of using OCaml/F# may attract tech talent who may not have otherwise considered your company. There are many variables and the answer is not really clear-cut.