EMVALUE / Website cost guide

How much does a website cost in Australia?

Basic one-page websites for individuals and sole traders start from A$300. Larger websites, apps and business tools are quoted in writing after a short conversation, before any work starts. The useful question is what that price includes and which parts of your project need a separate scope. This guide explains the factors to discuss before comparing quotes.

1. The short answer and the basic scope

For individuals and sole traders, our basic one-page website starts from A$300. It is one scrollable page with up to six content sections, not a multi-page website at the same starting price. A clear section list helps you decide whether this scope is enough: introduce the business, explain services and show the information needed to contact you.

The basic scope includes layouts for phones, tablets and computers; contact options such as an enquiry form or phone, email or WeChat buttons; basic search settings consisting of a title, description and sharing image; launch on your domain and hosting account; and one round of revisions. The agreed contact method should match how you actually want to handle enquiries.

Domain and hosting charges, copywriting, photography, a second language, booking or payment connections and long-term maintenance are not included in that basic build. They can be quoted separately. This distinction matters when comparing a page price with a larger proposal: list the work and continuing costs included in each, rather than assuming the first number covers everything you may need.

Larger websites, apps and business tools are quoted in writing after a short conversation, before any work starts. Use the basic scope as a reference for defining your project, not as a fixed rate for every feature. Confirm the page list, responsibilities and boundaries first; the proposal then explains the deliverables, payment stages and ongoing costs you need to review.

2. What changes the work involved

Pages and design: a single introduction and a site with separate service, price, work and contact pages have different scopes. Decide what belongs on each page and whether the design needs to explain different kinds of information. A page list is more useful than simply asking for a small website, because it makes the proposed content and design work visible.

Functions: bookings, ordering, payments and forms introduce choices beyond displaying information. Explain what a visitor needs to do and which existing service you want to use. We can assess a connection to an established service and explain platform fees beforehand. Ask which setup work belongs to the build and which fees or operational tasks remain with the platform or business.

Content and photographs: identify who prepares service descriptions, prices, images and business details. A layout cannot make those facts accurate for you. If materials are not ready, list the missing items and agree whether content preparation is additional work. The basic one-page scope excludes copywriting and photography, so these responsibilities should be clear before comparing it with another quote.

Languages: a second version involves page correspondence, writing and review as well as a switch in the navigation. English and Chinese should carry consistent business facts while being written for their readers. Decide which pages need both languages and who maintains each version. A second language is outside the basic single-page scope, and its work should be described in the proposal.

System connections: if information must move between a website and an existing service, name that service and the required flow. Access, the information involved and the work to connect it need assessment before a commitment. A client portal or quote tool is a separate custom scope; do not assume that every connection is included because a proposal mentions a website.

An old-site migration: explain the current platform, account access and what should be retained. Moving a site can require a content review and an old-to-new address map with redirects. That is different from starting with an empty page. We assess the present site before recommending an update, redesign or migration, and include the agreed handling of existing addresses in the scope.

3. Costs that continue after the build

Domain and hosting are continuing cost categories rather than part of the basic build price. The domain and service accounts should be registered in your name. Ask which accounts you need, who manages them and how renewal responsibilities are handled. Keeping the build and these services separate in the proposal helps you understand what you are paying for after launch.

Paid tools and third-party platforms may also be part of the agreed arrangement for a booking, ordering or payment connection. Their fees are explained before you decide. This guide lists categories rather than quoting changing supplier prices. Review the proposed platform and its continuing charges alongside the setup work, and check which service account remains under your control.

Maintenance and later changes need an agreed arrangement or a separate quote. Decide what you intend to update yourself and where you need help. A price adjustment, new page or connection may fall outside the original build scope. Ask the proposal to explain ongoing responsibilities and what happens when requirements change, so maintenance is not confused with an unlimited extension of the project.

4. Choosing how to build

A self-built site can suit an owner who wants to prepare and maintain the pages directly and is comfortable making the layout and service choices. Consider the time you can put into content, setup and updates as well as the service fees. Decide whether that route fits the pages and functions you need; a low initial outlay alone does not define a complete scope.

A freelancer can be a suitable route when the work and communication arrangements match your project. A studio can also suit a business seeking agreed design, development and handover work. Those labels alone do not tell you what a quote includes. Compare the responsibilities, deliverables, review process and support boundaries that are actually written down, rather than assuming a label guarantees an outcome.

Whichever route you choose, explain the same page list, functions, languages and content readiness when requesting a quote. Ask how accounts are held and what is handed over. That makes differences easier to understand without naming competitors or relying on an unsupported market average. The useful comparison is between clear scopes that meet your needs and the work you are prepared to handle yourself.

5. How we prepare a quote

We begin with a conversation about your business, customers, current tools and the problem the website should solve. The result should be a scope you can review: pages, functions, content responsibilities and proposed delivery milestones. Timing depends on the pages, features and content readiness; milestones are set out in the written proposal rather than assumed from a generic launch deadline.

Before paid work begins, the written proposal explains deliverables, costs and payment stages. Compare those stages with the agreed review and delivery points, and ask about anything unclear. The proposal also separates continuing service costs and maintenance from the build, so the starting price does not hide work or responsibilities that need another decision. No universal payment percentage is assumed in this guide.

New requirements are confirmed before additional work starts. Explain the proposed change and discuss its effect on cost and timing against the original scope. This lets you decide whether to include it now or treat it as later work. A written change agreement is more useful than allowing the original page or feature list to grow without a shared understanding.

6. Prepare these details before asking

Write down your business name, service area, contact details and the information a visitor needs before making an enquiry. List the pages or up to six basic sections, and mark any content that is not ready. Include photographs and service descriptions you want to retain. Distinguish what you will supply from the writing or image work that would need an additional scope.

List the required actions: contact, bookings, ordering, payments or a particular form. Name existing tools and tell us what access is available. Note which languages customers need, who checks the business facts and who will maintain each version. If this is a redesign, provide the current address and say what still works. These details make the first conversation about actual work rather than an unexplained number.

Finally, explain your priorities, budget and any concept you want to discuss. Identify what must be in the first version and what can be considered later. We can use this preparation to clarify the scope and give a written proposal before work starts. You can begin through the project enquiry below; the purpose is to agree a useful build and understand its continuing costs.

Related pages

Website design and the basic scope

Discuss your website scope

Tell us your pages, functions, languages and what content is ready. We can clarify the work and prepare a written proposal.

emvalue.studio@gmail.com

Start a project →

Last updated: 2026-10-08