How to Build a Company Website: The 7 Real Phases

Building a company website doesn't mean opening an editor and starting to put pages together. It's a project that goes through seven precise phases, from analysing objectives to management after launch, and each phase produces something the next one needs. We've been working on company website projects for several years now, and the point is always the same: when a website doesn't work, the problem is almost never the last phase. It's a phase that was skipped at the start, when it seemed like it could be done quickly.

In this guide we look at what really happens in each of the seven phases, what the company needs to prepare, roughly how long each one takes and which steps tend to push back deadlines. At the end you'll find a summary table with timings and a preparation checklist to use even before you ask for your first quote. If instead you're looking for the overall picture of the project, costs included, the starting point is our guide to creating professional websites for businesses.

Phase 1. Analysis and objectives: what the website needs to do

The project starts well before the design. In the first phase, the focus is on who the company is, who it's aimed at, what concrete results the website needs to produce and which competitors it's up against. "Concrete results" means numbers and actions: phone calls, quote requests, appointments, job applications. A website created without a stated objective is judged only on its looks, which is why so many redesigns end up changing the colour of the buttons rather than the number of enquiries received.

This phase also gathers the real constraints: who will update the website, how often, which existing systems will need to interact with it, which languages are needed. This information shapes everything else and costs very little to define now, since it's all still on paper. We've gone into more depth on the reasoning behind objectives in the article on what a website that brings in customers should look like.

What we need from you: objectives, a list of services or products, names of competitors, a point of contact who can make decisions. Approximate duration: 1-2 weeks. Outcome of this phase: a shared and approved planning document.

Phase 2. Architecture and page map

Once the objectives are defined, the structure is designed: which pages exist, how they're linked to each other, where the information visitors are looking for can be found and at which point in the journey they're asked to take action. This phase determines whether the website will be easy to use and easy to find, because the way pages are organised is also how Google understands what the company does.

This is also where the naming of pages and addresses is decided, duplicate pages covering the same topic are avoided, and it's decided which content deserves a dedicated page and which doesn't. These are choices that affect rankings for years to come and need to be made before the copy is written, not after. If you want to understand the link between structure and visibility, you can read the guide to SEO for SMEs.

What we need from you: confirmation of the services to highlight and the areas to keep separate. Approximate duration: 1 week. Outcome of this phase: the site map and the layout of each page type.

Phase 3. Content: copy, photos and materials

This is the most underestimated phase and, in practice, the one that most often extends the timeline. You need copy written for the web, real photos of the company, service descriptions, company details, and any videos and documents. This isn't material you can improvise the day before launch: the copy needs to answer the questions people are searching for, the photos need to be high quality, and the information needs to be final, not provisional.

The reason this phase so often holds up projects is simple: it depends on the company, not on whoever is building the website. Whoever does the work can only lay out what they've been given. Preparing the materials in advance, or having the copy written by someone who writes for the web, is the most effective way to shorten the overall timeline. If you're also thinking about how to keep the website updated afterwards, the article on content marketing for SMEs is worth a read.

What we need from you: final copy or a discussion with whoever writes it, photos, a high-quality logo, price lists and documents. Approximate duration: 2-4 weeks, often in parallel with the next phase. Outcome of this phase: approved content, ready to be laid out.

KeideaCMS

Want to know where your current website stands before rebuilding it?

Find out how we work →Request a free analysis

Phase 4. Graphic design and prototype

Only at this point is the look of the site designed, starting from the company's identity and the already approved structure. The main pages are planned, along with behaviour on phone and tablet, the hierarchy of texts and the placement of calls to action. Working on a navigable prototype, rather than static images, makes it possible to spot right away if a path is awkward, while fixing it still costs little.

The guiding principle to stick to at this stage is that design must serve the goal, not just look good. Elaborate graphics that slow down loading or hide the phone number are a problem, not a merit. The visual decisions made here have a direct impact on the performance measured during the testing phase.

What we need from you: visual identity materials, one focused round of feedback instead of corrections in instalments. Estimated duration: 2-3 weeks. Outcome of this phase: the approved prototype of the main pages.

Phase 5. Development and construction of the site

This is the phase in which the project becomes a real site: page templates are built, the approved content is laid out, contact forms are connected, the areas manageable by the company are configured, and the necessary tools are integrated, from analytics to the appointment calendar and, if needed, the catalogue. This is also where it's decided how easy it will be to update the site without calling a technician every time.

It should be stated clearly that a corporate presentation website and an online shop are two different projects: the latter involves a catalogue, cart, payments and shipping, with longer timelines and higher costs. If your goal is to sell directly online, the right path is the one described on the ecommerce development page. To get an idea of the costs of a corporate website instead, the analysis on how much a corporate website costs is useful.

What we need from you: access to the domain and existing services, feedback on the page drafts. Estimated duration: 2-4 weeks. Outcome of this phase: the complete site in a staging environment.

Phase 6. Testing, technical SEO and pre-launch checks

Before going live, the site must be put to the test. We check how it renders on different phones and browsers, the actual loading speed, the functioning of contact forms, internal links, the correct handling of personal data, and the texts on every page. This is also when we check the parameters used to measure the loading experience, the Core Web Vitals, which remain a concrete benchmark even in 2026: we explained them in the Core Web Vitals guide.

If the site is replacing an existing one, this phase includes the most delicate step of the entire project: preserving the ranking already earned. The old addresses must be mapped, redirects set up to the new pages, and content that brings in visits preserved. This is work that must be prepared before launch, not fixed afterwards, and we described it step by step in the guide on how to migrate a site without losing ranking.

What we need from you: one final read-through of the texts and verification of the contact details. Estimated duration: 1-2 weeks. Outcome of this phase: testing passed and the redirect plan ready.

Phase 7. Publication and management after launch

Publication is a technical step that takes just a few hours, but it opens the longest phase of all, because it never really ends. In the following days we check that the pages are being indexed, observe speed under real traffic, check the requests coming in through the forms, and fix the details that only emerge from daily use. Then maintenance begins: updates, verified backups, monitored security, growing content.

The point to clarify before signing, not after, is who will take care of this and with what response times. A site left to itself slows down, accumulates errors and slips in search results without anyone noticing until enquiries start to drop. We've written two practical guides on this: one on managed security for a website and one on periodic checks to carry out on a website. The European framework on data processing, from the GDPR to the NIS2 directive on cybersecurity, has turned these safeguards into a matter of routine management rather than an optional add-on.

What we need from you: the decision on who will manage the site and which content to update. Estimated duration: 1 week for the start-up, then ongoing. Outcome of this phase: the site online, monitored and maintained.

The 7 phases at a glance: timeframes and roles

This table summarises the complete journey. The timeframes are orders of magnitude that recur in corporate presentation website projects, not contractual commitments: they change depending on the number of pages, the functions required and, above all, the speed of feedback.

Adding up the phases, and considering that content and design often proceed in parallel, a well-organized company website project generally falls between two and four months from kickoff to launch. When someone promises the same result in a few days, they are almost always skipping analysis, content and testing.

What really causes delays

In most cases, delays don't come from the technical side. These are the most frequent causes, in order of occurrence:

• Content arriving in bits and pieces. Text and photos delivered a little at a time force layouts that were already finished to be redone.

• Feedback given in installments. Corrections sent one day at a time take up far more hours than a single, organized round of revisions.

• Decisions without a single point of contact. When three people approve different things, the project stalls while waiting for the company to decide internally.

• Changing goals mid-course. Adding a members' area or a catalog halfway through development means going back to phase two.

• Missing access credentials. Domain, email or analytics credentials that can't be found can delay the launch by weeks.

Almost all of these causes can be prevented at the quoting stage, by clarifying who does what and by when. We've gathered the right questions to ask before signing in the article on what to ask before signing a website quote. If instead you're starting from an existing site, the process and the signs to evaluate are described in the guide on when and how to redo your company website.

The preparation checklist

These are the points to have in order even before asking for the first quote. The more items you can check off, the faster and more predictable the project will be.

• I have written down in concrete terms what the website needs to achieve: calls, inquiries, appointments.

• I have designated a single point of contact who can respond and approve.

• I have the complete list of services or products to present, with priorities.

• I have the logo in high quality and real photos of the company, not just stock images.

• I have gathered the existing text that can be reused and I know who will write the new copy.

• I have retrieved access to the domain, email and analytics of the current site.

• I know who will update the site after launch and how often.

• I have clarified whether additional languages, a members' area or links to management software are needed.

• I have checked which pages of the current site bring in traffic and need to be preserved.

• I have agreed on realistic feedback turnaround times on my part, not just the supplier's.

How the phases change with a managed platform

Looking back at the process, you'll notice that the phases depending on the company are the first three, while the more technical ones, from development to maintenance, are those a business owner has neither the time nor the obligation to get involved in. This is where a proprietary platform managed under a subscription simplifies the project: with KeideaCMS the site runs on dedicated servers and already includes performance, security and updates handled by a team, with no plugins to install or modules to keep in order. The seventh phase, the one that never ends, stops being a problem you have to solve over and over again.

It's worth being precise about this, because it's often misunderstood: with a managed platform, the site is hosted and maintained on the servers of whoever manages it. The company remains the owner of the domain, content and data, which are exported if it decides to move elsewhere in the future, while the platform code remains the property of its developer. In exchange for the fee, you're not buying software to maintain on your own, but service continuity and predictable costs.

If you're comparing this approach with a site built on popular platforms, you'll find a point-by-point comparison on the comparison page, while to understand what's included and get an idea of costs, you can check out our plans.

In summary

A corporate website gets off to a good start when the project follows an order: first you understand what it needs to achieve, then you build the structure, prepare the content, design, develop, test and finally publish and manage it. The phases that seem like they can be postponed, analysis, content and testing, are exactly the ones that determine whether the site will bring in leads. The real timeframe for a serious project is measured in months, not days, and the most important variable isn't technology: it's how quickly the company provides materials and feedback.