Why the right pre-meeting information changes the quality of the meeting

A discovery call or site visit is a first impression — not just of you as a person, but of how your business operates. When you show up with no prior context, you spend the first ten minutes of the meeting gathering information that could have been collected in advance. The prospect has to repeat themselves, the conversation stays at surface level for longer than necessary, and the overall impression is one of a business that does not have a clear process.

On the other hand, asking for too much before the meeting creates a different problem. A prospect filling in a detailed twelve-field form before a thirty-minute call starts to wonder whether the time investment is worth it. Some will complete it. Others will quietly decide it is too much effort and move on to a competitor whose booking process was easier.

The goal is to collect enough information upfront that you can prepare meaningfully, without the pre-meeting form feeling like a substitute for the meeting itself.

What to ask before a discovery call

A discovery call is a conversation. Its purpose is to understand whether there is a fit and what the right next step looks like. The information you need in advance is limited to what helps you prepare for that conversation — not what helps you do the job.

That is it. Four pieces of information are enough to prepare for a productive discovery call. You know who the prospect is, roughly what they are trying to do, and when they are hoping to do it. Everything else — budget, decision-making process, what they have tried before, specific requirements — emerges naturally in the conversation itself, where you can explore it with follow-up questions and respond in real time.

A one-line brief before the call also gives you something specific to reference in the opening moments of the meeting. "You mentioned you're looking to improve how leads come through your website — can you tell me a bit more about what that's looked like so far?" is a much stronger opening than starting from scratch.

What to ask before a site visit

A site visit has different requirements. Unlike a discovery call, which can proceed with minimal advance information, a site visit may require your team to arrive with equipment, materials, or specific preparation. The pre-visit information needs are shaped by logistics as much as by content.

This list is longer than the discovery call list, and appropriately so. Without the address and access information, the visit cannot happen. Without a sense of scale, you cannot allocate the right amount of time. Without the day-of contact number, a team member stuck outside a locked gate has no way to proceed.

What is not on this list: a detailed specification of the job, a breakdown of every element to be surveyed, or questions better answered by seeing the site in person. Those belong in the visit itself.

Questions that belong in the meeting, not the form

There is a category of questions that businesses often try to ask before the meeting but which are far better handled in person. These are diagnostic questions — ones where the answer will change depending on what the prospect says next, and where the conversation needs to go in multiple directions depending on the response.

Examples include: What specifically is not working with your current situation? What have you already tried? What is your budget? Who else is involved in making this decision? These questions require follow-up, clarification, and the ability to read the response. A form cannot do that. A conversation can.

Asking diagnostic questions in a pre-meeting form also raises an expectation problem. If a prospect writes a detailed answer about their budget in a form, and then the first question you ask in the meeting is "so what kind of budget are you working with?" — they notice. It signals that the form was not read, or that the process is not coordinated. Either way it damages trust at exactly the moment you are trying to build it.

The golden rule for pre-meeting information

A useful test for any question you are considering adding to a pre-meeting form: would the answer change what the team member does before the meeting, or would it only be useful once the meeting has started?

If the answer is the former — the team member would research something, bring different materials, or prepare a specific angle based on the response — it belongs in the form. If the answer would only be useful once the conversation is already underway, it belongs in the meeting.

Pre-meeting information is for preparation. The meeting is for discovery. Keeping these two purposes distinct produces better meetings, shorter forms, and a booking process that more prospects actually complete.

From the EveryCatch team

EveryCatch helps service businesses design pre-meeting information flows that prepare the team without creating friction for the prospect. The goal is always the same: shorter forms, better meetings, more bookings completed.