Page and content requirements
Page and content requirements is scoped around your requirements, existing systems and the outcomes the project needs to support.
Practical guidance
How much does a website cost in Australia?
Website cost depends on the job the site needs to do. A small information site has different needs from a content-heavy website, an online store or a custom platform connected to business systems.
A practical guide
Start with the real need. Build the right solution.
We do not present a single price as suitable for every project. The online estimator currently uses GBP, so Australian businesses should share their preferred AUD budget when requesting a proposal. The written proposal should confirm the currency and what is included.
We keep the process practical: understand the context, identify dependencies and risks, agree the first useful outcome and plan how the work will be tested and supported.
- Page and content requirements
- Design and accessibility needs
- eCommerce and payment workflows
- Integrations, migration and testing
- Hosting, licences and ongoing care
Scope and capabilities
The key parts of a well-planned project.
The exact scope depends on your users, existing systems and business rules. These are the areas we review together.
Design and accessibility needs
Design and accessibility needs is scoped around your requirements, existing systems and the outcomes the project needs to support.
eCommerce and payment workflows
eCommerce and payment workflows is scoped around your requirements, existing systems and the outcomes the project needs to support.
Integrations, migration and testing
Integrations, migration and testing is scoped around your requirements, existing systems and the outcomes the project needs to support.
Hosting, licences and ongoing care
Hosting, licences and ongoing care is scoped around your requirements, existing systems and the outcomes the project needs to support.
How we work
From clear scope to supported delivery.
A straightforward process keeps decisions visible and gives everyone a shared view of progress.
Clear ownershipVisible progressPlanned handover
01PHASE 01
Understand the need
Describe the outcome and audience
02PHASE 02
Agree the scope
List key pages and required features
03PHASE 03
Build and review
Identify integrations and content needs
04PHASE 04
Prepare handover
Review scope, assumptions and support
Questions and answers
Questions to consider before you begin.
The best approach depends on the requirements and constraints of each project.
Ask something else →01How do we get started?
Share the business goal, what exists today and the most important requirements. We will review the context and identify what needs to be clarified before a scope or estimate can be confirmed.
02Can you work with an existing platform or team?
Yes. We can review an existing system and work alongside internal teams or other partners. Access, responsibilities and handover are agreed before delivery.
03Is the online estimate a fixed quote?
No. The online estimate is an indicative planning range. A written proposal follows a review of requirements, dependencies and assumptions.
Plan the next step
Have a project to build or improve?
Tell us what you are trying to achieve and what you need the software to do. We will help identify a practical next step.
Discuss your project ↗