A website project rarely fails because of the technology. It fails because no one wrote down what the site was supposed to achieve, because the validation process dragged on, or because the launch was treated as a mere formality. The following six steps are where costly decisions are made—and where a well-informed client can change the outcome.
1. Scoping: Defining the Site’s Objectives
Before any mockups are created, a single page of answers is enough to avoid months of wandering:
- Who should visit this site? A business buyer overseas, a local resident, and a test taker don’t expect the same thing.
- What should they do next? Call, fill out a form, buy, sign up, or visit in person. One goal per page.
- What search terms should the site be found for? The words your customer types, not the jargon of your industry.
- What already exists? Logo, text, photos, Google listing, analytics account, domain name.
This document is your safeguard. Anything not included here will either be forgotten or billed as an extra—and in either case, it will be too late to discuss it.
Red flag: A service provider who talks about technology before asking these questions is selling a tool, not a solution to your problem.
2. The site map: Decide on the pages before deciding on the design
The site map is the list of pages and their hierarchy. It’s the least glamorous yet most critical step: it determines the URLs—and thus the structure that search engines will index—and it reveals gaps in the content long before a single line has been drawn.
A common mistake is to cram everything onto the homepage. A page that covers everything doesn’t rank for anything. It’s better to have one page per actual topic: one service, one page; one frequently asked question, one page.
This is also the time to decide on language support. The decision to create a bilingual site is made here, not later—adding a second language to a structure that wasn’t designed for it costs several times more than planning for it from the start.
3. Content: The Real Bottleneck
In the vast majority of delayed projects, the delay stems from text and photos, not from development. The service provider waits for the service descriptions; the client waits until they have time to write them.
Two decisions can prevent this bottleneck:
- Who writes the content? If it’s you, set aside time slots right from the scoping phase. If it’s the service provider, it’s a line item on the quote—not a service provided as an afterthought.
- Which photos? Recognizable stock images undermine credibility. Your own offices, your teams, and your projects are better—even if they’re carefully photographed over the phone.
Plan the content for all the languages identified in Step 2. A half-finished English version signals to a foreign buyer that they weren’t part of the plan.
4. Design and Mockups: Approve in One Go
A mockup is approved based on three questions: Does the visitor understand what you do within five seconds? Is the expected action obvious? Does it work on a phone screen?
The rest—color nuances, font choices—deserve feedback, but not a third round of back-and-forth. Set the number of rounds of revisions included from the start. Without this limit, the feedback process drags on, the budget spirals out of control, and frustration sets in on both sides.
Insist on seeing the mobile version. A mockup presented only in full-screen format hides half the problems.
5. Acceptance Testing: Test Before Signing Off
Acceptance testing is the phase where you verify that the site does what was specified in Step 1. This is done using a checklist, not just a general impression:
- Does each form actually submit a message, and to the correct address?
- Does the site display correctly on your own phone, not just the service provider’s?
- Does each page have a distinct title and description?
- Is the security certificate (HTTPS) active on all pages?
- Are both languages fully implemented?
- Is the web analytics tool tracking visits?
One detail that can cost you dearly later on: ask that the analytics tool exclude your own connections and your admin panel. Without this, your numbers will mix your visits with the actual ones, and you’ll be flying blind for months.
6. Launch and Beyond: What Belongs to You
On launch day, make sure you walk away with:
- Access to the domain name, registered in your name. This is the most important item on this list: whoever owns the domain owns the address.
- Access to the hosting and site administration.
- Access to the web analytics account, as the owner.
- The site registered with webmaster tools, with its sitemap submitted.
- A brief training session on how to edit your content without having to call anyone.
Then comes what many people forget to plan for: maintenance. A website isn’t a piece of furniture—it’s software that’s constantly online. Security updates, backups, and bug fixes: either these are included in the contract, or they won’t happen—and within eighteen months, the site will become that dusty showcase that costs more credibility than it brings.
Key Takeaways
Projects that go smoothly share three common characteristics: objectives are written down before the first mockup, content is treated as a scheduled task rather than a minor detail, and there is no doubt about who owns access rights by the end.
The rest—the choice of technical framework, the content management system, the hosting provider—falls under the purview of the developer. That is precisely the subject of the following article: how to recognize someone who can do it right.
To set the stage for the challenges ahead, the article Why a Business Needs a Website discusses visibility and credibility. And if your project is already well-defined, a request for a quote describing your situation is all it takes to get the conversation started.