Web companies rarely advise against a project, because taking it produces revenue. There are several cases we raise first, because the client will not get what they expected and we end up with an unhappy one.
These are the situations where we suggest reconsidering or changing the approach.
1. Wanting a website because you feel you should have one
If you cannot say what problem the site solves, it will probably solve none.
The conversation typically goes: what do you want visitors to do — learn about our company. And after they have learned — well, they will know we exist.
What results is an attractive website nobody visits, and a conclusion a year later that this was a waste of money.
Our suggestion: settle on one concrete purpose first. It might be letting customers verify you are a real company before phoning. It might be being found when someone searches a specific service. It might be having a link to send in a message.
Those three produce entirely different websites. With a purpose, two pages suffice; without one, twenty achieve nothing.
2. Wanting to launch before the content exists
Half of a website is content — words, photographs, product information. Without them, what gets built is a template with nothing in it.
What we have seen: build first, add content later. Three months on it is still placeholder text and stock imagery.
Worse, this kind of site actively damages you. A visitor recognising template content and stock photographs concludes you are not serious, which is worse than having no website.
Our suggestion: prepare content to a launchable standard first. If it cannot be assembled quickly, build something small containing only real material — three genuine pages beat ten hollow ones.
Photography especially is worth doing first. In several industries conversion depends almost entirely on images, and one session lasts two or three years.
3. Spending the budget on the build with nothing left for promotion
The most common and most regrettable case.
The entire budget produces a carefully made website, nothing is spent on visibility afterwards, and the client waits for customers.
A website does not generate traffic, it receives it. Building one is like opening a shop; where it is and whether anyone passes are separate matters.
Where the total budget is limited we generally suggest: build only what is needed and reserve at least a third for promotion. A plain site with genuine content plus sustained visibility outperforms a beautiful one nobody sees.
Conversely, if your customers arrive by referral, the site’s role is verification rather than discovery and no promotion budget is required — but then it does not need to be large either. Who you are, what you do, how to reach you.
4. Wanting everything in version one
Memberships, a shop, scheduling, multiple languages, a forum, loyalty points — all of it immediately.
The obstacle is not technical. It is that every feature carries ongoing maintenance and most go unused after launch.
In our experience roughly half the features built into a first version sit idle a year later. Idle features are not free — they still need updating with the platform, still produce bugs, still need attention when a security issue appears.
Our suggestion: build only what you are certain you will use. Add the rest when a real need appears. Version one arrives sooner and costs less, and the decision about version two is made with actual usage rather than speculation.
5. Pages created purely for SEO
Someone will propose a landing page per service per suburb, producing fifty pages: service plus Auckland, service plus North Shore, service plus West.
That worked a decade ago, largely does not now, and carries risk — large volumes of near-identical content differing only by place name are treated as low quality.
The practical objection is more immediate: who writes and maintains fifty pages? Done badly it is fifty empty shells; done well it is fifty times the work.
Our suggestion: build a few pages with real substance. One page covering a service thoroughly, with real examples and actual prices, outperforms ten templates with the suburb swapped.
6. Expecting a website to fix a sales problem
If your problem is enquiries that do not convert, a website will not help. The issue is in quoting, follow-up, or the offer itself.
A website affects the number and quality of enquiries, not what happens after one arrives. Spending on a site to solve a sales problem is aimed at the wrong thing.
Here we usually suggest something far cheaper first: tidy up the follow-up process. A great deal of “did not convert” is actually “was forgotten”.
When it is worth doing
Conversely, the return is fairly reliable in these situations:
People search for your service and cannot find you. The most direct gap there is.
Referrals are frequent but people cannot verify you. After a recommendation, people search your name. Finding nothing, or something obviously dated, can lose the job. The value here is conversion rather than traffic, and it does not appear in analytics.
The existing site is difficult on a phone, or its information is wrong. Repair work: controlled cost, predictable result.
Opening a new customer group. A business serving Chinese customers wanting local ones, for instance. The website is a necessary entry point.
Why say any of this
The direct reason: projects that should not have happened trouble both sides. The client feels the money was wasted and we gain no work worth showing anyone.
The other reason is that being able to say what should not be done demonstrates that judgement was applied. A company that accepts everything and says yes to everything gives a client no way to tell what it is actually good at.
So if you talk to us and hear that we would not recommend proceeding, it is not a brush-off. Establishing that before starting saves both parties, and that stage is free.