Skip to content
HomeServicesAboutPricingArticlesContactPerformance test

Web Strategy

How building a website works

From the first call and price proposal to design, development and launch: how a website project works at Developly.

Kevin A. Sommerstein3 min read

How we take your idea from concept to launch

A good website rarely starts with code. It starts with questions: what should the site accomplish, who is going to use it, and what happens after launch? Here we walk through how we take a project from idea to finished website, and why we build in Next.js and Strapi.

Key factsJuly 2026
Step 1
Planning and needs
Step 2
Development in Next.js
Step 3
Content in Strapi
Step 4
Testing and quality assurance
Step 5
Launch and ongoing improvement

Foundational planning

Every project starts with a conversation. We go through what the website should accomplish, who the visitors are, and which features are actually needed. This is where the priorities get set, and it is usually where a project succeeds or fails. A good-looking site that solves the wrong problem helps no one.

Development with Next.js

The development itself happens in Next.js, a framework built on React. It produces fast pages that search engines have an easy time reading, a solid base for SEO from day one. We build the structure first: pages, components, and core logic. Then we let the framework do what it does best, like fetching data efficiently and only loading the code needed for the page the visitor is actually on.

Content management with Strapi

The content lives in Strapi, a standalone content system. That is where the text and images sit, separate from the code. We set up the structure during development, and after launch you are the one in control of the content: change a text or swap an image whenever you want, without going through us.

Testing and quality assurance

Before anything goes live, we test it. Unit tests check that each part works on its own, integration tests that the parts work together. Then we go through the site the way a visitor would: filling in the forms, clicking around on a phone, and looking for anything that feels off.

Launch and iterative improvement

Deployment runs through automated pipelines, so every update goes out in the same controlled way as the first. After launch we follow how the site performs and how it gets used, and adjust from there. Most websites gain more from ten small improvements after launch than from an extra month before it.

In short

The process is the same regardless of project size: understand the need, build in Next.js, put the content in Strapi, test, and launch. What varies is the content and the level of ambition, not the method. That is exactly why we can promise clear steps and a predictable path to launch.

Want to know more about how we build websites, or see what a project costs? Take a look at our pricing, or get in touch and we’ll take your idea forward together.

Frequently asked questions

It depends on the scope. A small business site is quicker to build than a larger project with integrations and custom features. We agree the timeline in the proposal, before work starts, and the process is split into clear steps so you know what happens when.

Next.js gives fast, search-friendly pages and Strapi gives a flexible content system you can control yourself. Together they give performance and freedom without locking you in. We compare Next.js with the alternatives in our guide to Next.js and WordPress.

Yes. With Strapi as the content system, you can update text and images yourself, without going through a developer for every change.

Launch is not the end. We follow up on performance and gather user feedback to improve the site over time. Many continue with ongoing development, often through one of our monthly plans.

Kevin A. Sommerstein

About the author

Kevin A. Sommerstein · Software Engineer

I have built websites and web apps for about ten years, mainly with Next.js, React and Node.js. At Developly I'm responsible for development and the technical decisions. You deal with me directly from the first call to launch.