Commissioning a new website or web app can feel like a black box: you leave a brief, and several weeks later something appears. With a serious tech agency, it's the opposite – a structured collaboration where you know what's happening, when it's happening and why. This guide goes through the entire chain from the first conversation to ongoing operation, and what you as a customer should reasonably expect in each phase.
1. Discovery – understanding the problem before the code
The first phase is never about technology. It is about understandingwhythe project must be implemented. A competent agency asks more questions than it answers: Who are the users? What should they be able to do? What business goals should the site support – more leads, faster onboarding, less support pressure?
In practice, discovery consists of workshops, interviews and a review of the current situation. The result is usually a number of concrete deliveries:
Goals and KPIs– measurable success criteria, not vague ambitions.
Target groups and use cases- often in the form of personas or jobs-to-be-done.
Sitemap and content structure– which pages and flows are needed.
Technical and legal framework– requirements for performance, availability, GDPR and integrations.
What you as a customer should expect:to be interviewed properly, to receive challenging counter-questions and to leave the phase with a document that describes what will actually be built. If someone jumps directly to design or code without discovery, it is a warning signal.
2. Design – from wireframe to finished prototype
The design phase translates discovery into something visual. It almost always starts in low-res format:wireframesthat shows structure and hierarchy without getting stuck in colors and fonts. Here, ideas are tested cheaply, before anyone invests time in pixel-perfect design.
A design system is then built – components, color scale, typography and spacing – in a tool such as Figma. The point of a design system is that it is reusable: buttons, forms and cards are designed once and reused consistently, making both construction and future management cheaper.
Accessibility is built in – not on
A modern design process weaves in accessibility from the start. Since the European Accessibility Act began to be applied on 28 June 2025 – in Sweden through the Act (2023:254) on the accessibility of certain products and services – more and more private actors are covered by requirements for digital accessibility. The standard to design against isWCAG 2.2 level AAas well as the European standard EN 301 549. It is concretely about clear focus markings for keyboard navigation, sufficient click surfaces and good contrast – things that are dramatically cheaper to design in than to correct afterwards.
What you as a customer should expect:to see and like wireframes before finished design, and a clickable prototype you can feel before a single line of production code is written.
3. Development – the right technology for the right problem
Now it is being built. The choice of technology should be guided by the needs of the project, not by what happens to be trendy. Two modern frameworks dominate the discussion in 2026, and they solve different problems.
Astro – for content driven sites
For market sites, knowledge banks and blogs areAstroa natural choice. Astro's philosophy is to send as little JavaScript as possible to the browser - the page is delivered as static HTML and thus basically becomes fast. WithServer Islandsindividual components (a logged-in user's avatar, a shopping cart, personalized recommendations) can be dynamically rendered without weighing down the rest of the page, while the critical content is displayed directly.Content Layer-The API allows content to be fetched type-safely from any source: a headless CMS, a database, or an external API.
React – for interactive applications
When the project is about an actual application – dashboards, booking systems, tools with a highly interactive state – isReactoften right. React 19, which was released in December 2024 and has since received several point updates, made React Server Components stable along with Actions, the hookuseActionStateand the newuse- the API. This means that parts of the interface can be rendered on the server and that form logic becomes simpler and faster.
Good agencies work in short iterations (sprints), with version management in Git, code reviews (pull requests) and automated pipelines. You should have ongoing visibility – often via a deploy preview where you can click around the build as it develops.
What you as a customer should expect:a justification for the technology choice in plain text, regular reconciliations and access to a test environment – not a construction project behind lighted doors.
4. Content – what actually does the work
The most beautiful design is worthless without content that converts. The content phase often runs parallel to development and includes copy, images, video and structure. Decisions are also made hereCMS: should the editors be able to update pages themselves, and if so how easily?
Search engine optimization already belongs here – not as an afterthought. It is about semantic HTML structure (heading levels, alt texts), well-thought-out metadata, internal link structure and structured data. It is significantly more effective to build SEO into the content from the beginning than to try to screw it up after launch.
What you as a customer should expect:clarity around who is producing content (you, the agency or both), an editorial deadline and – if relevant – training in the CMS before launch.
5. Test and quality assurance
Before something reaches the public, it is methodically tested. A modern test phase comprises several layers:
Functional tests– do all flows, forms and integrations work as intended?
Responsiveness- does the site look and work well on mobile, tablet and desktop?
Performance– measured against Google's Core Web Vitals. The benchmarks in 2026 are LCP below 2.5 seconds, INP at maximum 200ms and CLS at maximum 0.1. INP is the most common pitfall, so interactivity is tested especially closely.
Availability– verified against WCAG 2.2 AA using both automated tools and manual keyboard and screen reader testing.
Security– basic overview of dependencies, permissions and data flows.
What you as a customer should expect:a period for self-review (UAT – user acceptance testing) where you can test and report, as well as a clear process for how bugs are prioritized and fixed before launch.
6. Launch – more than pressing a button
The launch itself is undramatic once the preparatory work is done. But it requires planning: DNS and domain pointing, SSL certificates, redirects from old URLs (so that SEO value is not lost), analysis and consent tools and a final review of performance and availability in the production environment.
Modern sites are often operated on edge-based platforms with a global CDN, which provides fast delivery regardless of the visitor's location. The launch should take place with arollback plan- if something can go wrong quickly, it should be just as quick to reverse.
What you as a customer should expect:a launch checklist, a specific launch window and confirmation that redirects, analysis and security certificates are in place.
7. Operation and management – the project does not end at launch
A website is a living product. After launch, operations take over: security updates of dependencies, uptime and performance monitoring, backup routines and ongoing content updates. Equally important is following up against the KPIs that were set in discovery – does the site convert, does the support pressure drop, is it visible in search?
Good management is proactive. Frameworks like React and Astro release new versions continuously, and new legal sources – such as the updated EN 301 549 v4.1.1 which is expected to reference WCAG 2.2 – mean that requirements change over time. An agency that respondsbeforesomething becoming a problem is worth more than one that only appears when something has already crashed.
What you as a customer should expect:a clear management agreement, defined response times and a named contact person – not a support queue out of thin air.
What affects scope and investment?
The size of a web project depends on several factors: number of page templates and unique flows, how much custom design versus ready-made components is needed, number of integrations (payment, CRM, CMS), availability and performance requirements, and how much content production is included. Two projects both called "new site" can therefore differ in scope in a profound way.
If you want to have a picture of the scope of your particular project, it is easiest to start from concrete needs. At ZORC you can usethe quote calculatorto get an estimate based on your choices, or takecontactdirectly, we help you structure the project from idea to launch - and further into stable operation.
