Before a web designer starts building pages, a small business should have a clear goal, an accurate description of its services, the essential business details, usable brand and photo assets, and one person responsible for decisions. You do not need to write every headline or choose every layout first. The useful preparation is knowing what is ready, what is missing, and who will supply it.
That distinction matters. A website project can move through design and development while still waiting on a service description, a photo permission, or a decision about what should happen when someone submits a form. A good handoff makes those dependencies visible before they become surprises.
Start with the customer decision, not a page count
Write one sentence describing what a visitor should be able to do after using the website. For a local service company, that might be: “A homeowner should understand our services, confirm that we serve their neighborhood, and request an estimate.” For a consultant, it might be: “A potential client should understand our approach and request a conversation.”
Then write down the three questions a prospective customer usually asks before reaching out. These are more useful than a vague instruction to “make it modern.” They help your designer organize the navigation, content, and next step around a real customer need.
If you are unsure whether you need a new site or improvements to an existing one, see our guide to choosing between a website redesign and a refresh. That decision should come before collecting materials for an unnecessary rebuild.
The website handoff: what to gather
Business facts and services
Provide the business name as it should appear publicly, the locations or areas served, preferred contact details, hours where relevant, and a plain-English list of services. For each important service, explain who needs it, what the work involves, and what the customer should do next. If pricing varies, say how estimates work rather than inventing a number for the website.
Do not worry about polished marketing copy yet. Accurate notes are a better starting point than impressive-sounding paragraphs that fail to explain the business.
Proof and visual materials
Gather the best available logo file, existing brand colors, authentic photos of your work or team, and any approved testimonials, reviews, credentials, or project examples. Note which materials you have permission to publish. A photo of completed work can be valuable, but it should not be used if the customer or photographer has not authorized that use.
Put the originals in a shared folder with sensible filenames. A designer can help decide what belongs on each page. Avoid sending only low-resolution screenshots of a logo or copying photographs from another website.
Features and the path after an inquiry
List the actions the site must support: a quote request, document upload, product purchase, newsletter signup, service inquiry, or something else. For each form, identify who receives the information and what should happen afterward. A form that looks good but sends inquiries to an unattended inbox is not a finished customer process.
Our website forms and customer intake service explains why the handoff after submission belongs in the design conversation, not just the launch checklist.
Existing accounts and technical dependencies
If you already have a website, identify who controls the domain registration, hosting, website administration, business email, analytics, and any booking or customer-management tools. You may not need to grant access immediately, but you should know who can authorize it when the project reaches that stage. Use secure invitations or a credential-sharing method agreed with your provider; do not email passwords around.
For a redesign, flag any important existing URLs, forms, search traffic, or integrations that must be preserved. A new design should not casually discard functioning parts of the current website.
A more useful readiness test than “Is everything finished?”
Make a simple three-column handoff sheet. For every important item, label it Ready, Needs an owner decision, or Needs provider help. Add a named owner and a realistic next date. This is a planning framework, not a claim that every project requires the same documents.
- Ready: The service list is accurate, contact information is confirmed, and approved photos are available.
- Needs an owner decision: Two partners disagree about which service should be featured first, or nobody has approved a testimonial.
- Needs provider help: The business has rough notes but needs copywriting, has no suitable photography, or needs help defining a form workflow.
Consider a hypothetical neighborhood contractor preparing a five-page website. The owner has a logo, service list, and photos, but has not decided whether estimates should go to the office manager or directly to the field supervisor. The designer can plan the page structure, but the inquiry workflow still needs a business decision. Labeling that item clearly is more useful than declaring the entire project “ready” or “not ready.”
Use the same sheet to agree which materials the business supplies and which the designer creates. Copywriting, photo sourcing, SEO planning, legal policies, and software integrations are not automatically included in every web-design proposal. Put the responsibility and any added cost in writing.
What can wait until the project is underway?
You do not need a final menu structure, exact button colors, fully polished page copy, or a list of plugins before the first planning conversation. Those decisions should follow the business goals, scope, and platform requirements. You also do not need to buy new software merely because a designer mentions a feature.
What should not wait is a clear decision-maker. Assign one person to consolidate feedback and approve content, with a backup if that person will be unavailable. Agree on a reasonable review window. Development hours and calendar time are different: even a modest build can take longer when approvals, photographs, or access arrive late. An honest schedule should identify those dependencies rather than promise a launch date before they are known.
A short handoff note you can copy
Send your designer a note in this format and fill in what you know:
Website goal: We want visitors to ______.
Primary customers: ______.
Top customer questions: ______.
Services and locations: ______.
Available assets: ______.
Must-have functions: ______.
Current site and accounts: ______.
Items still undecided: ______.
Person approving decisions: ______.
Target date and known constraints: ______.
Missing information is acceptable when it is visible. A provider can help you plan around an unknown; it is harder to plan around an assumption that nobody has checked.
The right next step
If you have a goal and a rough service list, you have enough to begin a useful discovery conversation. Gather the other materials as you clarify the scope, responsibilities, and review process. The point is not to turn a small business owner into a web designer. It is to give the project a sound foundation.
Grassroots helps small businesses connect website design with clear messaging, dependable forms, and practical digital systems. If you are preparing a new website or trying to get a stalled project moving, request a discovery conversation through our Talk page. We can start with what you already have and identify what still needs a decision.
Built in collaboration with ChatGPT.
