What Actually Happens When You Order a Website, Step by Step

If you've never ordered a website before, it's easy to feel a bit lost about what you're actually signing up for. You send one message and then what? How long does it take? What do you need to prepare beforehand? What if you don't like how it looks halfway through, can you even say so?

I get some version of these questions from almost every new client, so here's the honest, unglamorous walkthrough of what actually happens, from the first conversation to the day your site goes live.

Step 1, the first conversation

This is just a normal conversation, not a sales pitch. I ask what your business does, who your customers are, what you want the site to actually achieve, and what, if anything, you already have, like a logo, existing photos, or an old website you're replacing. You don't need to arrive with answers to everything prepared in advance. Part of my job is helping you figure out what you actually need, especially if you've never thought about a website in these terms before.

At this stage there's no commitment on either side. It's just us figuring out whether the project makes sense and roughly what it involves, so you can walk away if it turns out not to be a fit, no hard feelings.

Step 2, the quote

Once I understand what you need, I put together a quote. This isn't a vague number pulled from thin air, it lays out what's included, roughly how many pages, what features, like a contact form, a shop, or a booking system, and the price and rough timeline.

If something in the quote doesn't match what you had in mind, this is the moment to say so. It's much easier to adjust the scope on paper now than to renegotiate it halfway through building. Take the time you need to think it over, there's no pressure to decide on the spot, and a rushed decision here is usually the source of headaches later.

Step 3, gathering the content

Once you approve the quote, I'll ask you for the material the site actually needs, your logo, photos, text about your business, your opening hours, your contact details, testimonials if you have any. This step often takes longer than people expect, mostly because good photos and clear text about your own business are surprisingly hard to pull together quickly when you actually sit down to do it.

My honest advice here, start gathering this early and don't wait until it's asked for. The single biggest thing that delays a website launch is the client, not the developer, still hunting for a decent photo of the shopfront three weeks in. If you don't have professional photos, that's completely fine, we can work with what you have or talk through alternatives together.

Step 4, design

Based on everything you've shared, I put together the visual direction, colors, layout, typography, the overall feel of the site. You'll see this before any of the technical building happens, so we're not guessing at what "looks right" to you after the fact, once it's already built.

This is the point where your gut reaction matters most. If something feels off, wrong colors, too busy, doesn't feel like your business at all, say so now. It's a five minute conversation to fix at this stage, not a rebuild once the whole site is built around it.

Step 5, building the site

This is the part that happens mostly out of view, and it's usually the longest single stretch of the project. I build out the actual pages, wire up any forms or shop functionality, make sure it works properly on phones, which is where most of your visitors will actually see it, and test that everything behaves as it should across different browsers and screen sizes.

You don't need to check in constantly during this stage. I'll update you at meaningful milestones rather than every small change, so you're not left wondering what's happening, but also not drowning in notifications about button colors and font sizes.

Step 6, revisions

Once there's a working version, you get to see it live, click around, and tell me what needs adjusting. Maybe a section needs reordering, some text needs tightening, a button needs to stand out more, or a photo just doesn't sit right. This is completely normal and expected, no website goes from first draft to perfect without a round or two of changes, and I'd honestly be suspicious of anyone who claimed otherwise.

A quote usually includes a set number of revision rounds, which keeps things fair for both sides and stops the project drifting endlessly. Small tweaks are quick to turn around. If you decide midway through that you actually want a completely different structure, that's a bigger conversation about scope, and I'll always tell you plainly if something has moved beyond what was originally agreed, rather than quietly absorbing it and letting the timeline slip.

Step 7, launch

Once you're happy with everything, we go live. This means connecting your domain, the address people type in, like yourbusiness.pl, setting up hosting if you don't already have it, and making sure everything works properly in the real world, not just on my testing setup.

Launch day is usually quiet and uneventful, which is exactly what you want from it. A calm, uneventful launch is a sign that the earlier steps were done properly, not that we got lucky.

Step 8, handoff

After launch, I show you how to do the basic day to day things yourself, if the site is built to allow that, like updating a text section or swapping a photo, so you're not dependent on me for every small change that comes up down the line. I'll also let you know what kind of ongoing support is available if you want it, and just as importantly, what isn't included, so there are no awkward surprises three months later.

What this actually means for you as a first time client

None of this requires you to know anything technical. Your job through the whole process is mostly to answer questions honestly, provide the material about your own business when it's needed, and tell me clearly and promptly when something doesn't feel right. Everything else, the actual building, the technical decisions, the problem solving, is on me.

The projects that go smoothly aren't the ones where the client happens to be technical. They're the ones where the client stays reasonably responsive and upfront. That's genuinely the whole ask.

If you're thinking about getting a website and the unknowns are what's holding you back more than the cost, reach out and I'll walk you through exactly what your specific project would look like before you commit to anything at all.