When do the 48 hours start?
When we have your final content, brand assets and access to any accounts or domains the site touches. Our terms state that late or incomplete materials extend delivery.
How We Build Your Website in 48 Hours
The four steps of a standard website build, what we need from you at each one, and what usually causes delays.
These steps and day counts describe standard website builds. Web apps, mobile apps, SaaS platforms and custom software follow a schedule agreed in writing.
The 48 hours are counted in business hours across business days, excluding weekends and Victorian public holidays. They start once we have your content, brand assets and access.
Step 1
Brief
Before day 1Send your brief by email or through the contact form: what the site needs to do, who it is for and the pages you need. A short call is available if you prefer. We reply with a written scope.
What's included:
- What the site needs to do
- Who it is for
- Pages and features
- Sites you like, and why
- What we need from you
- A brief covering what the site is for, who it serves and the pages you need.
- What usually delays it
- A brief that leaves the site's purpose open. We settle it with questions in writing before we scope.
Step 2
Design
Day 1We lay out the pages agreed in scope, starting with the phone layout. You see the structure and visual direction before development starts.
What's included:
- Page layouts
- Mobile-first design
- Brand colours and type
- Clear calls to action
- What we need from you
- Brand assets, logo files, and examples of sites you like or dislike.
- What usually delays it
- A logo that is not yet in a usable format.
Step 3
Development
Day 1-2We build the pages, responsive layouts, forms and analytics, with the content in the served HTML so search engines and AI assistants can read it. Integrations named in the scope are connected and tested before launch.
What's included:
- Clean, fast code
- Technical SEO foundations
- Contact forms
- Analytics setup
- What we need from you
- Final copy, images, and access to any third-party accounts the site connects to.
- What usually delays it
- Content arriving in pieces, and third-party APIs that behave differently from their documentation.
Step 4
Launch and handover
Day 2We deploy the site, check it at real phone, tablet and desktop sizes, and show you how to manage it. Unless your project document includes ongoing support, maintenance or hosting, the engagement ends at handover and later changes are quoted separately.
What's included:
- Live deployment
- SSL certificate
- Training walkthrough
- Handover
- What we need from you
- Approval, and your hosting preference if you have one.
- What usually delays it
- Domain access, when nobody has the login for the domain.
Start with a brief
Send us a brief or book a call, and we will set out the scope, timeline and cost in writing.
Before you start
Questions that decide whether a build runs to time.
What do I need to have ready before you start?
Final copy for each page in scope, your logo in a vector or high-resolution format, any photos you want used, and login access to your domain and connected accounts. If you do not have copy, tell us in your brief so it can be planned. A list of sites you like, and what you like about them, usually saves a revision round.
What if my content isn't ready?
Then the 48 hours have not started, and we will tell you. You can narrow the scope to the pages you can fill now, build around placeholder content that you replace before launch, or add copywriting to the scope.
How many rounds of changes do I get?
The number of revision rounds is set in your project document. Extra rounds, and changes to something you have already approved, are quoted separately. Our terms treat a deliverable as accepted when you approve it in writing, or five business days after delivery if no revisions are raised.
Who writes the content?
By default you do, because you know your business and your customers best. Copywriting can be added to the scope and quoted like any other work.
Do I need to be available during the build?
Only at three points: sending the brief, approving the design direction, and a final check before launch. A reply within a working day at each point keeps a 48-hour build on schedule.
More answers on scope, hosting and SEO are on our FAQ page.