The website development process, step by step

From the outside, the website development process often looks like a black box. You send an enquiry, you exchange emails for weeks, and then one day a finished site appears. Or it does not.

What a well-run project looks like

A well-run project is the opposite: a series of predictable steps where you know exactly where things stand, what the next decision point is and when something is needed from you.

In this article we go through the whole path from enquiry to launch, the way we do it. We also say what we expect from you along the way, because half of a project's speed depends on you.

Discovery and quote: half of the project is decided here

In the first meeting we do not ask what colour the button should be. We ask what the site has to achieve: bring enquiries, bookings or sales, or build trust before a more expensive service.

On top of that comes the target audience, the competitors, the existing brand and the content you already have. The clearer this picture, the fewer surprises later.

The quote

At the end of discovery comes the concrete quote: list of pages, features, schedule, price. For orientation only: a focused project starts from a few hundred thousand HUF, and the final amount is driven mostly by the number of pages, the custom features and the amount of content.

If a quote has no itemised content, only a total, ask about it. A lack of detail leads to disputes later.

Wireframe: the skeleton before anything looks nice

A wireframe is the skeleton of the site: a plain sketch of which section goes where, what is above the fold and where the buttons are. Many clients get impatient here and ask when it will look good.

Yet this phase saves the most money. Fixing a structural mistake in a wireframe takes ten minutes. On a finished, coded site the same fix takes days.

What to check in a wireframe

When you review a wireframe, watch for three questions:

• Is the order logical? Visitors read from top to bottom. Your strongest argument cannot sit at the bottom of the page.
• Is everything there? Whatever we leave out here becomes a painful late addition.
• Is it clear what the visitor should do? One page, one main action.

Design and development: where the plan becomes a website

After the skeleton is approved comes the design: colours, typography, imagery, motion. Everything that makes the site your brand and not an anonymous template. If you have a mature brand, we build on it.

If you do not, this is the point where we sort it out. We write more about how we think about this on our design service page.

From the approved visual design, development builds a working website: fast, flawless on a phone and easy for search engines to read. This is where the technical quality is decided: loading speed, security and a structure that can be extended later. We describe our approach on the web development page.

Content and SEO basics: in parallel, not afterwards

Content is the most common source of delay in the whole process. Text and images do not go on the site "at the end". The design is built on the real content, not the other way around.

In parallel we lay the SEO foundation: one main keyword per page, a clean heading structure, meta titles and descriptions, fast loading and a mobile-friendly build. This is not yet a full search optimisation campaign, which is a separate discipline. But without this foundation even the most beautiful site stays invisible on Google.

Testing and launch: "done" is a checklist, not an opinion

Before launch we do not check whether the site looks good. We go through a checklist: does the form actually send, and does the email arrive? Does every link work?

How does the page load on a phone with a weak connection? What does the form do with invalid input? Most errors surface here, and this is still the cheap moment to fix them.

The launch itself

The launch itself is a short, pre-agreed operation: domain and SSL setup, connecting the tracking codes and, if you had an old site, redirecting the old addresses to the new ones. That last step is critical. Without it, the Google positions you built earlier are simply lost.

Handover and maintenance: launch is not the end

At handover you get all the access details and a short training on the content management system, and we put in writing what counts as a warranty fix. Then comes the decision: who maintains the site? Besides updates, backups and small changes, the biggest value of maintenance is measurement.

You see where visitors come from, where they get stuck, and you improve the numbers month by month with small changes. A website is not a statue. It earns when it moves.

What we expect from you as a client, and why it speeds up the project

Project timelines typically range from a few weeks to a couple of months, and most of that spread comes not from development but from the pace of feedback and content. What we ask for:

• One decision maker. If five people comment in five directions, the project stalls. Have one person whose word decides.
• Content on time. Texts, images, the logo in vector format. Or say at the start that producing these is part of the project.

Feedback and honesty

• Feedback in one batch and on deadline. One collected list is worth far more than messages trickling in over two weeks.
• Honesty. If you do not like something, say so in the wireframe or design phase, when everything is still easy to move.

The next step

If you want to start now, the first step is a short meeting: we talk through what your site has to achieve, and you get an itemised quote. Write to us, and within a few days you will know exactly what to expect.