Not whether, but what
In most machine-building companies documentation is produced in the design department – at the end of the project, when the machine has to be finished and nobody has time. The result is familiar: the manual of the previous machine is copied and adapted as far as time allows.
An in-house technical writing team solves this but pays off only if it is permanently busy. A service provider solves it too, provided it is clear what it takes on and what not. The sensible question is therefore not “in house or external” but: which activities need the company’s knowledge – and which mainly need time, method and practice?