These vendors are probably solving the problem of letting you automate your billing and invoicing process without developing your own system.
As you said earlier, there's already a lot of Ask HN about this. So a solution does exist.
I take your point that on the other hand it may require a lot of input on my part into an already existing program.
For example, if you were going from project to project as a developer - you would probably be doing your own system. And if as a project manager - you would look for an existing solution on the market, hoping to reduce development costs))
It would be a mistake to assume that either "build" or "buy" is automatically superior in any given situation.
What I will say is that the vendor has a team of flying monkeys that will spread FUD about "build" and the other vendors because that is the marketing message that moves the needle.
How good the product is really depends on the mental model it is based on. If the mental model is right it will be excellent but if it is wrong you are in for a world of pain.
Again, it depends your needs and the complexity required by your business. Happy to discuss that deeper if needed.
My first instinct as a software dev is that coding up a prototype of a billing system can be completed more quickly than evaluating two or three vendors of billing systems.
Either way you can be highly successful or deeply disappointed. What really matters is the match between the mental model behind the system and your domain.
In principle the product you buy can have a lot more labor in it both in terms of design and implementation. On one level you benefit from outside investment into vendor but on another level you (and the investors) are paying for sales, marketing and management at the vendor too. The commercial product almost certainly has a better looking UI for your team to use. Something you develop yourself will likely have a minimal UI but if it meets your needs than that's good enough.