How a build runs, what it includes, what happens to the site afterwards, and how search work is measured.
Questions about the company, ownership, client data and what we do not do are answered in the company and engagement FAQ.
Send us a brief by email or through the contact form, or book a short call if you would rather talk it through. We then set out the scope in writing, including what is included, what is not and the timeline, for you to read before anything is agreed.
The 48 hours apply to standard website builds and cover the build and deployment, counted in business hours across business days, excluding weekends and Victorian public holidays. The clock starts once we have your content, brand assets and access, and our terms treat 48 hours as a good-faith target rather than a guarantee. Web apps, SaaS platforms, migrations and custom software follow a schedule agreed in writing.
We tell you, with the reason and a revised date. Delays usually come from content that has not arrived, a third-party integration that behaves differently from its documentation, or a scope change agreed during the build. Our terms set out the remedy if we fail to deliver and the failure is ours.
Each project is quoted against a written scope after a free consultation, because a website of a few pages, a web application with accounts and a multi-tenant SaaS platform are different builds with different costs. The scope lists what is included before any work begins. Our pricing page explains how we quote. Our guide to website costs explains what drives the price of a website.
What is included is listed in your scope before the build starts. A build covers the agreed pages, responsive layouts, the technical foundations search engines need, and deployment. Pages or integrations added later are quoted separately.
Usually, yes. Some sites are delivered with a content management system so you can edit text, images and pages yourself, and others route changes through a developer. Tell us before the build if editing the site yourself matters, because it is decided at scoping.
Yes. We are a Melbourne software and web development studio and work with businesses across Australia over video calls, shared documents and email. The process is the same wherever you are.
Yes. Layouts are built responsively for phones, tablets and desktops, with readable text, usable tap targets and images sized for mobile data. We check each build at real phone, tablet and desktop sizes before handover.
We use widely used, well-supported technology, so another developer can pick up your project and read it. The stack depends on what the project needs and is named in your scope before the build begins.
Hosting can be arranged as part of a project, but it is not included automatically. Our terms treat domain registration, hosting and similar third-party costs as yours, so the hosting account and the relationship with the provider stay with you. Any ongoing hosting arrangement is written into your project document.
Sites are built with encrypted connections, dependencies that are current at handover, careful handling of credentials, and forms that validate what they accept. Security after handover depends on whether your project document includes an ongoing arrangement. Without one, our engagement ends at handover and later work is quoted separately.
Yes, from website builders, WordPress or custom systems. We map the existing URLs to the new structure and set up redirects before the switch, so the search visibility the old site has earned carries across where it can.
The backup arrangement depends on where the site is hosted and what your project document specifies. The code for projects we build lives in a repository you own, so the site can be rebuilt from source. Databases and uploaded content need a stated backup policy, which we raise during scoping.
Usually, yes: CRMs, booking systems, payment processors, email platforms and similar. Each integration is scoped individually, because the effort depends on the quality of the other system's API. We do not control third-party platforms, and our terms say we are not responsible if they change or go offline.
Yes, on a hosted platform such as Shopify or as a custom build where the catalogue, checkout and fulfilment match how you trade. Which suits you depends on your margins, your catalogue size and how far your process differs from a standard store. Payment processing is handled by a payment provider, and its fees are yours.
Traditional SEO works to rank a page in a list of links, while AI SEO, also called answer engine optimisation, works so an AI assistant can quote your site inside a generated answer. The foundations overlap: crawlability, page speed, clean structure and valid structured data. AI SEO adds crawler directives for AI agents, entity consolidation, and passages written to be quoted on their own. Our AI SEO explainer defines AEO and GEO.
Search engines control ranking and indexing timelines, so we do not put a date on results. The work itself can be checked straight away: whether pages are crawlable, structured data is valid and content is in the served HTML. How quickly that shows in rankings depends on the site's starting point, its competition and how often search engines recrawl it.
No. Google's guidance on hiring an SEO says to be wary of anyone who guarantees a number one ranking, and our terms state that we do not guarantee rankings, traffic or leads. We provide documented technical work on the parts of your site you control, with a record of what changed.
Yes. Local search depends on consistent business details across the directories that list you, a complete Google Business Profile, location pages with specific content, and reviews. Most fixable problems are small inconsistencies, such as an address or phone number that differs between listings.
By a record of what changed: technical work completed, structured data validating, content in the served HTML, and crawl and index status. Position and traffic data come from Google Search Console and your analytics, reported alongside the work.
Unless your project document includes ongoing support, maintenance or hosting, our engagement ends at handover and later changes are quoted separately. Ongoing work can be scoped like any other engagement.
Yes. A short handover session covers how to edit content, where things live and what needs a developer. Ask for it early so the training sits inside the project scope.
Our terms are on the terms page, and the build process is set out on how it works. Longer guides on cost and on choosing a provider are on our blog.
Ask us directly and we will answer in writing.
