Prepare a short business brief, accurate service details, usable images, and one clear customer action. Separate what is ready from what needs help, then agree on who supplies content and approves the work.
Start with a one-page business brief
If you are looking for someone to build your business website, you do not need to arrive with the finished design. Start with the business name, contact details, actual service area, core offer, and the kind of customer you want to help. Explain what a visitor should do next: ask for a quote, request an appointment, buy a product, or call.
Colby Technologies uses the business goal to shape the website scope. “I need a professional website” is a starting point; “I need homeowners to see my completed projects and request an estimate” gives the project a clearer purpose. Include anything the site should not imply, such as services you do not provide or locations you cannot serve.
A brief you can complete today
We help [customer] with [service]. Customers usually ask [three questions]. Before contacting us, they need to see [evidence]. The next step is [action]. We will maintain [information] after launch.
Collect facts before polishing the wording
Make a short record for each main service: who it is for, what is included, what changes the scope, and what the customer needs to provide. Add the questions you answer repeatedly by phone. Rough but accurate notes are more useful than polished paragraphs that leave the offer unclear.
Google’s SEO Starter Guide recommends useful, well-organized content written for readers. For a website project, our practical recommendation is to supply the real information first and refine its presentation during the build. You do not need to invent a slogan for every section.
If you need writing help, say so before the proposal is finalized. Decide who will draft, check facts, and approve copy. The essential pages guide can help organize the material once the facts are collected.
Build a small, organized asset folder
Gather your logo, original photographs, approved testimonials, and relevant project examples. Keep full-quality originals rather than screenshots of social posts whenever possible. Name folders by project or service so the designer can understand what the images show.
- For each project, explain the work shown and your business’s role.
- Identify any images that should not be published.
- Confirm that the business has permission to use supplied material.
- Mark a preferred image without requiring it to fit every screen shape.
- List missing assets so photography or alternatives can be scoped.
A small selection with context is better than hundreds of unexplained files. If your only logo is a screenshot, our logo file guide explains what to look for.
List the systems the website must connect to
Write down where the domain is registered, where the current site is hosted, and which tools receive inquiries or bookings. Identify the account owner and whether access can be delegated. Do not put passwords into the content document; use the provider’s supported access-sharing process.
Include existing pages or links that must keep working. If you are replacing a website, keep its URL inventory available. If you need a booking tool, product catalog, or staff editor, describe the everyday task rather than simply requesting “an integration.” The developer needs to know what successful operation looks like.
Choose the reviewer and define ready-to-start
Assign one person to consolidate feedback. Several people can contribute, but contradictory instructions need a decision before they reach the developer. Mark items as ready, awaiting approval, or needing help. Agree on the minimum content required for the first version and which additions can follow.
A useful readiness check is whether someone unfamiliar with the business could explain its offer from your packet. If the answer is no, identify the missing fact. Do not delay a straightforward launch over optional decorative details, but do resolve unclear service information and the contact destination.
When you contact Colby Technologies, send the brief, a few representative images, and the customer action you want the site to support. We can then discuss the website scope and what preparation remains. You can ask for help assembling the content as part of that discussion.
Sources and further reading
Platform guidance checked September 27, 2026. Examples and worksheets are Colby Technologies recommendations; they are not measured client results.
Put the next improvement into practice.
Share your website and the problem you want to solve. Colby Technologies can help define a practical scope.