Why Web Projects Blow Up (and Whose Fault It Usually Is)

A business owner rings us in March. They signed in October. The site was due before Christmas.

They have paid about two thirds of the money. They have seen two designs, one of which they liked. They have not seen a working website. The last email from the developer was eleven days ago and said "just finishing off a few things". They want to know whether to keep waiting or start again.

We get this call often enough that the details blur. What does not blur is how similar the causes are. In the projects we have been brought in to finish, the same three things go wrong, in roughly the same order, almost every time.

The uncomfortable part of the post-mortem is that the fault is usually shared. Not always evenly, but shared. That matters, because the half you control is the half you can fix.

Why do website projects actually fail?

Almost never for technical reasons. In seven or eight years of picking up other people's unfinished work, I can count on one hand the projects that failed because something was genuinely too hard to build.

They fail because nobody wrote down what "done" meant, because the person building it stopped communicating, or because a decision sat unmade for six weeks while the clock ran. Usually some combination of all three, each one making the next more likely.

Those are process problems, not engineering problems. Which is good news: process problems are the kind you can spot early and fix cheaply.

The scope nobody wrote down

This is the first killer and the most common by a distance.

The proposal says "5-page website, modern design, mobile responsive, SEO ready, contact form". Everyone nods. Everyone signs. The trouble is that sentence describes almost nothing. What happens when the enquiry comes in? Does it email you, or land somewhere you can track? Who writes the words on the five pages? What happens to the 400 products on your old site? Is the booking system in or out?

Nobody asked, so everyone assumed. And people assume in their own favour, without meaning to. The owner assumes their existing content will be tidied up. The builder assumes it will be supplied ready to paste in. Neither is lying. They just never had the conversation, because the proposal was vague enough that both readings fit.

Six weeks later that gap surfaces as an argument about whether copywriting is a variation. Now there is money involved, and the relationship has its first crack.

The tell: a quote you can read in under a minute. Detail is not padding. A proposal that lists what is not included is worth more than one that lists only the good bits. We wrote about what actually happens inside a web project if you want the full shape of one.

The fix: before anything is built, get one page in writing that answers what you are getting, what you are supplying, and what happens if either changes. Not a legal document. One page. If your builder will not write it, that is information.

The builder who went quiet

The second killer is the one owners describe most vividly, because it is the one that feels personal.

Communication does not stop all at once. It degrades. Weekly calls become fortnightly. Detailed updates become "coming along well". Specific dates become "should be next week". By the time someone goes properly dark, the silence has been building for a month and everyone politely ignored it.

Sometimes this is what it looks like: someone took on too much work, is behind on three projects, and is avoiding the conversation because they do not have good news. It is rarely malice. It is almost always overcommitment plus embarrassment. That does not make it hurt less when it is your money and your launch date.

The tell: you cannot name a single thing that will exist by a specific date. Not a feeling of progress. A thing, and a date.

The fix: insist on seeing the actual work, on a real link, early and often. Not screenshots. Not a design file. A staging link you can open on your phone. Once a working link exists, silence becomes obvious immediately, because the link either changes or it does not. A project with a visible staging site from week two is very hard to hide inside.

The decision that never got made

Here is the half most articles skip, because it is the owner's half.

A lot of projects do not stall on the builder's side at all. They stall waiting for photos. For the final wording on the services page. For someone to decide whether the packages are called Bronze, Silver, Gold or something better. For sign-off that keeps getting pushed because the person who has to give it is busy actually running the business.

This is entirely understandable. You have a business to run and the website is one of forty things. But the effect is brutal, because momentum is the cheapest thing a project has and it does not survive a three-week gap. Work goes cold. Whoever was building it moves to another job to stay busy, and now you are queued behind someone else. A two-week stall routinely costs six weeks.

The tell: the last three emails in the thread are from them, waiting on you.

The fix: name one decision-maker before kickoff and give them a standing 30 minutes a week. One person, real authority, small regular commitment. If a decision genuinely needs the whole team, decide how that happens in advance, not the first time it comes up. And say "good enough for now" out loud more often than feels comfortable. Almost everything on a website is editable after launch, which is the whole point of launch day.

What does a project that does not blow up look like?

Boring, mostly. That is the honest answer.

There is a written scope you could hand to a stranger. There is a staging link from early on that changes visibly week to week. There is one person on each side who can make a call. There is a standing short meeting nobody dreads. When something changes, and something always changes, it gets priced and agreed before it gets built rather than argued about afterwards.

None of that is clever. It is just the difference between a project that finishes and a project you end up telling people about at barbecues.

Prices, since a warning without numbers is just a vibe: our rate is $990 a day and fixed build sprints are a flat $4,500, both inc. GST. A serious small-business build is typically a few weeks of work, not months. If a quote is dramatically under that, ask what has been left out. If it is dramatically over, ask what the extra buys. Both questions are fair, and how someone answers tells you more than the number does.

If you are already in the middle of one

If you recognised your own project in the paragraphs above, you are not as stuck as it feels.

Ask for three things in writing: what is complete, what remains, and a date for the next visible piece of work. A builder who is behind but honest will answer that within a day, and you can usually rescue the project from there. A builder who will not answer it has told you what you needed to know, and the sooner you act on that the less of your budget goes with it.

Either way, find out who controls your domain and hosting before you do anything else. That one is worth its own post, and it is the next one in this series.