5 Mistakes Business Owners Make When Ordering a Website

I've built enough websites for small businesses to notice the same handful of things going wrong, over and over, and almost never because of anything technical. They're decisions made early, often before a single line of the site exists, that quietly make the whole project harder than it needed to be for everyone involved.

None of these are about being a bad client. Most people ordering a website for the first time simply don't know what actually matters yet, which is completely fair, it's not your job to know. Here's what to watch for, so you can avoid learning it the hard way.

1. Picking the cheapest offer without checking what's actually included

When you're comparing quotes, a price on its own tells you almost nothing. One developer's "1500 zł" might include five pages, a working contact form, and help getting the whole thing live. Another's identical looking "1500 zł" might get you a single template page with no support at all if something breaks a month later.

Before choosing based purely on price, ask directly what's included, how many revision rounds you get, whether hosting and the domain are covered in that number, and what happens if you want changes after launch. A cheaper quote that's quietly missing half of what you actually need isn't cheaper, it's just a smaller bill now and a bigger, more annoying one later, usually at the worst possible time.

2. Not having a clear idea of what the site is actually for

"I need a website" isn't really a goal, it's a format. A website that exists to make people call and book a table is a different site from one meant to sell products directly, which is different again from one that just needs to prove you're a real, trustworthy business when someone looks you up out of curiosity.

Before you talk to a developer, it's worth spending ten honest minutes answering one question, what do you want someone to actually do after they land on this page. Call you? Buy something right there? Fill out a form? Everything about the site, the layout, what goes on the homepage, which button sits at the top, follows from that one answer. Skip this step, and you tend to end up with a site that looks perfectly fine but doesn't actually push visitors toward doing anything in particular.

3. Not planning for content and photos in advance

This is the quiet project killer, more than any technical issue ever is. Building the actual site is often faster than most people expect. What slows everything down is waiting on the text and photos that need to go into it, your services described properly, decent photos of your work or your space, your actual opening hours and contact details written out clearly.

If you wait until it's asked for, you're now trying to write good copy about your own business and dig up presentable photos under real time pressure, which is exactly when it takes the longest and looks the worst. Start pulling this together before the project even properly begins, even just rough notes and whatever photos you already have sitting on your phone. It saves weeks, genuinely, not days.

4. Ignoring how the site works on a phone

Most people building their first website picture it on a laptop screen, mostly because that's how they're looking at the draft when it's shown to them. But the majority of your actual visitors will land on it from their phone, checking your hours on the way somewhere, comparing you to a competitor while standing in a queue, googling you from the back seat of a car between errands.

If a site looks great on a desktop monitor but the text is tiny, the buttons are hard to tap accurately, or a menu doesn't work properly on mobile, you lose exactly the customers who were closest to actually making a decision right then and there. Whenever you're shown a draft of your site, check it on your own phone before approving anything, and not just how it looks either, actually try tapping the buttons and filling in the form yourself.

5. Going quiet during the revision phase

Almost every website goes through a round of feedback and adjustments after the first draft, that's completely normal and expected, not a sign anything went wrong. What causes real delays is when a client goes quiet for two or three weeks at exactly this stage, whether from being genuinely busy, unsure what to say, or just quietly putting it off.

The project doesn't move while you're not responding, and momentum is genuinely hard to get back once it's lost, on both sides of the conversation. If you're not sure how to phrase your feedback, even something as vague as "I don't love this but I can't quite say why" is useful and enough for me to work with. Vague and prompt beats precise and three weeks late, every single time.

A quick one worth adding, assuming the site will just get found

A lot of business owners assume that once a website exists, people will simply find it, the way a shop on a busy street gets noticed. A website doesn't work quite like that on its own. It needs a bit of thought around what people would actually search to find you, and it helps if you're at least somewhat clear on that early, rather than treating it as an afterthought once the site is already built and launched.

The pattern underneath all of this

Look closely and these aren't really five separate mistakes, they're mostly versions of the same thing, treating the website as something you hand off completely and only check back on later. The projects that go smoothly are the ones where the business owner stays a little bit involved throughout, clear about the goal upfront, quick with the photos and text, quick with feedback when it's needed.

That's genuinely most of what's asked of you. The rest, the actual building and problem solving, is the developer's job to carry.

If you're about to order a website and want a second pair of eyes on a quote you've already received, or just want to talk through what your project actually needs before committing to anything, get in touch.