Someone searching for a new bathroom, a kitchen, a loft conversion or a roof repair is rarely looking for a directory of trades. They want one company to assess the property, price the work and see it through. That is harder to explain than a list of services, and it is easy to lose the moment an enquiry leaves the website and lands in an inbox. A firm that works this way, for homeowners, landlords, letting agents and commercial clients, has to plan the public site and the working day behind it together.
The published example is Ecobuild, a West Midlands building company. The customer contracts with Ecobuild. Ecobuild assesses the job, prepares the quotation and coordinates the employed staff or the subcontracted specialists who carry the work out. Jobs arrive with very different urgency, from a leaking roof to a planned extension. The website has to make that role obvious. The team still has to call, qualify the work, book a visit and follow up the quotation without rebuilding the picture from email.
What a building-market website is selling
In this market the offer is coordination. A page that only says the firm does kitchens and roofs leaves the customer to assume they must organise each trade themselves. The useful sentence is more specific. The company on the contract is the company that controls the quotation, and proposed changes are reviewed before extra work goes ahead.
That distinction belongs at the top of the site. On the Ecobuild homepage it is the first idea: the customer should not have to organise each trade. The page then shows the route from enquiry to assessment, quotation and coordinated delivery. A visitor who already knows the kind of work they need can go straight to a service. A visitor who is comparing firms can see who would be responsible if they proceed.
The same point has to survive the form. If the public pages say one company manages the project, and the email that follows reads like a lead passed to whoever is free, the website and the business are telling two stories. Web development for this sector starts with that sentence, then builds the pages and the enquiry around it.
Service pages and local pages, with an honest limit
People search for the job and the place. A single homepage cannot answer both. Ecobuild's public site gives each service its own page: bathrooms and wet rooms, kitchen fitting, renovations, extensions and loft conversions, and roofing and repairs. Area pages cover Birmingham, Solihull, Sutton Coldfield and Castle Bromwich, and the communities around them.
Coverage is confirmed after an enquiry is reviewed. The form does not treat every postcode in a listed town as accepted. That limit is deliberate. A local page that implies the van will come, when the team still has to check the address, creates a call that starts with a correction. The structure still gives search a clear URL for each service and each area, which is the useful part of local visibility. Titles, metadata and internal links belong in that structure from the start. Later search and marketing work can add pages. It cannot cheaply repair a site that was built as one long page with every town name in the footer.
Keep the first enquiry short
A project request on this site starts with the type of work and the property postcode, on the homepage or on a dedicated quote page. The full request is a three-step form with no obligation. It accepts residential, landlord, property-management and commercial jobs, because those are the clients the company already serves. A coordinator needs to know which kind of job has arrived before they dial.
A separate contact form handles general questions, so a supplier or a general enquiry does not have to pretend to be a bathroom quote. Office hours are shown as Monday to Friday, 08:00 to 17:00. WhatsApp is there for people who would rather start a conversation than complete a form. A chat message still has to become a job the team can see the next morning. The structured request is what makes that possible.
What the team opens after the form is sent
The thank-you page is where a brochure site stops. A building company still has to decide which call happens now, which quotation is late, and which visit is already in the diary. On the Ecobuild project that work sits in a coordinator workspace, on the same UK office hours, 08:00 to 17:00.
The overview shows tasks due, messages to check, qualified jobs waiting, appointments and new enquiries. The queue then splits into calls to make now, follow-ups, team confirmations and overdue quotations. Each enquiry keeps its status, its service, its postcode and its callback. Before a coordinator can mark it as qualified, they record the questions the call is for:
- Who owns the property
- Whether the decision-makers are on the call
- When the work is wanted
- The size of the job
- The visit address
Those answers are what make a site visit worth booking. Without them, the diary fills with journeys that cannot proceed. Appointments and a calendar show booked visits by the team assigned to them. Delivery teams are recorded with the trades they cover, and those contact details stay inside the workspace. They do not appear on the public pages. The customer contracted with the company, and the operational numbers stay with the people who schedule the work.
Selected public content can be changed from the same place. Coordinators can update the coordinated-delivery cards on the homepage, including the title, description, supporting line, sort order and photograph, and check a live preview before the change is published. The editing surface is small on purpose. It covers the part of the homepage the team is most likely to refresh as the work they want to show changes.
This is where the project becomes software for the people who run the day. The public pages are still the front. The queue, the qualification questions and the calendar are what keep the enquiry from falling back into a spreadsheet. The full account, including the service pages and the coordinator screens, is in the Ecobuild case study. The public site is at ecobuild.webworksrise.com.
How we approach a building-market project
The order of work is the same for a firm in the West Midlands and for a firm elsewhere in the UK. Start from the operating day, then design the pages around it.
- Write the public site in the order a customer meets the offer: who is responsible, which services exist, which areas are covered, and how to ask.
- Give each service and each real area its own page, and keep the form from promising coverage the team has not confirmed.
- Keep the first request short enough to finish, and specific enough that the first call is useful.
- Build the morning queue the coordinators will actually open, including the questions that must be answered before a job is treated as ready.
- Keep delivery-team contact details off the public site.
- Let the team change a small set of public cards without a code release, and show them a preview first.
The technical base follows that structure. The Ecobuild site uses Next.js and React, with a responsive front end, a custom operations workspace, enquiry and appointment management, homepage editing and technical SEO. The stack is there to support that journey.
Plan the website and the working day together
Ecobuild's website and coordinator workspace were built as one system. The company can explain its role, take a straightforward enquiry, and then manage the calls, visits and teams that follow. That is the pattern for this market. Web Works Rise is a UK-led team in Birmingham, with delivery from a development hub in Tunisia. The same team can shape the public explanation and the tools the coordinators use afterwards.
If the current site lists the trades and the calls still live in inboxes, the useful next step is a look at both. Talk to the team with the services you offer, the areas you cover, and how an enquiry is handled today. A new homepage that leaves the morning queue untouched has not dealt with the problem this market actually has.