How can you deliver a website in 48 hours?
The 48 hours covers build and deployment, and it starts once we have your content, brand assets and access, not when you first enquire. We work from a scope agreed before the build, so the time goes into building rather than deciding what to build. Our terms are explicit that 48 hours is a good-faith target and estimate rather than a contractual guarantee, and that late or incomplete materials extend it. Larger projects are scoped with their own timeline instead.
What is included in a website build?
What is included is listed in your project document before the build starts, because a five-page site and a twenty-page site with integrations are different jobs. Broadly, a build covers the pages agreed in scope, responsive layouts, the on-page technical foundations search engines need, and deployment. Anything outside that list, including pages or integrations added later, is quoted separately rather than absorbed silently. Ask for the scope in writing before you commit, and read what is excluded.
Can I update the content myself?
Usually yes, and how depends on what we build. Some projects are delivered with a content management system so you can edit text, images and pages without touching code. Others are built as static sites where changes go through a developer. Which approach suits you is a scoping decision rather than a default, and it is written into the project document. If editing the site yourself matters to you, say so before the build, because it changes how the site is put together.
Do you work with businesses outside Melbourne?
Yes. We are based at 220 Collins Street in Melbourne and work with businesses across Australia. Most of the work happens over video calls, shared documents and email, which suits both sides better than travel does. Being in the same city has not been a requirement for a web project for years. If you are in Melbourne and would rather meet in person for a larger project, that can be arranged; otherwise the process is the same wherever you are.
How do I get started?
Book a call or send the details through the contact form. The first call is free, and its purpose is to work out what you actually need, which is often narrower than people expect. After that we put the scope in writing: what is included, what is not, the timeline, and the payment structure, so you can read it before committing to anything. Nothing is charged until you have agreed a written scope and a project document.
Will my website work properly on phones?
Yes. Sites are built responsively, so layouts adapt to phones, tablets and desktops rather than being designed for a desktop and shrunk to fit. Mobile is usually where most traffic arrives, so it is treated as a primary case rather than an afterthought. That covers tap targets, text readable without zooming, and images sized so a phone on mobile data is not downloading desktop-sized files. We check the build at real viewport sizes before handover rather than assuming.
What do you build with?
We build with widely used, well-supported technology rather than anything proprietary, so another developer can pick your project up and read it. The specific stack depends on what the project needs, since a content-led site, a web application with accounts and permissions, and a multi-tenant platform have different requirements. Whatever we use is named in your scope before the build begins. Open-source components keep their own licences, which is normal and is set out in clause 7.3 of our terms.
Do you provide hosting?
Hosting can be arranged as part of a project, but it is not automatically included. Our terms treat domain registration, hosting and similar third-party costs as yours, and any ongoing hosting arrangement has to be written into your project document rather than assumed. The practical effect is that you hold the hosting account and the relationship with the provider, so nothing switches off if you stop working with us. We will tell you what your project needs and what running it costs.
What about website security?
Sites are built with the protections a modern site needs: encrypted connections, dependencies current at the point of handover, sensible handling of credentials, and forms that validate what they accept. Security is not a state you reach once though, it is maintenance. What happens 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, which clause 13.2 of our terms states directly.
Can you migrate my existing website?
Yes, migrations are routine work, whether from a website builder, WordPress, or a custom system. Most of the effort goes into the things that are easy to lose: existing URLs, redirects, page content, and whatever search visibility the current site has earned. A migration that changes every URL without redirects can undo years of ranking, so mapping the old structure onto the new one happens before anything is switched over, not afterwards when the traffic has already gone.
Do you provide backups?
What backup arrangement exists depends on where the site is hosted and what your project document specifies. Most modern hosting includes some form of snapshot or restore, and the code for projects we build lives in a repository you own, so the site can be rebuilt from source. Databases and uploaded content are the part that genuinely needs a stated backup policy, and that is a scoping decision we will raise rather than leave implied and discover later.
Can you integrate third-party tools and APIs?
Usually yes: CRMs, booking systems, payment processors, email platforms and similar. What determines the effort is the quality of the other system's API and whether it behaves the way its documentation says, which is not always the same thing. Integrations are scoped individually for that reason. Our terms note that we do not control third-party platforms and are not responsible for them changing or going offline, which is worth understanding before a project depends heavily on one.
Can you build an online store?
Yes. That can mean a hosted platform such as Shopify, or a custom build where the catalogue, checkout and fulfilment logic match how you actually trade. Which is right 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 rather than by us, and their fees are yours. If a platform would serve you better than a custom build, we will say so.
What is AI SEO, and how is it different from regular SEO?
Traditional SEO works to rank a page in a list of links. AI SEO, also called answer engine optimisation, works so an assistant can quote your site inside a generated answer. The foundations overlap almost entirely: crawlability, page speed, clean semantic structure, valid structured data. What is specific to AI SEO is crawler directives for AI agents, entity consolidation so the business is recognised as one thing, and passages written to survive being quoted on their own.
How long does it take to see SEO results?
Search engines control ranking and indexing timelines, so no provider can put a date on it and we do not. What is verifiable immediately is the work itself: a page is either crawlable or it is not, structured data is either valid or it is not, content is either in the served HTML or it is not. How quickly that shows up in position depends on the site's starting condition, its competition, and how often search engines recrawl it.
Do you guarantee first page Google rankings?
No, and no provider can. Google's own guidance on hiring an SEO says to be wary of anyone guaranteeing a number one ranking or claiming a special relationship with Google. Our terms say the same thing: clause 14.1 states we do not guarantee any particular commercial outcome, including search rankings, traffic or leads. What we provide is documented engineering work on the parts of the system you control, and a record of exactly what changed and why.
Can you help with local search?
Yes. Local search is a different problem from general ranking. It turns on consistent business details across the places that publish them, a properly configured Google Business Profile, location pages that say something specific rather than one paragraph with the suburb swapped, and reviews. Most of the fixable problems are consistency problems, where an address or phone number differs slightly between listings. It is unglamorous work, and it is usually where the improvement actually comes from.
How do you measure SEO work?
By what actually changed, not by a chart that moves on its own. That means a record of the technical work completed, structured data validating, content reaching the served HTML, and crawl and index status. Alongside that sits position and traffic data from Google Search Console and your analytics, which is Google's reporting rather than ours. We would rather show you what was done and let the search data sit next to it than present movement as proof of causation.
What happens after launch?
Unless your project document includes an ongoing support, maintenance or hosting arrangement, our engagement ends at handover and later changes are quoted separately. That is clause 13.2, and it is stated plainly so nobody assumes an open-ended retainer that was never agreed to. If you do want ongoing work, it is scoped like any other engagement. Either way you leave with the code, the accounts, and the ability to take the project to another developer without asking us.
Can you train my team to manage the site?
Yes, and it is worth asking for. A short handover session covering how to edit content, where things live, and what not to touch prevents most of the support requests that follow a launch. If the build includes a content management system the training covers that; if it does not, the session is about what you can safely change and what needs a developer. Raise it early and training can sit inside the project scope rather than being billed afterwards.
