It is from the viewpoint of the business partner.
First, if you want to deal with a technical founder, then you could explain (in gross terms) what the project will do.
Second, you must explain some technical requirements (if any). For example, "we have a website build on python." It is important because most developers don't know more than 2-3 languages. It's ok if the project starts from scratch.
Third, point to any requirement that it is unusual. For example, if a system requires "VR", "3d", "voice assistance" or other feature.
For example, let's say we want to build a shoe store.
Requirements: "We want a website that helps us to sell shoes" (straight to the point). You don't need to explain in detail what kind of shoes or where it is located unless it is important to talk about it.
Technology: "We already have a site using Wordpress, but we want to start from scratch," or "we don't have anything."
Requirements: "And we want to sell shoes using Stripe and PayPal."
A seasoned developer will ask about the volume and size of the operation. It is not the same to sells for 100 customers per day than to sells to 1 million customers per day.
You also want to hear about the platform, a server, a VPS, a cloud, etc.
If there is a team, then he/she wants to meet the team or are least know who are they.
You don't want to hear any buzz-term. And usually, you don't want to hear any that is the current hype. You want to hear some well stable (and supported) technology.
You don't want to hear somebody that wants to jump in without asking at least the minimum. Some people are fast to join a project, but they are also fast to quit it.
Somebody that asks money upfront.
You don't want to hire an inexperienced developer. Some jr developers want to experiment at your cost.
You don't want a shy developer or a yes-man. You want somebody that is willing to defend his/her point.