What 'website support' actually means — and what to ask before you sign

When you’re hiring a web designer, the word “support” gets used a lot. It’s on every quote. It’s in every email. “And of course we offer ongoing support after launch.”

The trouble is that “support” means wildly different things to different designers, and the difference is usually not visible until six months in.

For one designer, “support” means: I’ll respond to emails when I have time, fix urgent things if I can, and quote you separately for any actual work. For another designer, “support” means: I have a specific monthly retainer with a specific scope, a defined response time, and a defined list of what’s included. Same word; completely different products.

This post is a walk-through of what good website support actually looks like, what bad website support looks like, and the questions to ask before you sign anything so you know which one you’re getting.

What “bad” support looks like

The default version of website support in the Melbourne small business market is what I’ll call “passive availability”.

It usually sounds like one of these:

• “We’re here if you need us — just reach out.”
• “We offer ongoing support at our standard hourly rate.”
• “After launch, we’re available to help with any changes you need.”

These all sound reassuring. None of them are actually products. They’re vague offers of availability with no defined scope, no defined response time, and no commitment to actually doing anything on a regular cadence.

What happens with passive availability in practice:

• Month 1: Designer responds fast. Easy stuff. You feel looked-after.
• Month 3: Reply takes 4 days. Small text change takes a week. Designer is working on another launch.
• Month 6: You ask about why bookings have dropped. Reply says “could be a few things, want to book a paid hour to look into it?” You decide to wait and see.
• Month 9: You’ve stopped emailing. The site is sitting in the same state it launched in. No improvements have been made. No updates. No content. The investment is depreciating.

This isn’t bad-faith on the designer’s part. It’s the predictable outcome of a relationship that was never structured as anything other than “be available”. When availability is the product, the product erodes.

What “good” support actually looks like

Good website support is a recurring, scoped, priced service that does specific things on a specific cadence. Not “we’re available” — but “this is what we do every month, for this price, with this response time”.

A real support retainer has, at minimum:

• A monthly price. Not “billed hourly when needed” — a fixed monthly fee. The fee structures the commitment on both sides.
• A scope. What’s specifically included each month? (e.g., “security patches and platform updates”, “monthly site check across browsers”, “up to 60 minutes of small content updates”).
• A response time. How fast does the designer reply to a support request? (Same business day is the standard; 4 hours for urgent issues; 24 hours for everything else.)
• A “what’s not included” list. What constitutes new work outside the retainer? (New pages? Big design changes? Functional features?) And what’s the rate or quote process for those?
• A cancellation policy. Most should be month-to-month, cancellable with 30 days’ notice. Anything with a 12-month lock-in is a flag.

Beyond that minimum, the better retainers add proactive work — things the designer does without you asking, because they should be done:

• Monthly site health check. Speed, mobile, broken links, plugin updates. The designer catches issues before you notice them.
• Backup verification. It’s not enough to have backups; you have to verify they actually work. Most “backups” have never been tested.
• A small monthly improvement. A copy refinement, a new section, a tightened CTA. Sites that get small improvements monthly drift forward; sites that don’t get touched drift backward.
• A quarterly review. Where are we? What’s working? What’s not? What should we focus on next quarter?

That’s the floor of what “support” should actually mean. Anything that doesn’t have these elements isn’t a support product — it’s just availability with a label.

The three tiers of support that make sense for a small business

Most small business sites need one of three tiers, depending on what the website is doing for the business. (These are rough categories; my own retainer structure follows this pattern, but the categories generalise.)

Tier 1: Maintenance (~A$200–A$350/month)

This is the floor. What you absolutely need.

What it covers:

• Security updates (platform patches, certificate renewals, plugin updates if applicable)
• Backups + verified restore capability
• Monthly site health check (speed, mobile, broken links)
• Up to 30–60 minutes of small content updates per month (text edits, photo swaps, hours changes)
• Email support with same-business-day response

What it doesn’t do: new pages, design changes, SEO improvements, content creation.

Right for: small businesses where the website is brochure-style and doesn’t change much month-to-month. Tradies, cafés, salons where Instagram/GBP is doing more of the marketing work than the site is.

Tier 2: Growth (~A$500–A$800/month)

This is what you need when the website is actually one of your marketing channels — not just a brochure.

What it covers (in addition to maintenance):

• A monthly blog post or content piece written and published
• Monthly SEO improvements (suburb pages, condition pages, schema, internal linking)
• Google Business Profile maintenance (the weekly post + photo + review response routine)
• A monthly performance report you can actually read (not 47-page PDF — a 1-page summary of what’s moving and why)
• Up to 2 hours of design/structural work per month (new sections, improved CTAs, etc.)

What it doesn’t do: paid advertising management, full redesigns, custom development beyond the retainer hours.

Right for: established small businesses where the website should be doing real customer acquisition work. Clinics, professional services, growth-stage cafés, multi-location trades.

Tier 3: Partner (~A$1,500–A$2,500/month)

This is for businesses treating the website as a meaningful marketing function rather than a sometime asset.

What it covers (in addition to growth tier):

• More content (weekly, not monthly)
• Paid acquisition strategy and management (Google Ads, Meta if relevant)
• Conversion rate optimisation (running tests on the site to improve booking rates)
• Quarterly strategic reviews with the owner
• A larger pool of design/dev hours per month

Right for: established businesses making A$500k+ ARR where the website is the primary channel.

The seven questions to ask before signing a support agreement

Before you sign anything that includes “ongoing support”, ask the designer these seven questions. Take notes on what they say. The pattern of answers tells you whether the support product is real or a label.

1. “What’s the monthly fee and what specifically is included?” A clear answer here with a real list = good. “It varies based on what you need” = not actually a product.

2. “What’s the response time when I email a support request?” Same business day is the standard. 24 hours is acceptable. “When I can” is a non-answer.

3. “What’s the process if I have a true emergency — site down, contact form broken, payment widget failing?” A real answer involves a phone number or escalation path. No real answer = no plan exists.

4. “What happens proactively each month — what do you do without me asking?” This separates real support from passive availability. If the answer is “nothing — we wait for your requests”, that’s not a support product. That’s hourly billing with a different label.

5. “What kinds of work fall outside the retainer, and how are those priced?” A clear answer (e.g., “new pages are quoted at A$400 each, larger design changes are A$120/hour”) = transparent. Vague answer = you’ll be surprised by invoices.

6. “Is this month-to-month, or is there a minimum term?” Month-to-month with 30 days’ notice is the modern standard. Anything with a 12-month minimum without a meaningfully discounted price is a flag.

7. “Can you show me what a typical month’s report looks like for an existing client?” The good designers have an actual report template they’ve used dozens of times. The bad ones either don’t have one or it’s vague. The report quality is usually a proxy for the work quality.

If a designer can answer all seven of these with specific, real answers — you’re talking to someone who actually runs a support product. If three or more of the answers are vague, you’re talking to someone who offers availability with a “support” label, and the relationship will erode within 6 months.

The honest version: what support is really worth

The reason this matters is that the cost of not having real support is invisible until it’s too late.

A small business website that gets no real attention after launch depreciates. It gets slower (over 18 months, typically losing 1–2 seconds of mobile load time as content gets added without optimisation). It gets stale (the services list never matches what you actually offer now). Its SEO rankings slide as competitors keep adding content and you don’t. The booking widget breaks one Thursday and you don’t notice for three days. The contact form starts sending spam to your inbox because the spam filter expired.

None of these are visible as line-items in a budget. They’re invisible degradation. Most small businesses I look at have lost meaningful revenue to invisible degradation without ever realising it.

A real support retainer at A$200–A$700/month is a small line item on the spreadsheet. The work it does is the difference between a site that compounds over years and a site that depreciates from launch day. Over five years, real support is cheaper than the invisible cost of letting the site rot — by a long way.

The mistake isn’t paying for support. The mistake is paying for support that’s actually just availability with a label. For the wider read on how the post-launch relationship fits into the bigger picture of hiring and working with a designer, the complete guide to working with a Melbourne web designer is the broader reference.

---

If you’d like a read on what level of support your specific business actually needs — and whether what you’re currently paying for matches that — book a 15-minute call. I’m honestly happy to tell you “you’re paying too much” or “you’re paying for something you’re not getting” if that’s what the answer is.

Or if you want to see what your site looks like in its current state of attention vs. neglect, run the free audit — the report flags the obvious symptoms of underused support.