Custom Website Build Planning Guide
Write the customer task first
Before choosing colours or a page count, finish this sentence: “A customer should be able to use this website to…” The answer might be request a repair quote, book an appointment or buy a product. Pick a main task, then list the information someone needs before taking it.
A worked brief for a local maintenance business
The following is an illustrative brief, not a claim about a particular client: “We carry out general repairs, decorating and garden maintenance around Ashford. We want suitable homeowners and landlords to describe a job. We need the town or postcode, type of work, timing and a way to reply. We do not take online payment or confirm appointments through the form.”
That brief immediately rules out a checkout and an instant-booking promise. It also shows why a generic ‘Contact us’ form may not give the owner enough useful information.
Turn the brief into a page map
| Page | Customer question | Content needed |
|---|---|---|
| Home | Is this the right kind of business? | Clear service summary, coverage and enquiry route. |
| Services | Which service fits my job? | Choices, exclusions and links to useful detail. |
| Repairs | Do you handle this type of repair? | Examples, assessment process and what to send. |
| Decorating | What is included and how is it quoted? | Preparation, access, finish choices and scope assumptions. |
| Garden maintenance | Is this a one-off job or regular work? | Service options, coverage and availability information. |
| About | Who would I be dealing with? | Verified business information and permitted evidence. |
| Contact | How do I request help? | Short labelled form, phone option and explanation of the next step. |
This is one possible seven-page plan. A business with less distinct content may be better served by one well-organised page. A genuine multi-branch operation or a shop can need a different structure. The page count follows the information, not the other way around.
Collect the facts and permissions
Prepare the correct name, contact details, coverage, hours, services and any current registrations. Gather photographs you can publish and explain what each shows. A project example is more useful when it names the problem, the work and the result than when it simply says ‘another happy customer’. Do not invent a testimonial to fill a design slot.
Agree the limits of the first version
Write down what is included now and what can wait. For the example above, a photo-upload facility may be useful later, but it adds storage and handling requirements. Starting with a clear description field and a defined follow-up process can be proportionate. If customers need a booking system, identify the actual provider and its fees before promising integration.
Check the enquiry journey
Who receives the request? Is a copy stored? What does the visitor see on success? What happens if the notification email fails? Our EchoPM case study documents a real change from an email-app form to a saved website enquiry. It is a useful reminder that a completed form and a received request are separate things to verify.
Prepare for launch and ownership
Confirm domain access, hosting and email responsibilities. For a redesign, list existing URLs and decide which stay or need redirects. Review the preview on a phone and with a keyboard, then check the live links and form after publication. Agree who handles future changes and whether an editing interface is included.
Compare Lustre’s scopes and prices, read the project process, or use the Ashford guide to frame a local brief. You do not need polished marketing copy to make an initial enquiry; an accurate outline is enough to start planning.
Turn the findings into a useful website plan
Send the business details, current website and the problem you want to solve.
Get a website plan →