Back to the blog

First Website Meeting: Turn Initial Interest into a Clear Brief

Prepare your first website meeting with a local business: useful questions, a one-page brief, a fictional example and a recap before quoting.

Website project preparation questions in a notebook beside a laptop

A useful first meeting about a business website should produce three decisions: what visitors need to be able to do, what the initial version will include, and what you still need to know before quoting. You do not need to present every skill you have or ask the client to choose a technology straight away. You need to be able to write a short brief that your contact recognises as their project.

This guide is for a freelancer or small agency that has just received a positive response from a local business. The contact has agreed to a conversation, but may not have set a budget, prepared any copy or decided to hire you. The method below begins after that initial interest and stops before the quotation. Its central tool is a one-page decision sheet, accompanied by an entirely fictional example and a reusable meeting recap.

Prepare a working hypothesis, not a final diagnosis

Before the conversation, reread the message the prospect answered. Agreeing to receive a list of examples does not mean they want to buy a website. If they have asked for a price, start with that question. The meeting should continue their request, not replace it with your sales script.

Look at the useful public information: the business activity, service area, website shown, contact method and services described. A Google listing with no website displayed does not establish that the business has no website. Record the exact observation and its date, then let the owner correct it. Do not turn an incomplete page into a claim about their revenue.

Prepare just one working hypothesis: “Visitors seem to be looking mainly for your services and how to contact you. Is that the issue you want to address?” Add two open questions rather than a fifteen-slide presentation. Local research with SprintLead belongs upstream of this conversation; it does not replace the prospect’s own answers about their priorities.

If you still need to prepare your first message, see the website outreach email templates. In this guide, the contact has already agreed to continue the conversation.

Open the conversation by stating its intended outcome

Suggest a simple framework: “I suggest we look at what your customers need, separate the essentials from the optional extras, and see what we would need to clarify before a quotation. Does that work for you?” This opening gives the prospect a chance to redirect the conversation.

Then check whether they really have time available. If the person is being interrupted in the shop, it is better to arrange another time than to work through a series of questions in front of customers. A suggested duration is a planning choice, not a universal sales rule. Above all, leave enough time to summarise and agree on the next step.

Ask why the subject has come up now. An approaching opening date, misunderstood business hours and enquiries arriving in the wrong place call for different responses. “We need to look more professional” is still too vague: ask what happens today and what the person would like to change.

Finally, explain that you are taking a few notes so you can send a recap. This method does not require any recording. If you want to record a conversation, handle the applicable permissions and obligations separately rather than doing it implicitly.

Start with a situation the visitor actually encounters

The word “visibility” can conceal several different needs. Ask the owner to describe a recent enquiry: how the person found them, what they wanted to know and what needed explaining. You are looking for a concrete situation, not a detailed demographic profile.

Three questions are enough to begin: “Who would you like this website to help?”, “What information do they need before contacting you?” and “What should they be able to do next?” If the answer involves several audiences, choose the one that will guide the initial version. A customer checking a service does not follow the same path as a partner looking for a company presentation.

Rephrase the answer using an observable action: check the repairs offered, confirm a service area or request a callback. Avoid turning a future number of sales into a promise attached to your service. A website can make a journey easier; it does not control local demand or the business’s ability to handle enquiries.

This priority may lead to a shorter website structure than originally expected. It may also reveal that something else is more urgent than a new website. In either case, discovery has helped make a decision rather than merely supplying material for a sales pitch.

Three people discuss a project around a laptop and take notes

Turn each request into a scope decision

When a prospect asks for “booking”, clarify what they mean. Do they want a button linking to an existing service, an enquiry form or a calendar that automatically confirms a slot? These options involve different work. Do not choose a complex solution for them simply because the word appears in their sentence.

For each request, record three things: the action expected from the visitor, the person who will handle it and what should happen next. A callback request, for example, needs a recipient, useful information and a way to organise the response. If nobody can handle it, adding a form does not solve the problem.

Sort requests into three categories: necessary for the initial version, an option to quote separately, or something to investigate later. An exclusion needs to be as explicit as an inclusion. Saying “business website” is not enough to exclude online payments in a client’s mind.

The France Num guide to a website specification, consulted on 12 November 2026, highlights the value of documenting objectives and scope. The sheet proposed here supports an initial conversation; it is not a complete technical specification.

Identify what the client will need to provide

A project can seem simple until somebody mentions content. Ask what actually exists: a service list, usable photographs, a logo, contact details and approved copy. “We have some photos” needs to become a verifiable next step: who will gather them, within what anticipated timeframe, and who will confirm that they can be used?

Do not ask for any passwords during this first meeting. You can record the existence of a domain name, hosting account or booking tool and identify who is responsible for it. Access checks can happen in an appropriate setting if the project moves forward.

Distinguish supplied content from material you will have to produce. Reorganising text the client sends is not the same service as conducting an interview, writing every page and sourcing images. If the client expects this help, put it in the scope rather than allowing it to become an unstated task.

A launch date also depends on those contributions. Ask whether there is a genuine external deadline and why it matters. You can propose a schedule after examining the work and your availability, without promising immediate delivery simply to keep the prospect interested.

Discuss the budget without turning it into a test

Treat budget as a design constraint: “Have you already set aside an amount, or would you prefer to understand the options before deciding?” Either answer is useful. The absence of a number proves neither a lack of seriousness nor an unlimited ability to pay.

If there is a budget, clarify what it needs to cover. Initial development, content, third-party services and possible ongoing maintenance are separate subjects. Do not invent a recurring cost for a solution that has not yet been chosen. Instead, identify the items still to check and who would pay for them.

When the budget does not match the intended scope, propose a decision: reduce the initial version, defer some requests or do not proceed. Avoid promising the same outcome with less work without explaining what would change.

Also ask who needs to approve the proposal. The owner in the meeting may want to discuss it with a business partner. Record that step and the information needed to make the decision. Do not treat an expression of interest during the call as an order, and do not manufacture urgency to speed up a signature.

The one-page decision sheet to complete

Use this template during the conversation, then tidy your notes before sending them. One sentence per field is enough to start with. Mark unknowns instead of answering on the client’s behalf.

FieldDecision or question to record
NeedCurrent situation and desired change, expressed by the client
Priority visitorPerson and situation the initial version will address
Main actionWhat the visitor should be able to do
Initial scopePages or blocks and the expected functionality
ExclusionsRequests not included, separate options and deferred subjects
ContentExisting materials, missing items and who is responsible for each contribution
ApprovalPerson reviewing, person deciding and any other participant
BudgetStated amount or open question, and items still to estimate
Next stepAction, owner and agreed date if there is one

Give each line a status: confirmed during the conversation, an assumption to validate, or missing information. This prevents a supplier’s suggestion from quietly becoming a client requirement.

Before finishing, reread the three most important lines: main action, scope and exclusions. If the client corrects them, update the sheet immediately. A completed table that the client does not understand is not a usable brief.

A person organizes project notes beside a laptop

Fictional example: a shoe repair shop explaining its services

Imagine a fictional shoe repair shop called Atelier du Passage. No real outcome or SprintLead customer is described here. The owner agrees to a conversation because she regularly receives questions about the repairs she offers. Initially, she mentions a website with “booking and a shop”, without having distinguished those needs yet.

While discussing a recent enquiry, she explains that customers generally need to show the item before she can determine what work is possible. The chosen priority is therefore to help local residents understand the services and prepare for a visit. It is not to sell a repair automatically when the work involved is still unknown.

The sheet records an initial version presenting the main services, opening hours, address and a way to ask a question. Automatic booking and online sales are excluded from this initial scope. They are not declared useless: they would require a different examination of how the workshop operates.

The owner will provide the opening hours and check the descriptions. The freelancer still needs to clarify the copywriting work and the use of photographs. As no budget has been set, the freelancer will propose a priced scope after receiving these elements. The next step is approval of the summary, not starting work on the website.

Adjust the next step when the budget is low or the request expands

In the same fictional example, suppose the stated budget does not cover the whole project. One option is to explore an initial page focused on services, practical information and contact. But a single page is not automatically cheaper: the content work, requirements and integrations must still be considered. Propose a concrete reduction, not a reassuring label.

If the owner then adds accessory sales with delivery, separate that request from the initial brief. Ask which products, how orders would be organised and who would handle follow-up. You do not have to design the entire shop for free during this meeting. You can suggest a second scoping exercise or explain that this work falls outside the services you provide.

Another possible outcome is not producing a quotation immediately. For instance, nobody may know who can authorise use of the existing domain. Record the blocker and the person responsible for checking it. A project paused for an explicit reason is still better defined than a proposal full of invisible assumptions.

Send a recap that asks for a specific response

The recap should be shorter than your notes and separate agreed points from questions. Here is wording for the fictional example:

Hello,

>

If I have understood correctly, the website should mainly help local residents understand your repair services and prepare for a visit to the workshop.

>

We have identified an initial version covering services, practical information and a way to contact you. Automatic booking and online sales are not part of this initial scope.

>

You still need to confirm the service descriptions and which photos can be used. I need to clarify the copywriting work and the corresponding quotation.

>

Does this summary reflect what you need, or would you like to correct anything before I prepare the proposal?

If a date has been agreed, add it with the corresponding action. Otherwise, do not invent a deadline. The response you want is a correction or confirmation of the need, not a premature signature.

Once the proposal is agreed and the work has actually been ordered, the client project kickoff file can take over. Do not confuse that post-signature work with the first meeting: you do not yet need to organise production or request every account access.

Frequently asked questions

Should you send a questionnaire before the first meeting?

A short message is usually enough to ask about the project’s purpose, the existing website address if there is one, and who else should be involved. Save the detailed questions for the conversation. Requiring a long form before understanding the need can ask the prospect to make a disproportionate effort.

Can you give a price during this first conversation?

You can explain how you price work or provide a conditional indication if your service is sufficiently defined. Do not present an amount as firm when you still need to understand the content, booking requirements, languages or responsibilities. Write down the assumptions accompanying any estimate.

What if the prospect only wants to know the price?

Answer their question directly, then explain the few pieces of information that genuinely affect the price. You can offer a clearly described standard scope if you have one. There is no need to impose a lengthy discovery process for an already defined service; equally, do not pretend that a vague request is ready to quote.

Does the brief replace the quotation?

No. It helps define the scope and records what still needs clarification. The quotation and contractual documents must then specify the services, terms, responsibilities and any qualifications. Agreement with a meeting recap does not authorise you to start work that has not been ordered.

The right outcome from an initial conversation is not agreement at any cost. It is a project clear enough to propose a next step, or a specific reason not to proceed. Prepare your sheet before the meeting, fill it in using the client’s words, and ask them to confirm the choices and outstanding questions. You can then price a defined scope rather than an impression.