A Nice Website Is Not a Marketing System
Key takeaways:
- A website that looks good but converts at 0.05% is not an asset — it is a liability dressed in nice photography.
- Structural problems (unclear service pages, excessive form fields, no pricing guidance, no proof) kill conversions far more reliably than visual ones.
- Rebuilding for conversion rather than aesthetics returned roughly $180K in pipeline for an $18K investment over three months post-launch.
When the Numbers Don’t Match the Compliments
I have heard some version of this story dozens of times. A business spends real money on a website. The designer delivers something that looks sharp. The client’s colleagues say it looks great. Everyone moves on.
Then nothing happens.
Not a dramatic failure. Just silence. The traffic comes in, scrolls around, and leaves. The phone doesn’t ring any more than it did before. The contact form collects the occasional submission — a supplier, a job seeker, someone who clicked the wrong thing. The website sits there looking professional, doing almost nothing.
This is the gap nobody talks about at the brief stage. Looking credible and converting visitors into conversations are two different problems. A lot of agencies solve the first one and call it done.
What does a 0.05% conversion rate actually mean?
It means 6,400 people visited the site in a month, and three of them submitted an enquiry form.
That’s the situation a professional services firm near Tanjong Pagar found themselves in when they came to us. Their previous agency had built them what they described as a “modern website.” Nice photography. Clean layout. Nothing technically wrong with how it looked. But the analytics were damning. Three form submissions from 6,400 monthly visitors.
For context, a reasonable conversion rate for a professional services website — not world-class, just reasonable — sits somewhere between 1% and 3%. At 1%, that same traffic would have produced 64 enquiries. At 0.05%, they were getting 3. The site was haemorrhaging qualified opportunities every single month, and from the outside it looked completely fine.
The firm had been told they had a good website. They had a website with good aesthetics and broken fundamentals.
Why do professionally built websites fail to convert?
Because most agencies are briefed and measured on delivery, not on results. The brief says “build us a new website.” The agency builds a website. Job done.
Nobody writes into the contract “and it should convert at least 1% of visitors into enquiries within 90 days.” Nobody tracks that. So nobody optimises for it. The incentive is to produce something that looks good at handover, gets client approval, and closes the project.
I’ve been building websites since 1998. Back then, we had far fewer tools and zero analytics. But the fundamental question was always the same: what do you want someone to do when they get here? That question didn’t change when design tools got better. It just got buried under layers of mood boards and font choices.
When my team at Chillybin looked at this firm’s site, the design was the least of the problems. The actual structural issues were predictable. I’ve seen them a hundred times.
The service pages described what the firm did in vague, category-level language. “We provide strategic advisory and implementation support across a range of sectors.” That kind of copy tells a visitor almost nothing. It doesn’t help them self-qualify, understand scope, or feel like the firm is speaking directly to their problem.
There was no pricing guidance at all. Not exact numbers — pricing guidance. A sense of what engagement looks like, what a starting point might be, what variables affect cost. Professional services firms are often reluctant to put anything near a number on their site, and I understand the instinct, but the result is that every visitor has to make a blind enquiry just to find out if they can even afford you. Most won’t bother.
There were no case studies with outcomes. There were testimonials — two sentences each, no context, no numbers. Nothing that showed a prospective client what working with this firm had actually produced for someone like them.
And the contact form had 14 fields.
Name, company, email, phone, industry, company size, how did you hear about us, what service are you interested in, preferred contact time, message. I’m paraphrasing slightly but not much. Fourteen fields is not due diligence. Fourteen fields is friction. Serious enquirers will fill it in. Everyone else will close the tab.
How do you fix a website that looks fine but doesn’t work?
You stop treating it as a design problem and start treating it as a conversion architecture problem.
The rebuild we did for this firm took twelve weeks. It was not a visual overhaul. The photography was fine. The colour palette stayed. What changed was the structure — how information was organised, what was said on each page, and how visitors were guided toward making contact.
Service pages became specific. Instead of one page that lumped everything together under vague category labels, the firm had individual pages for each service line, each written to address a specific type of client problem. The language shifted from “what we do” to “what you get.” That’s a small distinction that makes an enormous difference to someone trying to figure out if they’re in the right place.
We added pricing guidance. Not a price list, but context. A typical engagement starts at X. Retainer arrangements usually run Y per month. Projects of this type generally involve Z deliverables over N weeks. That information filters out bad fits before they enquire, which actually improves the quality of the pipeline even if it slightly reduces raw volume. The firm was initially resistant to this. Two months post-launch, they told me it was the single change they were most glad they’d made.
The case studies got rebuilt with structure. Client situation, what was done, measurable outcome. Not every case study had hard numbers, but most did. The ones that did performed significantly better in terms of time-on-page and subsequent contact form completions.
The contact form went from 14 fields to 4. Name, email, company, and a free-text field for what they were looking for. That’s it. You can qualify leads in the first conversation. You cannot recover the ones who gave up at field nine.
Was an $18K rebuild worth it for a 15-person firm?
Three months after launch: same traffic (6,400 monthly visitors), 47 form submissions monthly instead of 3. Conversion rate moved from 0.05% to 0.73%. Their pipeline increased by roughly $180,000 in qualified opportunities.
The $18K investment returned multiples in less than a quarter. That’s not a story about design quality. That’s a story about building something with intent versus building something with aesthetics.
I want to be careful not to make this sound like every rebuild produces those numbers, because it doesn’t. This firm had the traffic. They had a credible service offering. They had real case studies with real outcomes. The inputs were there. What they were missing was a structure that converted those inputs into enquiries. When the structure got fixed, the existing traffic did the rest.
If a site has low traffic and low conversions, fixing the structure helps, but you’re also solving a different problem. If a site has decent traffic and almost no conversions, that’s a pure structural problem, and fixing it tends to produce fast results.
What separates a website from a marketing system?
Whether it was built to convert visitors into conversations, or built to win a client approval meeting.
I’ve watched this distinction play out across 25 years of client work. The sites that consistently generate pipeline have clear answers to three questions: Who is this for, what do we do for them, and what happens next. Every page answers those questions for a specific audience segment. Nothing is vague. Nothing requires the visitor to do extra interpretive work.
The sites that look good but generate nothing tend to answer a different question: How do we present ourselves? That’s a reasonable question for a brochure. It’s the wrong question for something that’s supposed to be your most scalable business development tool.
A marketing system isn’t a different product from a website. It’s the same product built with a different primary objective. You can visit chillybin.co and see how we think about this — the architecture of how we approach a build is driven by what a visitor needs to do, not by what a client wants to show.
The Tanjong Pagar firm didn’t need a new website. They needed their existing one to actually work. Sometimes those are the same project. Sometimes they’re not. The important part is knowing which problem you’re actually trying to solve before you spend anything.
Six months on from that rebuild, the firm’s biggest feedback wasn’t about the design at all. It was that they finally felt like their website was doing something. That’s the bar. Not “it looks good.” Does it do something.
Most websites don’t. Most were never built to.
