I wouldn't.
Knowing what to build is part that many businesses struggle with.
As much as consultants are lambasted, my experience of companies is that they struggle to develop or maintain anything in-house - even where it should theoretically make economic sense. >>46864857
I imagine "vibe coder" will eventually coalesce with business requirements analyst, into a sort of "LOB developer-lite." I.e. every low-code products' undelivered citizen developer dream.
You need someone in the technical details and with some developer background (thinking through edge cases is a hard skill requirement), and you need someone with the process analysis and documentation skills (as well as the ability to push back / simplify requirements where it makes sense).
External developers/consultants are typically terrible at the requirements discovery and specification stage, because they're not embedded day-to-day with the business. Ergo, you get stupid feature decisions because someone left a sentence off a doc.
From your other comment, I think you're thinking about more complex / core / feature-rich solutions than I am. I agree those may remain SaaS / outsourced.
But there's no way in hell dirt-simple CRUD and "I am the only person in the world who has this need" solutions stay out of house.