• Web design pricing varies this much because “a website” is not a defined product — scope, complexity, integrations, and strategy are the real cost drivers.
• A professional agency engagement for a Singapore SME typically runs $8,000–$15,000, and that number reflects discovery, strategy, content structure, and build — not just a template drop.
• The hidden costs (hosting, maintenance, future updates) are where most buyers get surprised, and they’re almost never included in the headline quote.

The reason no one publishes their rates

I’ve been asked about web design pricing more times than I can count. The question usually comes in one of two forms: a prospective client who’s just received a $1,200 quote from someone on Fiverr and a $22,000 quote from an agency and genuinely cannot understand why the gap exists, or a business owner who’s been burned before and wants to know what they should have paid.

The industry doesn’t make this easy. Most agencies hide their rates. The logic is: if you don’t know what it costs, you can’t shop around. I think that’s bad for everyone. Clients who have no frame of reference make decisions based on the wrong criteria, and agencies that compete on transparency don’t benefit from doing so. So the opacity continues.

I’m not going to do that here. I’m going to give you real numbers, explain what drives them, and let you make an informed decision. That’s the article I wish existed when clients started coming to Chillybin with no frame of reference at all.

Why does a website cost anywhere from $500 to $50,000?

Because “a website” is not a product. It’s a category that contains everything from a one-page landing page with a contact form to a multi-language e-commerce platform with CRM integration, custom pricing logic, and a content management system that twelve staff members will use daily. Calling both of those “a website” is like calling a studio apartment and a commercial office building both “real estate.”

The range exists because the scope varies that much. When someone tells me they got a quote for $800 and a quote for $18,000 for “the same thing,” I ask to see both briefs. They’re never the same thing.

What actually drives cost at the high end is this: discovery and strategy (figuring out what you actually need, not just what you asked for), content volume (how many pages, how much copy, how much photography or video), integrations (booking systems, CRMs, payment gateways, inventory platforms), custom design versus template work, number of revision rounds, and post-launch support. Strip all of that out and yes, you can build something for $800. The question is whether it solves the problem.

What does a cheap website actually buy you?

Template. Usually one of several hundred available for $50 on ThemeForest, with your logo and colours dropped in. No discovery process, which means no one asked what your customers actually need from the site. Limited revisions, typically two rounds, so if you change your mind about structure after seeing it, you’re paying extra. Development is often offshore, which isn’t inherently bad but tends to mean the person building it doesn’t understand your market, your customers, or the business context.

No strategy. No copywriting. And critically, no ongoing relationship. When something breaks six months later (and something always does), you’re either paying a stranger to fix it or starting over.

I’ve seen this cycle repeat at least fifty times. A business saves money upfront, gets a site that technically exists but doesn’t convert, lives with it for eighteen months, then comes to us to rebuild it properly. At that point they’ve paid twice. The original cheap site costs more in the long run because the rebuild starts at zero.

The $800 site isn’t always a bad decision. If you’re a sole trader testing a concept, a quick landing page while you validate the business makes sense. But if you’re an established business trying to generate leads or revenue from your website, the $800 option is usually false economy.

What does $8,000 to $15,000 get you from a professional agency?

This is Chillybin’s typical engagement range for a Singapore SME. I’ll tell you exactly what that covers.

It starts with discovery. Before any design happens, we spend time understanding the business, the customers, the conversion goals, and the content structure. That work usually takes a week to two weeks and shapes everything downstream. Agencies that skip this step are the reason redesigns don’t perform.

From there: custom design (not a template, though we may start from a framework), structured copywriting guidance or full copy depending on the engagement, a WordPress build with a content management system the client can actually use themselves, integration of one or two third-party tools (contact forms, booking systems, analytics), three rounds of revisions built into the process, cross-device testing, and a handover session where we walk the client through how to manage the site.

At $8,000, you’re toward the simpler end: a five to eight page brochure site, clean design, solid foundation. At $15,000, you’re typically looking at more pages, more complex layouts, a deeper discovery process, possibly a blog or resources section, and more sophisticated integrations.

One client, a professional services firm in Singapore with about forty staff, came to us in 2024. They had a site that was embarrassing them in pitches. We rebuilt it over ten weeks: new information architecture, updated positioning, a complete redesign, and integration with their CRM. Total engagement was $13,500. Within three months they were closing deals they previously couldn’t because the site gave them the credibility the firm had earned but wasn’t showing.

What is $20,000 and above actually for?

Large scope. Complex integrations. Content production. Full strategy.

At this level you’re typically looking at: e-commerce with custom pricing logic or multiple product types, multi-language sites (Singapore builds often need English and Simplified Chinese at minimum), custom functionality that doesn’t exist off the shelf, full content production including photography and video, a detailed SEO strategy baked into the build rather than bolted on afterward, or organisations where multiple departments need to sign off on everything.

A $30,000 project is not three times better than a $10,000 project in any linear sense. It’s a fundamentally different scope of work. More stakeholders, more pages, more integrations, more rounds of review, more time. The billing reflects time and complexity, not prestige.

I’ve worked on projects above $50,000. At that level you’re usually talking about a platform, not just a website. Custom development, API integrations with legacy systems, staff training, phased rollouts. Most SMEs don’t need that. Most people who spend that much know exactly why they’re spending it.

What are the hidden costs buyers never factor in?

This is where the sticker shock hits later. The quote you receive from any agency is almost never the full picture of what owning a website costs over three years.

Domain registration: $15 to $30 per year, trivial. Hosting: this varies enormously. Shared hosting at $5 per month is not appropriate for a business site. A managed WordPress hosting plan that’s actually reliable runs $50 to $150 per month, or $600 to $1,800 per year.

Maintenance: WordPress requires updates. Core, plugins, themes. If those updates aren’t managed, you get security vulnerabilities and eventually a broken site. A maintenance retainer from a decent agency runs $150 to $400 per month. I know that sounds like a lot. I also know what it costs to clean up a hacked WordPress site that wasn’t maintained (usually $500 to $2,000 and significant downtime). The retainer is cheaper.

Future updates: your business changes. Staff change, services change, you launch new products, your contact details change. Someone has to make those updates. If you can do it yourself, great. If not, you’re paying hourly for someone to do it. Budget at least $500 to $1,500 per year for ad hoc content updates if you’re not doing them yourself.

SSL certificates are usually included in hosting now. Email is separate from your website and shouldn’t be hosted with it (use Google Workspace or Microsoft 365, not your web host).

Add it up. A $10,000 website that runs properly costs closer to $12,000 to $14,000 in year one once you include hosting, setup, and a maintenance agreement. Year two is cheaper because the build cost is gone, but you’re still looking at $2,000 to $3,500 per year in operational costs. Anyone quoting you a website without discussing these should be asked about them directly.

How do you know if a quote is fair?

Discovery has to happen before the quote, not after. This is the single biggest tell that separates professional agencies from mills.

If an agency sends you a fixed-price quote within 24 hours of an initial conversation, they haven’t scoped your project. They’ve guessed. Or they have a standard package they drop everyone into regardless of fit. Either way, you’re not getting a quote for your project, you’re getting a quote for their default output.

A proper discovery process involves at least one substantive conversation about your business goals, your customers, your current site’s performance (if there is one), your content, and your constraints. It might involve a brief they ask you to fill out. It might involve a second meeting. At Chillybin (chillybin.co), we don’t quote until we understand the scope. That sometimes means we come back with a number higher than expected. But it also means the number is accurate, and the client knows what they’re getting.

Check the quote for line items. What is actually included? Design, development, copywriting, photography, integrations, revisions, testing, training, hosting setup, maintenance? If it just says “WordPress website, $9,500” with no breakdown, push for the breakdown. A vague quote is a risk you’re absorbing.

Ask about revision rounds. Ask who owns the site files when the project is complete. Ask what happens if you need changes six months later. These questions reveal a lot about how the agency operates.

References matter more than portfolios. A portfolio shows you what sites look like. A reference tells you whether the client would work with that agency again.

What you’re actually paying for

I’ve been doing this since 1998. Back then, building a website meant hand-coding HTML, uploading files via FTP, and hoping the design held together in both Netscape and Internet Explorer. The tools have changed enormously. What hasn’t changed is that the value of a website comes from whether it works, not whether it exists.

Web design pricing is high when the work is thorough. The discovery, the strategy, the copywriting, the architecture, the testing, the training, the ongoing support. That’s not padding, that’s the work. The cheap version skips most of it.

The number on the quote is not the price of the website. It’s the price of a process. What you’re evaluating is whether that process is the right one for your business. Get two or three quotes from agencies who ask real questions before giving you a number. Compare them on scope, not just price. And factor in the three-year cost of owning the thing, not just the cost of building it.

A site that costs $12,000 to build and generates $8,000 per month in leads was cheap. A site that costs $900 and sits there for two years without producing anything was expensive.

• The discovery call is the most reliable signal you have, agencies that ask about your business before your budget are worth talking to; the ones that skip straight to quoting are not.
• “Who does the actual work?” is the single most important question most buyers never ask. The answer will tell you more than any portfolio screenshot.
• Agencies that push back on your brief are showing competence, not arrogance. The ones who say yes to everything are the ones who will quietly fail you six months later.

The View from Inside the Industry

I’ve introduced clients to other agencies more times than most people would expect. Sometimes we weren’t the right fit for the budget. Sometimes the client needed a capability we didn’t have. Sometimes I just knew a competitor would serve them better than we would, and I said so.

What those conversations taught me (watching those engagements from a distance, sometimes hearing how they ended) is that most buyers have no idea what to actually look for when choosing a WordPress agency. They look at portfolios and check Google reviews and compare quotes. None of that is wrong. But it misses the signals that actually matter.

If I had to hire a competitor to build my own site tomorrow, I would not do any of those things first. I would run a very specific set of tests. Here is exactly what those tests are.

What should a good discovery call feel like?

Within the first ten minutes of a call, you can tell almost everything you need to know about how an agency operates.

A good agency will ask about your business before they ask about your website. What do you sell? Who buys it? What happens after someone visits your site, do they call, do they buy online, do they fill out a form? What has not worked before? These questions are not small talk. They are an agency doing its job, which is to understand the problem before proposing a solution.

A weak agency will ask what pages you need, what your budget is, and when you want to launch. Those questions are not wrong, they are just wrong to ask first. Agencies that open with them are not thinking about your business. They are thinking about scoping a project.

I had a client last year who came to me after spending six weeks with another agency. The first call with that agency lasted forty minutes. The client told me they spent most of it talking about the design brief. Nobody asked about conversion rates, about where their leads currently came from, or about why the existing site was underperforming. They got a beautiful new site that launched on time and changed nothing about their business results.

The discovery call is not a formality. It is the first real test of whether an agency thinks like a partner or like a vendor.

Who does the actual work?

This is the question most buyers never ask, and it is the one that matters most.

When you hire an agency, you are not necessarily hiring the people on the call. You might be hiring a project manager who coordinates with a development team in Eastern Europe, a designer in the Philippines, and a copywriter who also works with three other agencies simultaneously. None of that is automatically bad. My own team at Chillybin is distributed across six countries, and I am transparent about that with every client from the first conversation.

The problem is when agencies obscure this. When they show you a team page full of faces without being willing to tell you which of those people will touch your project. When they give vague answers about “our development team” without specifying where they sit, what their process looks like, or how quality is controlled across time zones.

Ask directly: who will manage my project day to day? Who does the development work? Is that person an employee or a contractor? If the agency hedges, changes the subject, or gets defensive, that is a signal worth taking seriously.

I have seen too many engagements fall apart not because the agency lacked skill but because the person who sold the project was never involved in delivering it, and nobody on the delivery side had any real context for what the client actually needed.

What should you actually look at in a portfolio?

Not the screenshots. Screenshots tell you almost nothing useful.

Any agency can make a site look good in a static image on a high-resolution display. What you want to know is what happened after it launched. Did the client’s conversion rate improve? Did organic traffic grow? Did they rehire the agency for the next phase of work, or did they disappear?

Ask these questions directly. A good agency will have answers, because they have stayed in contact with their clients and they track what their work produces. Some will be able to give you before-and-after numbers. A 34% increase in quote requests. A page that went from 2.1% conversion to 4.7% within three months of launch. A site that now ranks for twenty terms it previously did not appear for at all.

An agency that cannot speak to outcomes (only to deliverables) is an agency that does not think in terms of results. That is a real distinction, and it becomes a very expensive one about eight months after your site goes live.

The second thing I would look at is whether the portfolio shows range of problem, not just range of industry. Pretty sites for restaurants and lawyers and e-commerce brands do not tell me the agency can solve complex problems. I want to see evidence of an agency that has navigated something genuinely difficult: a migration from a legacy platform, a site that needed to perform in multiple languages, a project that changed scope significantly mid-build and still landed well.

Process is what separates agencies that get lucky from agencies that reliably deliver.

Why would a good agency push back on my brief?

Because your brief is probably wrong in at least two places, and a competent agency knows that.

This is the thing buyers consistently misread. You come in with a brief. You have been thinking about this for months. You know what you want. Then the agency says they are not sure the approach you have described will actually solve the problem, and you feel like they are being difficult.

They are doing their job.

Back in 2009 when I started Chillybin, I made the mistake of saying yes to everything. A client asked for a feature that made no sense for their users (I built it. A client wanted a homepage layout that would have buried their most important content below the fold) I designed it. The sites launched. The results were mediocre. And I was the one who knew, before a single line of code was written, that the approach was flawed.

An agency that says yes to everything is not being accommodating. It is being cowardly, or it does not understand the work well enough to know what to push back on.

What good pushback sounds like: “I understand why you want this, but here is what we have seen happen when sites are structured this way, and here is an alternative that addresses the same goal.” What bad pushback sounds like: “We do not do it that way.” One is expertise. The other is a rigid process masquerading as a standard.

If an agency reviews your brief and has no questions, no challenges, and no alternative suggestions, be cautious. A brief that requires no pushback is either perfect (rare) or being accepted by someone who is not thinking hard enough about it (common).

What does pricing actually tell you?

A lot more than most buyers realise.

Suspiciously cheap almost always means one of three things: the project is being scoped as a template deployment with minimal customisation, the development work is being offshored with minimal quality control, or ongoing support and maintenance are simply not included in the model and will be charged at a painful hourly rate later.

I have seen $2,000 WordPress builds that worked fine for two years. I have also seen $8,000 builds that were unmaintainable after six months because the agency used a custom theme architecture that only they could support, and then they stopped answering emails.

The number itself matters less than understanding what is actually inside it. Get a proper scope breakdown. Understand what happens after launch. Understand who you call when something breaks at 11pm on a Sunday before a product launch. If the agency does not have a clear answer to that question, you are buying a product, not a service.

Agencies that do not raise the retainer conversation during the sales process are selling you a finished object. Once they hand it over, your leverage disappears. The best agencies I have observed treat launch as the beginning of a relationship, not the delivery of a finished asset.

What are the red flags that are easy to miss?

The absence of process documentation is the one I would weight most heavily.

If you ask an agency how they manage a project and they give you a narrative rather than a framework, pay attention. “We kick off with a design phase, then go into development, then QA, then launch” is not a process. Every agency says this. It tells you nothing about how decisions get made, how scope changes are handled, how content delays are managed, or what the approval process looks like when the client and the agency disagree.

Ask for a sample timeline or a project plan from a previous engagement. Ask how they handle a situation where the client is late delivering content. Ask what their revision policy is and where it has caused friction in the past. The specificity of those answers will tell you more than the agency’s website ever will.

A process document that has clearly been built from actual experience of things going wrong is worth ten polished case studies. Experience shows up in the edge cases, not the success stories.

The other flag I would watch for: no questions about your existing site before proposing a rebuild. Any agency worth hiring will want to look at your analytics, your current traffic sources, and what is already working before they suggest tearing everything down. An agency that proposes a full rebuild before seeing a single data point is not thinking about your business. They are thinking about their pipeline.

The part buyers consistently underweight

Culture fit matters in a way that sounds soft until it is not.

You are going to disagree with your agency at some point. A decision will need to be made quickly, or a piece of feedback will be delivered bluntly, or a timeline will slip and the conversation will become uncomfortable. How an agency handles those moments is entirely a product of who they are, not what they have built before.

Ask about a project that went wrong. Every agency that has been operating for more than three years has had one. How they talk about it tells you how they operate when things are hard. Agencies that cannot describe a failure clearly are either inexperienced or defensive. Neither is what you want.

Knowing how to choose a WordPress agency is really knowing how to read the signals that most buyers skip past because they are looking at the wrong things. Screenshots. Quote comparisons. Review counts.

What I would actually look for is an agency that asks better questions than I do, tells me when my brief is wrong, knows exactly who is building my site, and has clearly been through enough difficult projects to have built a real process out of the wreckage.

That combination is rarer than it should be. But it exists. You just have to know where to look.

• Most WordPress agencies optimise for delivering what the client asked for, not what the client’s business actually needs, and the difference is expensive.
• The brief is a symptom. A good discovery process identifies the underlying problem. Most agencies skip discovery because it risks losing the project.
• The question that separates useful agencies from order-takers: “What does success look like in 12 months, measured in something other than how the site looks?”

When the brief is the wrong brief

I have been running a web agency since 2009. Before that, I was building sites for clients from 2003, doing the same work without the letterhead. Sixteen years of scoping, building, launching, and then watching what happens after launch has given me a specific kind of education, one that does not come from courses or conferences. It comes from patterns.

The pattern I see most often is this: a client arrives with a request, an agency takes that request at face value, builds the thing, and the thing does not move the needle the client was hoping to move. Nobody calls it a failure. The site launches, the invoice gets paid, and the client quietly wonders why nothing changed.

The wordpress agency industry is very good at executing briefs. It is much less good at questioning them.

Why do clients arrive with the wrong brief?

Clients arrive with the wrong brief because they are not briefing agencies on their business problem. They are briefing them on the solution they have already decided on. “We need a redesign.” “We need a new homepage.” “We need something that looks more modern.” These are solutions, not problems. And the agency, presented with a solution, gets to work on the solution.

This is not a conspiracy. Clients are not trying to mislead anyone. They come in having already done the internal conversation, the marketing manager has been told the site looks dated, the CEO has been to a competitor’s site and felt embarrassed, someone saw a mood board on Pinterest and forwarded it to the team. By the time they reach out to an agency, they have already formed a conclusion. The brief is that conclusion, handed over as instructions.

The problem is that the conclusion is almost always about aesthetics, and the actual problem is almost always about behaviour. Not how the site looks. What people do when they get there.

What does it mean to solve the actual business problem?

I had a client come to me a couple of years back wanting a full redesign. They had a services business, solid SEO traffic, a site that was maybe four years old and, honestly, not that bad to look at. But they were frustrated with it. They had a mood board. They had references. They wanted it to feel “more premium.”

Before any wireframes got drawn, I asked them to pull their analytics. The story those numbers told had nothing to do with how the site looked. Their homepage had a 78% bounce rate. Their contact page had a form that required seven fields and an anti-spam CAPTCHA that was breaking on mobile. About 60% of their traffic was on mobile. They had not checked the form in eight months.

The form was broken. Not metaphorically. The submissions were going to an email address that nobody monitored anymore.

A redesign would not have fixed any of that. We fixed the form, simplified it to three fields, replaced the CAPTCHA, and made sure the submissions were going somewhere useful. Bounce rate came down. Enquiries came in. The site looked exactly the same. They never did the redesign. They did not need it.

That is the gap I am describing. The brief said “redesign.” The business problem was “our contact form is broken and we are losing every lead we generate.”

Why do agencies execute the brief instead of challenging it?

The economics punish honesty. If I get on a call with a client who wants a $15,000 redesign and I tell them the redesign will not fix their problem, I risk losing the $15,000. The version where I say nothing and start on the mood board is the version that keeps the project alive.

Most agencies have made the calculation, consciously or not, that the brief is safer than the problem. The brief has a defined scope. The brief has a deliverable. You can show the client a finished product and say, “Here is what you asked for.” When you are solving a business problem, the deliverable is murkier, the scope is harder to pin down, and the results take longer to materialise.

Questioning the brief also requires a level of confidence that newer agencies and junior project managers do not always have. It feels presumptuous to tell a client they have the wrong solution. So instead, you execute what they asked for, everyone stays comfortable in the short term, and the actual problem stays unresolved.

I have done it myself, early on. I know exactly what the rationalisation sounds like from the inside: “They know their business, I know web design, let’s stay in our lanes.” The problem is that the brief lives at the intersection of both, and if nobody owns that intersection, it stays unowned.

What is discovery actually supposed to do?

Discovery is supposed to find that intersection. It is supposed to get underneath the stated request and identify what is actually happening.

A real discovery process for a website project covers a few specific things. Who is actually using the site right now, and what are they doing? Where are the drop-offs? What does the analytics data say versus what the client assumes? What has the client tried before, and what happened? What does a successful outcome look like in 12 months, measured in something concrete, something that is not “the site feels more premium”?

That last question is the one I ask in every first call now. “What does success look like in 12 months, measured in something other than how the site looks?” It is a simple question and it is genuinely clarifying. Some clients have a crisp answer immediately. “We need 40 qualified enquiries a month, we are getting 11.” That client knows what they have. That relationship will work because we are talking about the same thing.

Other clients pause and then describe aesthetics again. “We just want something that represents the brand better.” That is not a wrong answer, but it tells me the conversation about the actual problem has not happened yet, and we need to have it before anything else.

What separates an agency that builds sites from one that solves problems?

The mood board client and the problem client are genuinely different relationships. I do not mean that one client is unsophisticated and one is not. I mean that one client has thought past the deliverable and one has not, and the difference shapes everything that follows.

Mood board clients judge the project by whether the site looks like the references they brought. Problem clients judge the project by whether the problem got solved. Those are different criteria and they produce different working relationships. With a mood board client, every design decision becomes a negotiation about personal taste. With a problem client, every design decision is answerable with data: does this version convert better, does it load faster, does it reduce friction at the point where people were leaving?

The agencies that consistently build good work have shifted from the first framing to the second. They have stopped treating the brief as a spec and started treating it as a starting point. The brief tells you what the client has already decided. A good discovery process tells you what is actually true.

At Chillybin, we restructured our scoping process around this about six years ago. The discovery phase now comes before any conversation about design. Before we talk about what the site will look like, we talk about what it currently does, what the data shows, and what a solved version of this problem looks like. Some clients find this process confronting. It occasionally costs us the project. But the work that comes out of it is work we can stand behind, because the brief we are executing is the real brief, not the first brief.

The brief is a symptom, not a diagnosis

Sixteen years of scoping projects has left me fairly sure of one thing: clients do not arrive knowing exactly what they need. They arrive knowing what they think they need, which is different. The gap between those two things is where good agency work lives.

The agencies that will still be around in ten years are not the ones that get fastest at executing whatever lands in their inbox. They are the ones that have built a reputation for naming the actual problem, even when it costs them the easy version of the project.

Most clients have never worked with an agency that pushed back on the brief in a useful way. When it happens, they remember it. That is what earns the relationship, not the mood board.

A company will happily approve a $20,000 website redesign. New look, new feel, a launch announcement on LinkedIn, maybe even a small celebration in the office. Everyone’s proud. The project gets a slide in the quarterly board deck. Twelve months later, the site is quietly degrading — broken form fields, unpatched plugins, hosting performance that’s slowly bleeding mobile conversions — and nobody’s noticed because nobody’s watching.

Then I ask about website maintenance. “We’ll think about it” is the polite version. The honest version is that maintenance feels like a cost with no visible return.

This article is about why that thinking is wrong, what it actually costs, and what a sensible maintenance budget looks like for businesses operating in Singapore and the broader Southeast Asian market.

The Redesign Gets a Party. Maintenance Prevents the Disasters Nobody Talks About.

The psychology here is simple. Redesigns are visible. You can put a before-and-after screenshot in a presentation. You can point at the new homepage and say “we did that.” There’s a narrative arc — brief, reveal, launch.

Maintenance has no narrative arc. The story of good maintenance is: nothing went wrong. There’s no before-and-after for “the contact form kept working in October.” Nobody sends a company-wide email to celebrate the fact that a plugin vulnerability was patched within 48 hours of disclosure.

But that invisible work is doing real things.

A broken contact form that nobody catches for three weeks isn’t just a technical inconvenience. If your site generates five qualified enquiries per week and your average deal size is $8,000, three weeks of silence from your main lead capture channel is $120,000 in pipeline you never saw. You won’t find that number anywhere in your analytics. It just won’t appear.

This is the fundamental problem with how most businesses think about their websites after launch. They treat the launch as the finish line. It isn’t. It’s the start of the maintenance phase.

The Maths That Nobody Wants to Do

Let me make this concrete.

A typical business website redesign in Singapore runs between $15,000 and $30,000 depending on scope, functionality, and the studio involved. Call it $20,000 as a working number. Most businesses I’ve spoken to operate on roughly a three-year redesign cycle — sometimes shorter if the brand changes, sometimes longer if the budget doesn’t stretch.

Over three years, that’s $6,666 per year to address accumulated technical debt, design staleness, and whatever broke that finally became impossible to ignore.

A proper website maintenance plan — covering security monitoring, software and plugin updates, uptime monitoring, performance checks, regular backups, and basic content updates — runs around $300 per month, or $3,600 per year, for a standard business site.

So the comparison looks like this:

• Reactive approach: $6,666/year (averaged redesign cost) to fix things after they break, look outdated, or finally become a business problem
• Maintenance approach: $3,600/year to prevent most of those problems from occurring in the first place

The boring dollar is cheaper. It’s also more effective. And yet it’s the harder sell, every single time.

What $147/Month Actually Catches

I want to be specific about what ongoing website maintenance actually does, because “maintenance” is a vague word that tends to get dismissed as overhead.

Here’s what active monitoring and maintenance catches:

Plugin and CMS vulnerabilities disclosed on a Friday. Security researchers and hackers both operate on the same schedule, and it’s not 9-to-5 Monday to Friday. Vulnerability disclosures happen at inconvenient times. If nobody’s watching your site over the weekend, a known exploit can sit unpatched for 72 hours. That’s 72 hours of exposure on a vulnerability that’s now public knowledge.

Form failures that don’t announce themselves. Contact forms, quote request forms, booking forms — these break silently. A plugin conflict, a server-side change, a third-party API that updated its authentication requirements. The form looks fine on the front end. It just doesn’t deliver submissions anywhere. The only way to catch this reliably is to test it regularly.

Hosting performance degradation. This one is slow and insidious. Shared hosting plans in particular can degrade over months as server load increases or neighbouring sites consume more resources. A site that loaded in 1.8 seconds at launch might be loading in 4.2 seconds eighteen months later. You probably haven’t noticed because the change happened gradually. Your mobile visitors noticed. Google noticed.

Broken links accumulating from external sources. Partners change their URLs. Resources you linked to get moved or deleted. Internal links break when pages get restructured. A site with significant broken links is a worse experience and ranks worse. These don’t fix themselves.

Expired SSL certificates. Yes, this still happens. Automated renewal systems fail. Hosting control panels have bugs. An expired SSL certificate turns your site into a warning page in most browsers. If a potential client hits that warning before they’ve ever spoken to you, the relationship is over before it started.

None of this is exciting to prevent. All of it is expensive to repair after the fact.

A Scenario I’ve Seen More Than Once

A professional services firm in Singapore — legal sector, twelve-person team — came to us after a competitor pointed out their site had been showing a security warning for an unknown period. Best estimate was ten days.

They’d launched the site about eighteen months earlier. It was well-built, clean, professional. But they had no maintenance arrangement in place. No one was monitoring it. No one was checking.

In ten days, they’d had roughly 340 visitors to the site based on their analytics. Every single one of those visitors saw a browser warning telling them the site was potentially unsafe before they saw anything about the firm.

We fixed the immediate issue — an SSL certificate that had lapsed because the automated renewal had failed silently — within a couple of hours. But the harder conversation was about the ten days that had already happened. There’s no way to know how many of those 340 visitors were prospective clients. There’s no way to quantify what that period cost them in credibility.

They signed up for a maintenance plan the same week.

Why the Redesign Cycle Is Often a Symptom, Not a Strategy

Here’s the contrarian part of this argument.

Businesses that maintain their websites properly tend to need redesigns less frequently. A site that’s been kept technically healthy, performance-optimised, and content-fresh over three years will often still be competitive at the four or five-year mark. The decision to redesign becomes genuinely strategic — new brand direction, significant expansion, major shift in audience — rather than reactive (“it looks dated and the backend is a mess”).

Businesses that skip maintenance tend to hit a wall at the two or three-year mark where the site is technically fragile, slow, potentially insecure, and hard to update. The redesign isn’t really a strategic choice at that point. It’s a cleanup operation disguised as a rebrand.

I’ve seen this play out with clients at Chillybin over many years. The sites that age best are the ones that were treated as ongoing infrastructure rather than completed projects.

That reframe matters. Your website isn’t a project you finish. It’s infrastructure you operate.

Website Maintenance in Singapore: What the Market Actually Looks Like

One thing worth understanding about the Singapore market specifically is that expectations around digital quality are high. Singapore has some of the fastest internet speeds in the world, a highly mobile-literate population, and business audiences that are used to polished digital experiences.

A slow site or a broken form isn’t just a minor inconvenience here — it signals something about how your business operates. The baseline expectation is higher than in many other markets, which means the cost of a poorly maintained site is also higher.

There’s also the regulatory dimension. Depending on your sector, you may have obligations around data handling, security, and uptime that a dormant, unmonitored site can quietly fall out of compliance with. That’s a separate conversation, but it’s part of the maintenance picture.

What a reasonable website maintenance plan covers in this market:

• Security: WordPress (or equivalent CMS) core updates, plugin updates, theme updates, malware scanning, vulnerability monitoring
• Performance: Regular speed audits, image optimisation, caching checks, Core Web Vitals monitoring
• Uptime: 24/7 monitoring with alerts, not just a monthly report that confirms something broke
• Backups: Automated daily backups stored off-server, with a tested restoration process
• Content: Minor updates, text changes, new team members, updated service descriptions
• Reporting: Monthly reports that tell you something actionable, not just uptime percentages

Some agencies bundle this. Some offer it as a standalone service. The price varies, but the floor for anything that covers all of the above properly is around $200–$400 per month for a standard business site. Below that, you’re probably getting monitoring and updates only, which is better than nothing but not comprehensive.

The Invisible Return Is Still a Return

I want to address the objection I hear most often, which is some version of: “How do I know it’s working if nothing happens?”

This is actually the wrong frame. You don’t question whether your building’s fire suppression system is “working” because there hasn’t been a fire. The absence of the disaster is the evidence.

But if you need something more concrete: look at your site’s performance metrics over time. A maintained site should show stable or improving load times, consistent uptime above 99.9%, no security incidents, and form conversion rates that don’t mysteriously dip and then recover. If you’re seeing spikes and drops in your lead flow that don’t correspond to traffic changes, that’s often a maintenance failure leaving fingerprints.

Good maintenance also shows up in your SEO performance. Google’s signals increasingly reward sites that are fast, secure, and technically clean. A site that’s been maintained properly for two years has a compounding advantage over one that hasn’t.

The Takeaway Is Simple, Even If the Sell Isn’t

The $3,600/year maintenance budget doesn’t have a launch party. It doesn’t produce a before-and-after screenshot. It doesn’t generate a notification that says “you saved $40,000 today by catching that vulnerability on Friday afternoon.”

But the maths is straightforward. Preventing problems costs less than fixing them. A maintained site outperforms an unmaintained one on speed, security, and reliability. And the businesses that treat their website as ongoing infrastructure rather than a completed project get better returns from it over time.

The boring dollar — the one that monitors, updates, and prevents — consistently outperforms the exciting one. It’s just harder to put on a slide deck.

That doesn’t make it optional. It makes it the right call.

• A healthcare services site with a 69% mobile bounce rate saw that figure drop to 28% after a mobile-first rebuild, with membership signups up 43% and appointment bookings up 31% over the following six months.
• Desktop performance barely changed because desktop was already working. The entire gain came from closing the gap between where the traffic was and where the experience was broken.
• For most B2B and service-based websites in 2026, the largest conversion opportunity is not a redesign, a rebrand, or new content — it is fixing a mobile experience that was built as an afterthought.

Most sites are optimised for a visitor who doesn’t exist

The average website I look at in 2026 has been built, consciously or not, for a desktop user sitting at a desk with time to spare. Clean navigation, generous whitespace, hover states that work beautifully with a mouse. And somewhere in the analytics, a mobile traffic share sitting between 55% and 70%, with a bounce rate that would make a direct mail copywriter weep.

This is not a new observation. The industry has been talking about mobile-first since at least 2012. But talking about something and actually building for it are two different things. I have been building websites since 1998 and I have watched this gap persist across every era of the web — through the Flash years, the skeuomorphic years, the flat design years, and whatever we are calling the current one. The default mode is still desktop-first with mobile bolted on afterwards.

The site I am going to walk through here is a good illustration of what happens when you close that gap properly.

What did the original site actually look like?

The client runs a healthcare services business. Membership signups and appointment bookings are the two conversion goals that directly drive revenue. When they came to us at Chillybin, mobile accounted for around 60% of their total traffic. Their mobile bounce rate was 69%.

That number is worth sitting with. More than two-thirds of their mobile visitors were leaving immediately. Not navigating to another page, not reading the content and deciding the service wasn’t for them — leaving before the page had given them a reason to stay.

The desktop experience was not exceptional, but it was functional. Users were converting. The booking flow made sense. The information hierarchy did the job. Desktop bounce rate was in a normal range and desktop conversions were adequate.

The problem was not the website in the abstract. The problem was the mobile website specifically, and that problem was invisible to the client because nobody had shown them the split.

When I pulled the mobile analytics separately in the first conversation, the client’s response was something along the lines of “I assumed mobile would always be worse.” That assumption is exactly where the money gets left on the table.

What does a mobile-first rebuild actually involve?

It does not mean making the desktop site smaller. That is responsive design, and responsive design done carelessly is how you end up with a 69% mobile bounce rate in the first place.

A genuine mobile-first rebuild starts with the smallest screen and asks: what does this person need, and what is the fastest path to them getting it? Everything else is secondary.

For this project, that translated into three specific areas of work.

The first was mobile-first design. We rebuilt the layout starting from a 390px viewport and worked outward. Navigation was simplified to the two or three actions that mobile users were actually there to take. Content blocks that looked fine on a 27-inch monitor were completely rethought for a screen you hold in one hand while waiting for an appointment.

The second was the booking flow. The original booking process required users to navigate through four screens on mobile, with form fields sized for a mouse cursor and a date picker that was technically functional but practically unusable on a touchscreen. We rebuilt it as a three-step flow with large tap targets, auto-advancing between fields, and a progress indicator so the user always knew where they were. The cognitive load dropped noticeably — even in early user testing.

The third was page speed. This is the one clients often underestimate. A site that loads in 4.2 seconds on a fast Wi-Fi connection is loading in 7 or 8 seconds on a mobile network in certain parts of Southeast Asia. We compressed and properly sized every image, deferred non-critical scripts, and moved to a faster hosting environment. First contentful paint dropped from 4.1 seconds to 1.4 seconds on a mid-range Android device.

None of this was revolutionary. It was fundamentals done properly.

Why did the desktop metrics barely change?

Because desktop was not broken. This is actually the most instructive part of the result.

There is a pattern I have seen play out dozens of times across 25 years of this work. A site has a real performance problem. The client and their team use the site primarily on desktop. The problem is invisible to them because they are not experiencing it. They bring in an agency or consultant who does a general audit and recommends a full redesign. The redesign improves the desktop experience that was already working and does not fundamentally solve the mobile experience that was not.

Six months later, the numbers have not moved much and nobody is quite sure why.

The reason is that the intervention was applied to the wrong surface. Desktop was performing. Mobile was leaking. A redesign that treated both equally did not fix the leak.

In this project, we kept desktop largely intact. The visual identity stayed consistent, the content strategy did not change, the desktop booking flow was left almost exactly as it was. The investment went almost entirely into mobile. Six months out, the desktop metrics are essentially unchanged from where they were before. That is not a failure — that is the correct outcome. We did not break what was working.

What did the six-month numbers actually show?

Mobile bounce rate dropped from 69% to 28%. Membership signups over the six-month post-launch period were up 43% compared to the same window the prior year. Appointment bookings were up 31%.

To be precise about what this comparison controls for: we are looking at September through February versus September through February the previous year. Same seasonal period, same marketing spend, no significant changes to their service offering or pricing. The only material change was the website.

A 43% increase in membership signups from a single infrastructure change is not a small number. For a membership-based healthcare business, that compounds. New members who sign up in September are still members in February. The booking uplift flows from the membership growth, but also partially from existing members who were previously abandoning the booking process on mobile.

The underlying math was always there. Sixty percent of traffic, zero percent of focus. The rebuild moved the focus to where the traffic was.

Is this pattern specific to healthcare, or does it show up elsewhere?

It shows up everywhere, but it shows up most visibly in service businesses where the conversion action requires some friction — a form, a booking, a signup, a quote request. The more steps involved, the more damage a poor mobile experience does.

I have seen similar gaps in legal services, education, financial planning, and B2B software. I looked at a professional services firm last year whose mobile traffic had crossed 50% for the first time. Their mobile bounce rate was 74%. Their entire lead generation process had been built three years earlier around a desktop contact form that was technically present on mobile but required horizontal scrolling to complete.

The gap between where the traffic is and where the experience works — that is where the conversion loss lives. In 2026, for most B2B and service-based sites in Singapore and Australia, that gap is on mobile. Not because mobile design is hard, but because most sites were built by teams who tested on desktop and assumed.

How do you find your own gap?

Open Google Analytics or whatever platform you use. Segment your traffic by device category. Look at bounce rate, time on page, and conversion rate for mobile versus desktop separately. If you have never done this before, what you find will probably be uncomfortable.

Then look at your booking flow, your contact form, or whatever action you want visitors to take. Go through it on your actual phone — not a desktop browser with a resized window, your actual phone on a mobile network. Time yourself. Count the taps. Notice the moments where you want to give up.

Most business owners and marketing managers do not do this regularly. They check the site on their phone once when it launches and assume it still works the same way two years later, after three plugin updates, a new theme version, and a content team that has been adding images optimised for the homepage hero banner.

The gap grows quietly. Analytics shows the aggregate numbers but does not show you where the experience breaks unless you look specifically at the mobile segment.

One thing I have learned from building and reviewing hundreds of sites across different industries: the clients who look at their mobile analytics in detail are consistently the ones who find the biggest opportunities. Not because they are smarter — because they are looking at the right data.

The healthcare rebuild is not a special case. It is what happens when you point the work at the actual problem instead of the visible problem. Mobile was broken. We fixed mobile. The numbers moved.

Most sites I look at right now have a version of this same gap. The desktop experience was built carefully, tested carefully, and maintained. The mobile experience was generated by a responsive theme and left alone. Sixty percent of the traffic hits that experience and leaves.

Find your gap. That is where the work is.

• Most businesses have GA4 installed and have never logged in, meaning they are making website and marketing decisions with no data at all.
• Analytics data frequently reveals that the highest-value fixes on a website cost nothing to implement and require no redesign.
• In digital marketing in Singapore and across Southeast Asia, the gap between having analytics and actually using it is where most marketing budgets get wasted.

The redesign conversation that almost happened

Earlier this year I had a discovery call with a business owner who wanted a website refresh. Typical brief. The site felt dated, the design hadn’t been touched in a few years, they wanted something more modern. We were maybe ten minutes into the conversation when I asked about their analytics.

“Oh yeah, we have Google Analytics set up.”

I asked them to share the screen. GA4 had been installed for two years. Nobody had ever logged in. Not once.

Two years of traffic patterns, bounce rates, conversion paths, device breakdowns, all sitting in a Google account that nobody had touched. The instinct for most agencies at this point is to keep the conversation moving toward the deliverable. Book the project. Start the scope. But I’ve been doing this long enough to know that redesigning before you look at the data is one of the most expensive mistakes a business can make.

We spent the next twenty minutes in GA4 instead.

What does two years of ignored analytics actually show?

It shows you exactly where your website is failing, in ways that opinion and gut feel never will.

Within those twenty minutes we found three things that changed the entire direction of the conversation. Their highest-traffic page was not the homepage. It was a blog post from 2022 that still ranked well in search. Their contact page had the lowest time-on-page of any page on the site. And mobile visitors were bouncing at 78%.

None of that required a redesign to fix.

The blog post from 2022 had no call to action on it. It was pulling in organic traffic and sending it nowhere. Adding a simple lead capture or a link to a relevant service page would take a developer a couple of hours. The contact page loading slowly or presenting poorly on mobile? That’s a performance and layout issue, not a design identity issue. The 78% mobile bounce rate is a signal that something in the mobile experience is breaking before people commit to doing anything.

A redesign would have addressed the homepage aesthetics and probably made the contact page look cleaner. It would not have fixed any of the actual problems, because nobody had looked at the data to know what the actual problems were.

Why do so many businesses never open GA4?

Because GA4 is genuinely harder to use than Universal Analytics was, and most businesses were never trained on it.

Google forced the migration from Universal Analytics to GA4 in mid-2023. A lot of businesses had a developer install the tag, confirm it was tracking, and close the ticket. That was the extent of the transition. Nobody sat down and explained what the interface looked like, which reports to look at, or how to interpret what they were seeing.

GA4 also looks intimidating if you’re not in it regularly. The default home screen isn’t particularly useful. The reports are structured differently than what people were used to. And so the tab gets closed and never reopened, which means the data accumulates without anyone benefiting from it.

I’ve seen this pattern with clients in Singapore, in Australia, in businesses running six-figure ad spends who have a dashboard sitting there and don’t know how to read it. It’s not a size-of-business problem. It’s a setup-and-handoff problem. Someone installed it, nobody was taught to use it, and the workflow never formed.

What should you actually be looking at in GA4?

Start with four things, and ignore everything else until those four make sense.

The first is your traffic by landing page. Not your traffic overall, your traffic by the specific page people first arrive on. Most businesses assume this is their homepage. It often isn’t. Blog posts, service pages, and location pages frequently outperform homepages in organic search, and if those pages aren’t set up to convert, you’re leaking leads constantly.

The second is device category breakdown. What percentage of your visitors are on mobile versus desktop? If mobile is above 60% (and for most businesses in Singapore it is, given how phone-centric the market is here), every design and UX decision needs to be made mobile-first. Not mobile-friendly. Mobile-first.

The third is engagement rate by page. GA4 replaced the old bounce rate concept with “engagement rate,” which measures sessions where the user was actively engaged for more than ten seconds, triggered a conversion event, or visited more than one page. A low engagement rate on a page that’s meant to convert is a clear signal that something is wrong with that page specifically.

The fourth is conversion paths, what GA4 calls the “path exploration” report. This shows you the sequence of pages people visit before completing a goal. When you see that most of your form submissions come from people who visited the pricing page before the contact page, that’s useful. It means the pricing page is doing work, and you should keep it prominent, not bury it.

Those four views will tell you more about what your website is doing than any amount of stakeholder opinion.

Is this relevant to businesses running paid digital marketing in Singapore?

Especially relevant, and this is where ignored analytics becomes genuinely expensive.

If you are running Google Ads or Meta campaigns and sending that traffic to a landing page that has a 75% bounce rate, you are paying for that traffic and getting almost none of the value from it. The analytics will show you this. The ad platform will not, because the ad platform’s job is to keep you spending, not to tell you your landing page is broken.

I’ve worked with clients who were spending $5,000 a month on paid digital marketing in Singapore and had never connected their ad conversions to their GA4 data. They were measuring clicks from the ad platform. Clicks are not conversions. Clicks are people arriving. What happens after the click is where the money is made or wasted, and that story lives in your analytics, not in your ad dashboard.

Connecting GA4 to Google Ads, setting up proper conversion events, and reviewing which pages the paid traffic actually converts on takes a few hours to set up correctly. The information it gives you changes how you allocate budget. The businesses I’ve seen get this right spend the same money and get materially better results, because they stop putting money into traffic patterns that don’t convert and start reinforcing the ones that do.

My team at Chillybin has had this conversation so many times that it’s become part of how we open every new digital marketing engagement. Before we talk about what to build or what to spend, we look at what the data already says. Nine times out of ten, it says something useful that changes the conversation.

How do you go from no analytics habit to actually using it?

You make it a fixed, recurring task with a specific scope, not an open-ended investigation.

The reason most people don’t open GA4 is that they don’t know what they’re looking for, and so opening it feels like staring at a wall of information with no starting point. The fix for that is to define the starting point before you open the tab.

Pick a day each month. Open GA4. Look at the same four things every time: top landing pages by traffic, device breakdown, engagement rate by page, and conversion events. Write down one observation. That’s it. You’re not looking for insights every time. You’re building familiarity so that when something changes, you notice it.

Over time this habit compounds. You start to know what “normal” looks like for your site, which means anomalies stand out. A page that usually gets 400 sessions a month drops to 80, and you notice it quickly. A mobile bounce rate that was 65% is now 82%, and you know something has broken. This is how analytics actually helps you, not through quarterly reports someone else produces, but through you knowing your own numbers well enough to act when they shift.

If you have a team member who handles marketing, this is a task that can sit with them. But make sure there is a specific output expected from the review, even if it’s just a three-line summary in a shared document. Accountability and structure are what turn analytics access into analytics use.

The business I mentioned at the start of this article did not do a redesign. They updated the 2022 blog post with a clear call to action and a link to their most relevant service page. They fixed a rendering issue on mobile that their developer identified in about ninety minutes. And they added a stronger value statement to the contact page with one testimonial above the form.

Three months later their contact form submissions had increased meaningfully. Their mobile bounce rate was down to 61%. They had not spent a cent on a new website.

The data was there the whole time. It just needed someone to open it.

• Peak season website outages are almost always preventable, and almost always happen because nobody planned for the traffic before it arrived.
• The cost of downtime during a high-traffic period is not just lost sales — it’s lost trust, lost ad spend, and customers who don’t come back.
• A basic uptime and load monitoring setup costs less per year than a single hour of emergency developer time during a crisis.

The reunion dinner ends. The traffic spike begins.

Every Chinese New Year, the same thing happens. Businesses close for a few days. Teams rest. Families eat. And then, usually somewhere between the second and fifth day of the new year, the phones and the inboxes and the websites wake back up — all at once.

I’ve watched this pattern for years from Singapore. The city has a rhythm to it. CNY is one of the clearest examples. The quiet before the traffic is almost deceptive. Everything feels calm because everyone is eating lo hei and watching the lion dances. Then Monday arrives, the office reopens, the promotions go live, and whatever was quietly broken in the background becomes very publicly broken in the foreground.

In 2025, our team at Chillybin spans six countries. We support clients across Singapore, Australia, Southeast Asia, and beyond. And without exception, the support tickets that arrive in the days immediately after a major public holiday follow a pattern I’ve been watching for two decades. The sites that go down during peak periods are almost never the ones that were poorly built. They’re the ones nobody checked before the storm arrived.

Why does downtime always happen at the worst moment?

Because load and timing are the two things most website owners never plan for together.

A site that handles 300 visitors a day without issue can fall over at 3,000. Hosting that costs $20 a month is optimised for average traffic, not spike traffic. And if you’ve just sent an email to 40,000 subscribers or launched a promotion on the back of a public holiday, you’ve just turned an average Tuesday into a stress test your server wasn’t prepared for.

I’ve seen this happen dozens of times. One client runs a retail business in Singapore — decent-sized email list, a seasonal promotion they run every CNY. For two years running, the campaign went out and the site slowed to the point of being functionally unusable within about 90 minutes. The first year they assumed it was a one-off. The second year they called me. We looked at their hosting setup and it was exactly what you’d expect: a shared hosting plan they’d been on since 2019, never reviewed, never upgraded, perfectly adequate for normal weeks and completely inadequate for the one week per year when it actually mattered most.

We moved them to a plan with auto-scaling. Set up basic uptime monitoring. Put a load test on the calendar for six weeks before the next promotion. The third year, the campaign went live, the traffic came in, and nothing broke. Uneventful in the best possible way.

What does website downtime actually cost?

More than most people calculate, because most people only count the obvious number.

If you run an e-commerce store and your site is down for two hours during peak traffic, you lose the revenue from those two hours. That’s the number people quote. But the real cost is bigger. You’ve also burned the ad spend that was driving traffic to a broken page. You’ve created a bad first impression for every new visitor who hit that page and bounced. You’ve probably sent an email campaign that drove people somewhere that didn’t work. And you’ve trained your existing customers — even if only slightly — to think of your site as unreliable.

That last one is the one that compounds over time. I’ve been building websites since 1998. In the early days, downtime was more common and more accepted. Tolerance for it has dropped significantly. People have too many alternatives. If your page doesn’t load in three seconds, they leave. If it doesn’t load at all, they find someone else and they may not come back.

In 2025, with paid traffic costs what they are in Singapore and Australia, sending visitors to a page that isn’t responding is one of the most expensive mistakes a business can make. Google Ads doesn’t refund you because your server fell over.

What should you actually monitor?

Uptime, load time, and transaction completion — in that order.

Uptime monitoring is the baseline. There are tools that will ping your site every minute or every five minutes and alert you the moment it stops responding. Some are free. Some cost $20 a month. There is no excuse in 2025 for not having one configured. I still encounter clients who have no idea their site went down unless a customer emails them. That’s a position that would have been understandable in 2003. It isn’t understandable now.

Load time monitoring tells you something different. A site can be technically “up” and still be so slow it might as well be down. A 12-second page load during a traffic spike is not a functioning website. Tools like Google Search Console will show you performance trends over time, and there are third-party tools that will give you real-time load data broken down by geography — which matters if you’re serving customers across Singapore, Malaysia, and Australia from the same server.

Transaction completion monitoring is the one most people skip. This is where you check that the actual end-to-end flow works: the cart, the checkout, the form submission, the booking confirmation. A site can pass an uptime check and still have a broken payment gateway. I’ve seen this happen after routine plugin updates, after hosting migrations, after seemingly unrelated changes. If you’re not synthetically testing the full user journey on a scheduled basis, you’re finding out it’s broken when a customer tells you — or when you notice your conversion rate has quietly collapsed.

How much does it cost to set this up properly?

Less than one hour of emergency developer time during a crisis.

That’s the comparison I use with clients who push back on spending money on preventive monitoring. Emergency developer support — the kind you need at 11pm when your site is down the day after a major holiday campaign launch — costs between $150 and $300 per hour at minimum, usually more if it’s genuinely urgent. A basic uptime monitoring setup, a decent hosting plan with some room to breathe, and a pre-peak load test will run you somewhere between $500 and $1,500 to do properly, and then a fraction of that per year to maintain.

The maths aren’t complicated. The decision is just inconvenient because it requires spending money before a problem exists, and most businesses operate on a “fix it when it breaks” model for their websites. I’ve spent 25 years watching this model fail repeatedly and expensively.

The businesses that treat their website like infrastructure — the same way they’d treat their point-of-sale system or their phone lines — are the ones that don’t call me in a panic during Chinese New Year. The ones that treat it like a brochure they published and forgot about are the ones who find out, at the worst possible moment, that it stopped working sometime last Tuesday.

What’s the right time to do this?

Before you need it. Which means before peak season, before a campaign launch, before anything that’s going to send a significant volume of people to your site at once.

In Singapore, the calendar is full of these moments. CNY. National Day. Harborfront sale events. The back-to-school period. The year-end holidays. In Australia, it’s EOFY, Christmas trading, and the January rush. These dates don’t sneak up on you. You know they’re coming.

The mistake I see most often is treating the campaign as the project and the website as an afterthought. The email sequence gets built. The ads get set up. The discount codes get loaded. And nobody asks: “What happens to our site if 5,000 people click this link in the same two-hour window?”

My recommendation is simple. Six weeks before any major campaign or peak period, run a load test. Check your hosting plan against your expected traffic. Confirm your monitoring is configured and alerting to a real person who will actually see the alert. Make sure your checkout or enquiry flow works end to end. This takes half a day if your setup is already reasonable. It takes longer if you’ve been ignoring the infrastructure, but that’s still a better use of time than rebuilding trust with customers after a failed launch.

At Chillybin (chillybin.co), the pre-campaign infrastructure check is something we’ve built into how we work with clients. It’s not glamorous. Clients don’t send us thank-you notes when nothing goes wrong. But I’d rather that than the alternative.

This year, the Fire Horse energy everyone’s talking about means ambition and acceleration. That’s fine. Ambition is worth nothing if the infrastructure underneath it can’t hold the weight. Build the campaigns, run the promotions, push the growth — but check your bloody website before you hit send.

• The difference between agencies that deliver reliably and ones that operate on heroics is almost always invisible infrastructure: databases, templates, and systems that clients never see and rarely think to ask about.
• Investing time in internal tooling — client intelligence, standardised design components, deployment processes — compounds over years. The payoff is consistency, not speed on any single project.
• Most agencies skip this work because it doesn’t win clients, doesn’t appear in proposals, and doesn’t photograph well. That’s exactly why it separates the ones who last from the ones who don’t.

What separates agencies that last from ones that look like they will

I spent the break between Christmas and New Year doing work that will never appear in a case study. No client will reference it in a testimonial. It won’t show up in a proposal or impress anyone on a discovery call. It was internal systems work, and it was some of the most valuable time I’ve spent in years.

That probably sounds backwards. The instinct in most agencies is to fill any downtime with sales activity, content, or at minimum a planning session with optimistic revenue targets written on a whiteboard. I’ve done all of that. But after 25 years of watching agencies operate, including building and running Chillybin since 2009, I’ve come to a fairly firm conclusion: the agencies that deliver consistently are not the ones with the best pitch decks. They’re the ones who did the boring infrastructure work that nobody posts about.

What does “internal infrastructure” actually mean for a web agency?

It means the systems and tooling your team uses every day that clients never interact with directly but absolutely feel the effects of.

For us, that breaks into three areas right now. First, a proper client intelligence database. We’re rolling out a setup with 120+ data points per maintenance client, connected to ClickUp, ActiveCampaign, and our ticketing system. Before this, too much knowledge lived in email threads or in someone’s head. Hosting credentials buried in a chain from 2021. Notes about a client’s preferences scattered across Slack. That’s not a systems problem unique to us — every agency I’ve spoken to has some version of it. The fix isn’t complicated, but it requires someone to actually sit down and build it properly, which means not billing client hours while doing it.

Second, updated design templates in Figma. Standardised component library, consistent naming conventions, structured so new projects can start from a real foundation rather than from last quarter’s client work with the colours changed. Back in 2015 we were doing a version of this with Photoshop documents that nobody could find and even fewer people could open without something going wrong. The tools have improved dramatically. The discipline to actually build and maintain a proper component library — that requires intention, not tools.

Third, Beaver Builder 2.10. We deployed the update across client sites starting in October last year. The Components feature specifically is saving meaningful time per build. When I say meaningful I mean hours, not minutes, across a project. That’s real margin recovered, or real time returned to quality work that used to get squeezed at the end of a build.

Why don’t more agencies do this?

Because it doesn’t win clients and it doesn’t get celebrated.

Nobody is going to post on LinkedIn about the fact that they spent three days rebuilding their internal database schema. No client is going to reference it in a referral. There’s no award category for “most improved ticketing system integration.” The incentives in agency life all point toward client-facing work, visible deliverables, and things that can be put in front of a prospect.

I understand the pressure. In 2009 when I started Chillybin, every hour that wasn’t billable felt like a loss. That framing is almost universal in the early years of running any service business. But it’s the wrong frame, and the longer you hold it the more it costs you.

The agencies I’ve watched fall apart — and I’ve watched a lot of them over the years — don’t usually collapse because of a bad client or a lost pitch. They collapse because the internal scaffolding was never built. Everything depended on one person knowing where things were. Every project required heroics to deliver. The margin got eaten by rework and hunting and miscommunication that a proper system would have prevented.

One client we’ve worked with for several years came to us after leaving another agency. The handover was a disaster. No documentation. Hosting credentials locked to a personal email address. No record of what plugins had been installed or why. The previous agency wasn’t negligent — they were just operating without the boring infrastructure that makes clean handovers possible. That’s not a horror story unique to small operators. I’ve seen it happen at agencies with 30 people and decent revenue. Scale doesn’t fix a systems problem. It amplifies it.

What does it actually cost to skip this work?

The cost is almost never visible until it’s expensive.

A disorganised client database doesn’t cause a crisis on a Tuesday in March. It causes a two-hour delay on a Friday afternoon when someone’s site is down and you’re hunting through email for the hosting login while the client is watching. A missing Figma component library doesn’t fail a project — it just means every project starts slower than it should and the design consistency that clients pay for slowly degrades across a portfolio of work.

This is the insidious thing about infrastructure debt: it doesn’t look like a problem until the cost is real. In services businesses especially, the default is to absorb those costs invisibly — through longer hours, through stress, through senior people doing junior work because the system doesn’t support delegation properly.

At Chillybin we track things like build time per project type and ticket resolution rates across our maintenance clients. When those numbers move in the wrong direction, the cause is almost always a systems gap rather than a people gap. Someone isn’t slow. The process is missing or broken. The distinction matters because fixing people is hard and fixing process is usually just unglamorous work that someone has to prioritise.

Is this only relevant to agencies?

No, but agencies feel it more acutely because the work is relentless and the margin for error is narrow.

Any business that delivers services on repeat — whether that’s web development, accounting, legal work, or consulting — accumulates the same kind of invisible debt. The consultancy that keeps everything in the founder’s head. The law firm that stores matter notes in email folders. The accountant whose client onboarding process is a mental checklist rather than a documented workflow.

The pattern is identical. The business works because the people are good. And then growth, or turnover, or illness, or just volume reveals that the business was actually running on individual heroics with no supporting structure.

I first noticed this clearly in myself back around 2012. Chillybin had grown enough that I couldn’t personally oversee every project. The gaps in our systems became immediately and painfully obvious. Not because anything catastrophic happened, but because things that had worked when I was close to everything stopped working when I wasn’t. That period of rebuilding our internal processes was genuinely uncomfortable. It required admitting that what had worked wasn’t scalable and then doing the work to fix it while still running the business day-to-day.

Most people postpone that reckoning until they’re forced into it. Doing it proactively, when you have the time and the margin to do it properly, is almost always better. Downtime between projects, quiet periods in the calendar, the gap between Christmas and New Year — that’s when the infrastructure work actually gets done properly if it’s ever going to.

How do you know where to start?

Start with whatever caused the most pain in the last six months.

This is the only heuristic I use now. There’s no shortage of systems that could be improved at any given time. If you try to audit everything you end up in a planning loop. But if you ask the team where the friction is — where things slow down, where information gets lost, where someone has to ask the same question twice — you get a specific, honest list.

For us, the client intelligence database came directly from a maintenance review where we realised the information we needed to do good proactive work for clients was scattered across four systems and one person’s memory. The Figma component library came from a retrospective where two designers independently rebuilt similar components for two separate projects in the same month. The Beaver Builder update came from tracking build time data and seeing the efficiency gain clearly enough to prioritise deployment across the portfolio.

None of these were strategic insights. They were responses to observed friction. The strategy is just: fix the friction before it becomes structural.

The agencies and businesses that operate with the most reliability aren’t necessarily the ones with the best talent or the highest-profile clients. They’re the ones that did the unsexy systems work early enough that it stopped being a problem. The infrastructure becomes invisible because it works. That’s the point.

Most of this work will never show up anywhere a client can see. It won’t be mentioned in a sales conversation. The clients who benefit from it won’t know they’re benefiting from it. That’s fine. That’s what good infrastructure is supposed to do.

• WordPress is dropping support for PHP 7.2 and 7.3, meaning sites still running those versions will become vulnerable and eventually stop functioning correctly.
• The upgrade itself takes roughly an hour, but without staging environment testing first, it carries real risk of breaking a live site.
• Paying a developer $400–600 to handle this properly is significantly cheaper than emergency recovery on a site that stops loading for your customers.

The maintenance tasks nobody thinks about until something stops working

I’ve been building websites since 1998. In that time I’ve watched the industry develop a reliable pattern: everyone ignores the infrastructure until the infrastructure ignores them back.

PHP versioning is a perfect example. It’s not glamorous. It doesn’t come up in brand strategy meetings. Nobody has ever asked me, during a discovery call, whether their hosting environment is running a deprecated runtime. But when it goes wrong, it goes wrong loudly. Pages that won’t load. Admin dashboards that throw white screens. Plugins that silently corrupt data because they’re executing against a version of PHP that no longer behaves the way they expect.

The WordPress ecosystem has been moving toward PHP 8.x for years. The deprecation of 7.2 and 7.3 is not a surprise. It’s been telegraphed through official channels, through hosting provider notices, through developer forums. And yet, when my team at Chillybin audited our full maintenance client list last October, we found 12 sites still sitting on PHP 7.3. These weren’t neglected sites. They were active businesses with ongoing maintenance contracts. The problem is that PHP version isn’t something you see when you log into WordPress. You have to go looking for it.

What does PHP deprecation actually mean for a WordPress site?

It means WordPress will stop guaranteeing compatibility with those versions. In practice, what follows is a cascade. Core updates ship with code optimised for supported PHP versions. Plugin developers stop testing against deprecated versions. Security patches get applied to supported environments first, and sometimes only. A site running PHP 7.2 in late 2024 is a site running on infrastructure the entire ecosystem has quietly moved away from.

The WordPress core team doesn’t pull the plug dramatically. What happens is more gradual and, in some ways, more dangerous. Your site keeps loading until one day it doesn’t. A plugin update introduces a function call that PHP 7.3 handles differently than PHP 8.1. A core update assumes a capability that older PHP doesn’t have. An edge case in your checkout process, your contact form, your membership logic, stops working. You might not notice for days. Your customers notice immediately.

I’ve seen this play out more times than I can count. A client rings on a Tuesday afternoon. Their WooCommerce store is showing a white screen on the cart page. They updated a plugin that morning. Rollback doesn’t fix it. The actual problem is two layers deeper: the plugin update was written for PHP 8.0, and the server is running 7.3. The plugin author tested against supported environments. Nobody tested against a deprecated one.

How do you check what PHP version your site is running?

The fastest way is to log into your WordPress dashboard and go to Tools > Site Health. WordPress added this panel a few years back and it surfaces your PHP version clearly. If you’re on 7.2 or 7.3, it’ll flag it as a recommendation to upgrade. If you’re on anything below 8.0, you should at minimum know that and have a plan.

The second method is through your hosting control panel. cPanel, Plesk, and most managed WordPress hosting interfaces give you direct access to PHP version settings. Some hosts, particularly older shared hosting providers, still default new accounts to legacy versions because legacy defaults cause fewer support tickets on day one. The problem surfaces later, and by then most customers have forgotten what the original setup was.

A third option is to install a plugin like Display PHP Version, which puts the information directly in your admin bar. Takes thirty seconds.

When we ran our October audit at Chillybin, we pulled PHP version data across all 100-plus maintenance clients programmatically. Of the 12 running 7.3, several were on hosting setups that had been provisioned years earlier and never touched. The hosting environment had been stable, so nobody had looked at it. Stable and current are not the same thing.

Why can’t you just upgrade PHP and be done with it?

You can. And sometimes it’s completely uneventful. The upgrade itself, at the server level, takes minutes. What takes time is knowing whether your existing codebase will behave correctly under the new version.

PHP 8.x introduced breaking changes relative to 7.x. Functions that were deprecated in 7.4 were removed entirely in 8.0. Argument handling changed. Error handling tightened. Code that was sloppy but functional under 7.3 can produce fatal errors under 8.1 or 8.2. Most well-maintained plugins and themes have handled this. But “most” is not “all”, and a single incompatible plugin can take down an entire site.

This is why staging environments exist. You spin up an identical copy of the live site, upgrade PHP on the staging copy, run through the site systematically, and log what breaks. Then you fix those things before you touch the live environment. The whole process, including testing and fixes, runs roughly an hour if nothing major breaks. If something major breaks, you find out on staging instead of on your live site at 2pm on a Wednesday.

One client I worked with earlier this year had a booking system built on a plugin that hadn’t been updated since 2021. When we tested their PHP upgrade in staging, the booking confirmation emails stopped sending entirely. A function the plugin relied on had been removed in PHP 8.0. We found a compatible alternative, tested it in staging over two days, then pushed to live. Zero downtime. Zero customer impact. If they’d upgraded PHP directly on the live server without staging, they’d have had a broken booking system and no idea why.

Is paying a developer to handle this worth it?

Yes. A developer who knows what they’re doing will charge somewhere between $400 and $600 to handle a PHP upgrade properly. That includes auditing your plugin and theme compatibility, setting up or using an existing staging environment, running the upgrade, testing systematically, and resolving anything that breaks before it affects the live site.

Compare that to the alternative. Emergency developer rates for a site that’s down are typically double standard rates, and that’s before you factor in the revenue impact of downtime. A small e-commerce site doing modest numbers can lose hundreds of dollars per hour during an outage. A service business with a broken contact form is generating zero leads while the site is broken, often without realising it. The $400–600 is insurance. The premium is cheap relative to the claim.

There’s also a compounding risk that often gets overlooked. Sites running deprecated PHP versions are running software that no longer receives security patches from the PHP Foundation. Vulnerabilities discovered in PHP 7.3 after its end-of-life date don’t get fixed. They get published. Your server is running software with known, unpatched security holes, and the information about those holes is publicly available to anyone who wants it.

I’m not raising this to alarm people. I’m raising it because it’s the argument that actually lands when I’m talking to a client who’s hesitating on the cost. The $500 isn’t just about keeping the site functional. It’s about not running exploitable infrastructure.

What should you actually do this week?

Check your PHP version today. Log into WordPress, go to Tools > Site Health, and look at what it says. If you’re on 8.0 or higher, you’re in reasonable shape. If you’re on 7.4, you’re not in immediate danger but you should have an upgrade scheduled before the end of the year. If you’re on 7.2 or 7.3, treat this as urgent.

Contact your hosting provider and ask two things: what PHP version you’re currently running, and what the process is to upgrade. Most reputable hosts have made this straightforward. If your host doesn’t support PHP 8.1 or higher, that’s a separate conversation worth having, but start with the upgrade path.

If you have a developer or agency managing your site, forward this to them and ask where your environment sits. If you’re self-managing and comfortable in the WordPress backend, the Site Health panel will give you what you need to start the conversation with your host.

If the site is complex, has custom code, or runs e-commerce, don’t upgrade PHP directly on the live server without testing first. That’s the one rule. Everything else is manageable.

The sites that end up broken in these situations are almost never neglected. They’re sites that were set up properly at the time, maintained reasonably well, and never had anyone look at the underlying server configuration because nothing had gone wrong. That’s the gap. Infrastructure doesn’t announce that it’s drifting out of currency. It just quietly becomes a liability.

Twenty-five years of this work has made me fairly unsentimental about the boring parts of web infrastructure. PHP versions, database backups, SSL renewals, server software patches: none of it is interesting, and all of it matters more than the font choice on your homepage. The sites that stay reliable are the ones where someone is actually watching the underneath, not just the surface. The surface is easy to see. The underneath is where the real risk lives.

• A low-cost website that fails to generate enquiries is not a bargain — it has a calculable cost in missed revenue that typically exceeds the price of a proper rebuild.
• The metrics that reveal a website’s real performance are enquiry volume, average session duration, and conversion rate — not how the site looks or what it cost to build.
• For professional services firms, a single converted client can exceed the full cost of a website rebuild, which means the ROI calculation is simpler than most business owners assume.

What a template install actually costs you over three years

There is a version of this story I have seen dozens of times. A business gets a website built for a few thousand dollars. It looks reasonable. It loads. The team signs off on it and moves on. Three years later, nothing has changed — the site still loads, it still looks roughly the same, and it is still generating almost no enquiries. Nobody connects those two facts.

I built my first website in 1998. WordPress did not exist. Neither did the template economy that now makes it trivially easy to put something online for next to nothing. When I started using WordPress in 2003 and founded Chillybin in 2009, the conversation around website investment was different — partly because there were fewer cheap options, and partly because clients had fewer reference points for what a bad site was costing them. Now the cheap options are everywhere, and the cost of a poor website has never been higher because attention is harder to earn and competitors are better at keeping it.

The story I want to walk through here is a specific one, because the numbers make the argument better than any general principle can.

What was wrong with a $3,500 website from 2021?

Quite a lot, as it turned out. Last year I worked with a consulting firm near Raffles Place — six consultants, sharp team, serious clients. Their website had been built in 2021 for around $3,500. Template install, reasonable branding applied, nothing obviously broken.

When we actually looked at it, the problems were structural rather than cosmetic. There were no clear service descriptions — the kind of specific, scannable copy that tells a potential client within eight seconds whether they are in the right place. There were no case studies, no evidence of outcomes, nothing that would give a CFO or a managing director a reason to pick up the phone. The contact form was buried three clicks from the homepage, which in 2024 is roughly the equivalent of putting your phone number in the footnote of a printed brochure. On mobile, the site technically functioned but practically did not — text was small, CTAs were hard to tap, and the experience communicated, without saying it, that this firm did not think mobile visitors mattered.

The average session duration was 45 seconds. For a professional services firm where the typical engagement value is $35,000, 45 seconds is not a browsing pattern. It is a bounce.

Why do so many professional services firms have websites like this?

Because nobody measured what the website was not doing. This is the core of the problem, and it repeats across almost every sector I work in.

A business owner commissions a website, pays the invoice, and from that point forward evaluates the asset on what it cost, not on what it produces. If it cost $3,500 and it is still online three years later, it feels like money well spent. The absence of inbound enquiries does not get attributed to the website — it gets attributed to market conditions, to the sales team not following up fast enough, to LinkedIn not performing, to any number of other variables. The website sits quietly in the background, costing nothing obvious and delivering nothing measurable, and that invisibility is precisely why this pattern is so durable.

I have had this conversation with business owners in Singapore, in Sydney, in Auckland. The question is always the same: “How do we know the website is the problem?” The answer is usually to spend twenty minutes in Google Analytics together. Session duration under a minute. Bounce rate above 70%. Contact page visits that do not convert to form submissions. Once you see those numbers, the diagnosis is not complicated.

What does an $11,000 rebuild actually involve?

Eight weeks of work, in this case. Two of those weeks were content planning — sitting with their team, mapping their services properly, understanding how their best clients had found them and what had convinced those clients to get in touch. That content work is the part most cheap builds skip entirely, and it is the part that determines whether the finished site actually converts.

The remaining six weeks covered information architecture, design, development, and testing. We restructured the site so the services were front and centre, each with enough specificity to qualify a visitor before they made contact. We built out two case studies from work the firm had already done — they had the material, nobody had ever formatted it for the web. We moved the contact form to a prominent position and simplified it down to four fields. On mobile, we rebuilt the experience from scratch rather than relying on a responsive template to do the job for us.

At Chillybin we do this kind of work regularly for professional services firms, and the content planning phase almost always surfaces the same gap: the business knows exactly what they do and how well they do it, but none of that knowledge has made it onto the website in a form that means anything to a cold visitor.

How quickly did the numbers change?

Within three months, the results were measurable enough to be unambiguous. Enquiry form submissions doubled. Average session duration went from 45 seconds to 2 minutes and 40 seconds — that is not a marginal improvement, it is a different category of engagement. It means people are reading, not just arriving and leaving. Three new clients came in through the website during that period, and the firm could trace all three directly to website enquiries.

At their average engagement value of $35,000, three new clients represents $105,000 in revenue. The rebuild cost $11,000. By the time we reviewed the data at the three-month mark, the website had paid for itself several times over. The actual payback period, working backward from the first new client conversion, was under 60 days.

These are not exceptional numbers for a professional services firm with a clear offer and a functioning website. They are what happens when a site is built to convert rather than simply to exist.

Is there a way to calculate what your current website is costing you?

Yes, and the calculation is not complicated. Start with three numbers.

First, your average enquiry-to-client conversion rate. If you close 30% of qualified enquiries, you need that baseline. Second, your average client value. Third, your current monthly enquiry volume from the website specifically, not from referrals or outbound.

If your website generates two qualified enquiries per month, your close rate is 30%, and your average client value is $20,000, your website is producing $12,000 in annual revenue. If a rebuild converts four enquiries per month instead of two, it produces $24,000. The difference is $12,000 per year. A $10,000 to $15,000 rebuild pays for itself in twelve months and continues paying after that.

The reason most business owners do not run this calculation is that the current state feels like zero cost. The site is already built. It is already paid for. The hosting is $30 a month. What is there to spend? The answer is opportunity cost, which is real money even though it does not appear on an invoice. The consulting firm near Raffles Place had been running their 2021 template for roughly two and a half years before the rebuild. At three clients per quarter attributable to a functioning website, the old site had cost them somewhere in the range of $250,000 in missed engagements over that period. Against that number, $3,500 does not look cheap at all.

Should every business rebuild their website?

No. A rebuild makes sense when the underlying business has a clear offer, a defined audience, and an existing pipeline that a better website could accelerate. It does not make sense as a solution to unclear positioning or a product that has not found its market. A better website amplifies what is already there. It does not create demand from nothing.

It also makes sense to look at the data before assuming the website is the problem. Session duration, bounce rate, form conversion rate, and traffic source breakdown will tell you quickly whether the issue is the website itself or something upstream of it. Sometimes the traffic is fine and the site is not converting. Sometimes the site is fine and there is simply no traffic. Those are different problems with different solutions, and conflating them produces expensive misdiagnoses.

What I can say after 25 years of building and rebuilding websites is that the “we’ll fix it later” posture has a real cost. Later almost always means two or three years later, after the original site has been silently underperforming through what would otherwise have been a period of growth.

The $3,500 site was not the affordable option. It was the most expensive decision they made that year — they just could not see the invoice.