Some founders have a strong technical background. They can get something working, and they might have put a great deal of thought into how it's built. I'd still want to ask who will use it, who will pay and what would persuade somebody to change from what they do today.
A founder with commercial experience might have a clear idea of the opportunity and how to reach customers. They may then need help deciding what to ask a development team to build, how to keep the first version manageable and how to judge the work as it progresses.
I've worked with clinicians who have a very clear idea of the service they want to provide. Their experience is essential, but turning that into a business also involves decisions about the product, the technology, the team and how the service will be paid for. Those need attention alongside the clinical work.
Getting the right people involved
I wouldn't expect one person to know all of this. As a founder, I've had to work with people whose knowledge is different from mine, and make sure we're using that knowledge when we make decisions.
That's one of the reasons I like speaking to people individually when I review a business. The leadership team, product people, developers and customer-facing staff may each understand something the others haven't seen. It's worth finding out whether they're working towards the same thing and where their views differ.
The useful question is where the gaps are in this particular business. Do we need to understand customers better? Is the team clear about what to deliver? Have we involved the people who know how the service will actually be used?
This applies to an established company launching a product as well as a startup. Before committing more money, I'd want the leadership team to know which questions they can answer confidently and where they need more information or experience.