Start with the last enquiry you received
Find a real question from someone who eventually bought from you. Remove their name and contact details. Read the conversation from the beginning. What did the person already know when they wrote to you? What did you have to explain before they could decide? A builder might have to explain whether the price includes plans, permits and finishing. A bookshop might have to check whether a particular edition is available for collection today. Those conversations call for different pages, even if both businesses describe the goal as getting more enquiries.
Write down what a successful visit would look like. For the builder, it could be a request for an estimate that includes a location, approximate floor area and a preferred start date. For the bookshop, it could be a reservation for a specific edition at a named shop. Give the studio the details you actually need to take the next step. If a field rarely changes your answer, consider asking for it later in the conversation.
Show how the work reaches a customer
Walk through one ordinary transaction from the first question to delivery. Say who checks the request, what they look up and what they send back. Include the small decisions people usually make from memory. A customer might choose an appointment online, but someone at reception still needs to check which room has the right equipment. A calendar showing open hours would tell the customer very little about which appointments can really be booked.
Bring one exception as well. What happens when the requested date is full, a product is reserved at another branch or the delivery address is outside the usual area? Describe the reply you would want the customer to receive. The studio can use that example to distinguish a simple contact form from a booking system that has to read availability and offer alternatives. That distinction belongs in the first estimate.
Bring material that can shape the design
Choose one service you would gladly sell tomorrow. Collect the price or the way you calculate it, a photograph you have permission to publish, a short description and the answer to a frequent question. A renovation company might bring two photographs of the same kitchen, a list of the work carried out and a note about what the owner supplied. A designer can build a useful project page around that material and see where a visitor will need a caption or a closer look.
For a catalogue, bring a small, deliberately varied sample. Include an ordinary item, an item with sizes or colours, something temporarily unavailable and an item with special delivery conditions. Use the actual field names from the file you maintain. Five well-chosen products can reveal a missing size chart or a difference between pack price and unit price that an empty spreadsheet would never show.
Explain what you like in a reference
Pick two or three pages you can discuss in detail. Point to a particular feature and describe what it lets the visitor do. You might like a floor plan that is legible on a phone, a gallery that keeps the project description nearby, or a comparison that lets customers choose between service packages. Saying why you like something gives the designer room to solve the same problem with your own material.
Open each example on your phone. Try the task with one hand and follow it through to the next screen. If a striking desktop layout hides the booking button on mobile, mention both observations. A screenshot with two short notes is often easier to use in a design conversation than a folder of twenty unlabelled links.
Map languages, branches and responsibilities
Make a list of the languages customers use and the people who can answer in each one. Decide where a request in Spanish should go and what should happen if the visitor changes language halfway through an enquiry. If prices, delivery areas or booking hours vary by location, identify who owns those details. Translating one page and maintaining local information for several branches are different jobs.
For a franchise, separate material shared across the network from details managed by a park or shop. The brand may own the description of a birthday package while the local park sets the timetable and closes bookings when places run out. Sketch what a local manager should be allowed to change. That decision affects the editing screen, the approval process and the information a visitor sees after choosing a location.
List the systems that already hold the information
For every connection you need, write one concrete sentence. For example, a sale at the till should reduce the quantity available for online collection at that branch. Identify the system that holds the stock figure, the direction in which the information travels and the person who notices a discrepancy. If you do not know the name of the product or whether it offers an integration, bring a screenshot with private details removed.
Ask the person who runs the process how often an update has to arrive. A nightly export might be enough for a wholesale price list. The last copy of a book reserved for collection is a different matter. Where a decision is still open, write down who can answer it and when they will be available. You can ask for a separately priced investigation if the connection is central to the project.
Decide what must work on opening day
Imagine the site goes live on Friday. List the things that would make you postpone the announcement. The contact number must reach the right person, a paid order must appear in the shop, and a branch manager must be able to correct tomorrow's hours. Put future ideas such as loyalty points or an extra language on a second list with a reason to revisit them. This gives the studio a launch target it can test and leaves you a record of good ideas for later.
Finish with a short handover note. Name the person who approves the design, the person who checks prices and the person who will edit the site after launch. If that is the same person, say so. Give them one real task to perform on the preview, such as replacing a project photo or changing a collection time. A useful brief ends with the owner being able to recognise a finished job.
Before sending the brief, ask a colleague to read it without the rest of the conversation. Have them point out anything they would need to ask you before estimating the work. If they cannot tell which branch gets an enquiry or what happens after someone clicks “reserve”, add that one missing detail. A few lines answering a real question are more useful than another page describing the company.