The website development process runs through seven clear stages: discovery and brief, sitemap and content plan, design, development, testing, launch, and post-launch monitoring. A simple brochure site moves through these stages in 2-4 weeks, while a corporate site takes 4-8 weeks; and the point where the process most often stalls is almost always the same one: waiting for the client to deliver text and image content.
1. Discovery and Brief: Where the Process Is Actually Built
In the first meeting, it is you, not the agency, who does most of the talking: who your target audience is, which service you want to highlight, 2-3 example sites you like, and who your competitors are. This conversation usually takes 45-60 minutes, but its output becomes the document the whole project is measured against: the brief.
One warning sign to watch for when choosing an agency: be wary of firms that hand you a fixed price at the proposal stage without asking a single question. A quote given without a real discovery process usually turns into extra charges once the project is underway. A good discovery conversation should turn into a clear scope document within 3-5 business days, one that spells out the number of pages, the features included, and how many rounds of revisions you get.
Four items must appear in the contract at this stage: a firm delivery date, the number of revision rounds included, a payment schedule (usually split 50% upfront and 50% on delivery), and a written guarantee that the source files, design files, and site admin access will be handed over to you once the project is complete. If these items are missing from the contract, you may end up facing surprise arrangements later, along the lines of 'the files stay with us, you just keep paying as if it were rent.'
2. Sitemap and Content Plan
At this stage the site map is drawn up: home, about us, services/products, testimonials, blog, contact - typically 6-10 pages in total. For every page, the team decides which text, which image, and which call-to-action (CTA) button will appear.
A specific set of deliverables is expected from the client here: logo files (vector format, .ai or .svg), a brand color guide if one exists, service or product descriptions, and team and reference photos. In our experience, roughly a third of projects stall at this exact stage, because the client wants to write the text themselves but can never find the time. To be realistic: once text delivery drags past a week, getting help from the agency's copywriter is the most practical way to shorten the overall timeline.
The sitemap decision is not just a visual layout choice, it is also an SEO decision: it settles which service gets its own dedicated page, which topic becomes a blog post, and how the URL structure is set up. Giving each service its own page, for example, instead of lumping everything onto a single 'services' page, produces stronger results for users searching for that specific service - but it also increases the number of pages, and with it the time needed for design and content.
3. Design Stage and Approval Rounds
Design typically proceeds by first presenting 1-2 alternative concepts for the home page, then adapting the approved concept to the remaining pages. A standard contract includes 2 rounds of approval; a third round and beyond are usually billed separately, since they fall outside the agreed scope.
The expected turnaround for client feedback is 3-5 business days. The longer this stretches - say, feedback spread over 2-3 weeks - the more the project timeline slips in direct proportion, since the agency's team has moved on to other projects and getting back in the queue can add a few extra days of delay. Giving feedback through a single point of contact, item by item and concretely - saying 'make the logo 1.5 times its current size in the header' instead of 'make the logo bigger' - speeds up every round.
4. Development (Coding) Stage
The approved design turns into a live website here. The choice of CMS is decisive at this stage: the answer to WordPress versus custom software directly determines how fast and flexible the site will be. Responsive coding, basic SEO settings (title tags, meta descriptions, image alt text) and form integrations are also completed during this step.
The client is usually quiet during this stage, and that is normal. A transparent agency, however, should share a staging link as development progresses, so you too can check midway through that things are heading in the right direction. Development typically takes 2-3 weeks for a corporate site, and can stretch to 4-6 weeks for sites with integrations such as an appointment system, multiple languages, or a custom form.
5. Testing and Quality Control
Checks that need to happen before launch: appearance testing across different browsers, mobile and tablet testing, confirming that every form actually lands in an inbox or CRM, a spelling and grammar sweep, a broken-link check, and measuring site speed. Skip this step, and the 'the form doesn't work' or 'it looks broken on my phone' feedback that follows after launch damages the brand's first impression.
Agency, Freelancer, or In-House Team? How the Process Changes
It is worth seeing how these three models shape the process differently. Working with a freelancer is usually more flexible and cheaper, but because everything depends on one person, that person getting sick, taking on another job, or simply slowing down on communication can stall the project for weeks. Working with an agency means a project manager tracks the process, and if one team member is out, someone else can pick it up; that assurance usually costs 20-30% more. Building an in-house team (hiring a full-time developer) only makes sense for companies with a large, constantly changing digital footprint; for a small or mid-sized business, the fixed monthly cost rarely pays for itself.
For a small neighborhood café, the freelancer model is usually enough, since the budget is limited and the scope is simple. For a manufacturing company with several branches, on the other hand, the agency model is the safer bet, because project management, coordinating multiple languages, and long-term maintenance needs are more than one person can reliably carry.
6. Launch Day
Domain routing, SSL certificate setup, registering the site with Google Search Console and Analytics, and, if there is an existing site, setting up 301 redirects from the old URLs to the new ones - these are the tasks for launch day. A small tip from experience: launch on a Tuesday or Wednesday rather than a Friday, so that if a DNS delay or technical issue turns up, the support team can address it before the weekend hits.
7. Post-Launch: The First 30 Days
Once a site goes live, it usually takes Google 1-2 weeks to index the pages; traffic will look low during this window, and that is normal. What should happen in the first 30 days: tracking core goals in Analytics (form submissions, phone clicks), producing the first performance report, and handling any small content fixes under the maintenance scope.
Where Does the Process Stall? 4 Common Mistakes
- Content is delivered late: This is the single biggest source of delay in projects; asking for text and images only after the design is finished, rather than during the brief stage, can double the overall timeline.
- Revision rounds are assumed to be unlimited: Once the number of rounds written into the contract is exceeded, both time and budget grow; that is why clarifying scope up front matters so much.
- Too many decision-makers get involved: When approval requires sign-off from 4-5 people, each round can take weeks instead of days; naming a single decision-maker is the most practical fix.
- Domain and hosting access is shared too late: When access credentials cannot be found on launch day, the site can sit finished but unpublished for days, even though design and development are done.
- Scope grows after the fact: Mid-project requests like 'let's also add this page' or 'let's include this feature too' change both the timeline and the budget if they weren't in the contract; it is healthier for both sides to agree upfront that a new request means extra time and extra cost.
What Documents Should You Prepare for a Website Project?
The process speeds up considerably if you already have the following on hand before the project starts:
- Logo files in vector format (.ai, .eps, or .svg); a PNG or JPG logo alone will blur at larger sizes and makes the designer's job harder.
- Brand colors and a font guide, if you have one; if not, the designer will build a palette together with you, which adds 3-5 days.
- Service or product descriptions; bullet-point notes are enough, they don't need to be full sentences - the agency's copywriter can polish them.
- Photos of your team, office, or production; real photographs, unlike stock images, build trust.
- 3-5 client names or case summaries you can use as references, if available.
How Often Should You Expect to Talk to the Agency During the Project?
A healthy project needs no more than a short weekly status update (an email or a 15-minute call) and a feedback conversation at each approval round. Expecting daily back-and-forth is not realistic; instead, planning conversations around specific milestones (sitemap approval, design approval, pre-test review) makes better use of both your time and the agency's. An agency with an assigned project manager will set this rhythm up for you; if you're working with a freelancer, you should propose it yourself from the start.
If you'd like a more concrete picture of how long the whole thing takes, take a look at our article on how long a website takes to build; if you're curious about the time and cost difference between a template and a custom design, our template vs. custom design comparison will be useful. For budget planning, we recommend our website pricing and cost article, and if you're building a corporate site, our what should a corporate website be like guide.
Frequently Asked Questions
What happens if I don't like the design?
If you still have revision rounds left under the contract, you can list what you don't like point by point and ask for a redesign. If the concept changes direction entirely - moving from a modern look to a classic one, for example - this is usually counted as an extra round and billed accordingly; that's why being specific about what you dislike at the first concept approval saves you from surprises in later rounds.
Can the agency ask for extra money partway through the project?
No, not if the scope was clearly written into the contract. But if you request a new page, a new feature, or an extra revision round midway through the project, that will carry an additional charge. A good agency puts this extra request in writing and prices it before doing the work, rather than surprising you with an invoice later.
Who should own the domain and hosting?
It's best for the domain and hosting accounts to be registered in your name, paid with your own payment method. If you let the agency register the domain under its own account, you can run into access problems later if you want to switch agencies; this is one of the most frustrating disputes we see in practice.
Is maintenance mandatory once the site is live?
It's not mandatory, but it's recommended. If you're using a CMS like WordPress, security updates, backups, and plugin compatibility all need regular attention; without a monthly maintenance arrangement, your site can fall out of date or develop security holes over time.
What should you consider when setting the launch date?
If you want the launch tied to an event, campaign, or the start of a season, say so at the very beginning of the project; the agency will build the development and testing schedule around that date. Moving the launch date up mid-project usually means cutting the testing phase short, which raises the risk of small errors surfacing after launch.
At Welda, we run these seven stages of web design and development projects on a clear timeline, and we tell you upfront what we need from you at every step. To talk about how long your project will take and where to start, you can request a free initial consultation on our contact page.