Building a website moves through clear, predictable stages: brief and analysis, design, development, content and basic SEO, testing, launch and maintenance. Each stage has a concrete result and a moment where you, the client, hand something over or approve something. Once you understand the stages, you see exactly what you're paying for and why a serious site isn't "done in an evening." Below is how a real project runs, from the first request to the first visitor.

1. Brief and analysis: what we want to achieve

It all starts with a conversation, not with Photoshop. We define the site's goal (sales, quote requests, bookings), who the audience is and what page structure makes sense. The result of this stage is a clear sitemap and a feature list — essentially, what we build and why. Here you approve the direction before a single line of code is written. How to prepare the information from your side is covered separately in "How to Write a Website Brief," so I won't repeat it here.

What you provide now: details about your business, examples of sites you like and your real differentiator. The more specific you are, the faster this stage goes.

2. Design and prototype: how it will look

Based on the structure, we first do the UX (where each element sits and why), then the UI (how it actually looks). Usually you see the homepage mockup first, approve it or request changes, and only then we continue with the rest. Approving the design is a key moment: changes are cheap now, on the mockup, and expensive later, in code.

Your role here: timely feedback and clear decisions. "More modern" doesn't help; "bigger logo and a red button" does.

3. Development: the site comes to life

Now the mockups become a real site that works in the browser. This includes:

  • Front-end — what the visitor sees, responsive on phone, tablet and desktop.
  • Back-end — the logic behind the scenes: forms, integrations, databases where needed.
  • CMS / admin panel — so you can edit texts and images yourself, without a developer.

During this stage you're relatively free; it's the perfect time to prepare the final texts and photos for the next step.

4. Content and basic SEO

A site without good content is an empty storefront. We add the texts, optimized images and basic SEO settings: title and meta description on every page, a correct heading structure, speed and social-network tags. What you provide matters enormously here: real texts, quality photos, a logo in a usable format. If there's no content, the project either stalls or we write it — but that has to be decided early, not on launch day.

5. Testing: catching problems before customers do

Before launch we check the site as a real user, not just as developers. We test on multiple devices and browsers, measure speed, submit test forms and check every link and button. The goal is simple: we find the errors, not your first customer. Your role: a final walk through the site with fresh eyes and confirmation that contact details and offers are correct.

6. Launch: the site goes public

We connect the domain and hosting, move the site to the live version, activate the SSL certificate, connect Google Analytics and Search Console and submit the site to Google for indexing. The exact pre-launch list is detailed in "Website Launch Checklist," so I only mention it here as a step. You give us access to the domain and relevant accounts; the rest is our job.

7. Maintenance and growth after launch

A website isn't a "once and done" job. After launch come updates, backups, security, small tweaks and, ideally, growth driven by data: which pages convert, what people search for, what needs improving. Here you enter a long-term relationship, not a one-off transaction. A site left untouched for months quietly falls behind: plugins break, copy goes stale, speed drops. Regular maintenance costs less than an emergency fix after a hack or a big rebuild.

The most expensive mistake I see in Moldova is rushing: "just make me something quick, like my competitors." Without a brief and analysis it always ends in rework — wrong structure, useless pages, a pretty site that doesn't sell. An hour of analysis at the start saves days of work at the end. That's why the riskiest way to save money is cutting that very first step: it's the cheapest one, yet it decides everything else.

Honestly about timelines: a landing page usually takes a few days, a business card site about a week, an online store one to two weeks, and complex projects run for weeks or months. These are reference points, not guarantees: the real timeline depends on the type of site and, very much, on how fast you supply content and feedback. A good process doesn't promise "fast at any cost" — it promises predictability, with no surprises.

At shadowforge we run every project through exactly these stages, with a fixed price and timeline, so you know from the start who does what and when. If you need a website for your business, message us and we'll propose a clear stage-by-stage plan.