A strong website project does not start with colours, layouts, or page copy. It starts with understanding the business, the client’s goals, the target audience, and the search intent behind the website.
For the Willbrink website project, the process started with discovery. After the initial discussion, I sent the client a discovery questionnaire so I could understand the business properly before making design or SEO decisions.
The client completed the questionnaire and sent it back. I then used those answers to create a working website demo with AI, based on the client’s actual vision, business model, services, audience, and positioning.
This meant the client was not only reading a proposal or looking at static design ideas. He could interact with a working website demo, get a feel for how the final website could look, and then give feedback on the site itself.
That entire process, from discovery call to questionnaire, working demo, and client feedback, took less than 48 hours.
Why the discovery stage matters
The discovery stage gives structure to the project before any serious build work begins.
Instead of guessing what the client wants, I used the questionnaire to understand:
-
What the business does
-
Who the target audience is
-
What services need to be presented
-
What makes the company different
-
What tone and visual direction the client prefers
-
What outcomes the website needs to support
-
What the user journey should feel like
This helps avoid the usual back-and-forth that happens when a website project starts without enough clarity.
Because the client had already explained the business in detail, the demo could be shaped around real information instead of assumptions.
Using AI to move from discovery to demo faster
AI helped speed up the early website development process, but it did not replace strategy.
The value was not just in generating a quick demo. The value was in using the client’s discovery answers to create something practical that the client could actually respond to.
This gave the project a faster feedback loop:
-
The client explained the business through the questionnaire.
-
I used that information to generate a working website demo.
-
The client reviewed the demo like a real website.
-
The client gave feedback based on what he could see and experience.
-
That feedback became the foundation for the final WordPress build.
This process helped the client trust the direction quickly because he could see progress almost immediately.
Building trust in less than 48 hours
The speed and accuracy of the discovery process helped build confidence early.
Instead of asking the client to imagine the final website, I gave him something visible and usable. He could see how his ideas were being translated into a real website experience.
That reduced hesitation, uncertainty, and doubt.
It also made the payment decision easier because the client already understood what was being built. He had seen the direction, reviewed the demo, and given his input before the full WordPress build started.
This changed the dynamic of the project. The client was no longer unsure about the outcome. He was already involved in shaping it.
Turning client feedback into a better website plan
After the demo was reviewed, the client sent detailed feedback.
Instead of treating that feedback as scattered notes, I broke it down page by page and section by section. This made the project easier to manage and helped separate design changes from SEO and structure decisions.
The feedback included direction around:
-
Header and navigation changes
-
Logo size and slogan removal
-
Visual style and brand colours
-
Truck imagery
-
Homepage section order
-
Service page content
-
Partner logos
-
Footer layout
-
Contact details
-
Graphic ideas
This step matters because client feedback should not be ignored once the project moves into strategy. The client’s input is the first reference point.
However, if a stronger SEO or user experience approach is available, I make a clear note of it. That way, the client’s feedback is still respected, but the final website is improved where needed.
Planning SEO before writing copy
Once the feedback was organised, the next step was to plan the sitemap and keywords before writing the website copy.
This is important because SEO should not be added at the end of a project. If the sitemap is weak, the copy has to work harder, and Google receives unclear signals about what each page is meant to rank for.
For Willbrink, the client’s feedback showed that the company is not a general logistics business. The stronger positioning is around building, funding, managing, and measuring SME transport businesses through Enterprise and Supplier Development programmes.
That changes the SEO direction completely.
Instead of targeting broad searches like “logistics company” or “transport services”, the website should be structured around more specific search intent such as:
-
Enterprise and Supplier Development programme management
-
Owner-driver programme development
-
SME transport business management
-
SME funding and fund management
-
ESD impact reporting
-
Supplier development
-
Governance, compliance, and cashflow management
This helps attract the right audience: corporates, transformation teams, procurement teams, funders, and decision makers looking for a structured programme partner.
Why the sitemap comes before copy
The sitemap defines how the website will be understood by both users and search engines.
If every page has a clear purpose, the website becomes easier to navigate and easier to rank.
For this project, the sitemap needed to support both the client’s business message and Google search behaviour.
That means each page should have:
-
A clear topic
-
A clear keyword focus
-
A clear user intent
-
A clear role in the overall website journey
This prevents pages from competing with each other and helps each service area get its own search visibility.
For example:
-
The Services page can target broad ESD programme management intent.
-
The Owner-Driver Programme Development page can target programme design intent.
-
The SME Business Management page can target hands-on transport SME management.
-
The Funding page can target transport SME funding and fund management.
-
The Impact Reporting page can target reporting, evidence, and measurable outcomes.
This structure gives Google a clearer understanding of the website and gives visitors a more direct path to the information they need.
How this cuts the creation process in half
Because the discovery questionnaire, AI demo, and client feedback happened before the final build, the actual WordPress development process becomes much more focused.
The client already knows what the website direction looks like.
The client has already given feedback.
The sitemap is being planned with SEO before copy is written.
The design changes are already listed.
The target audience and business positioning are already understood.
This removes a large amount of uncertainty from the project. It also reduces stress for both the client and the developer because the project is no longer being built blindly.
Instead of spending time guessing, revising, and trying to uncover missing information later, I can focus on the work that really matters: building a website that is clear, searchable, conversion-focused, and aligned with the business.
How this benefits the final website
This process improves the website in several ways.
First, it improves accuracy. The website is based on real client input, not assumptions.
Second, it improves speed. The early demo gives the client something to react to quickly, which shortens the feedback cycle.
Third, it improves trust. The client can see progress early and understand that their vision is being taken seriously.
Fourth, it improves SEO. The sitemap and keywords are planned before the copy is written, which gives the site a stronger search foundation.
Fifth, it improves the final build. By the time development starts in WordPress, the project already has a clear direction, clear pages, clear content priorities, and clear client-approved feedback.
Why this process matters to employers
This project shows that my web design and development process is not only about building pages.
It starts with discovery, strategy, client communication, rapid prototyping, SEO planning, and structured implementation.
I use AI to speed up the process, but the goal is not to skip thinking. The goal is to get to clarity faster, reduce uncertainty, and give the client something practical to respond to.
The result is a better website process:
-
Faster discovery
-
Faster client buy-in
-
Clearer feedback
-
Stronger SEO planning
-
Less uncertainty
-
Better final execution
For me, a successful website starts before the first WordPress section is built. It starts with understanding the business deeply enough to create a website that users can understand, Google can read, and the client can trust.