The questions worth asking any studio before you hand over a project: who you are contracting with, what you end up owning, what happens when something goes wrong, and how you leave if you want to. The company details below can be verified on the public register rather than taken on trust.
For questions about the work itself — support, hosting, security, migrations and integrations — see the service FAQ.
Is GetQuickSites a real company?
Yes. The legal entity is GETQUICKSITES PTY LTD, an Australian private company registered with ASIC. The ABN is 82 690 212 474 and the ACN is 690 212 474. The ABN has been active on the Australian Business Register since 20 August 2025, and the registered business location is Melbourne, Victoria 3000. Every one of those details can be checked independently at abr.business.gov.au by searching the ABN, without taking our word for any of it.
How much does a website cost? A web app? A SaaS platform?
We do not publish prices, because those three words describe very different builds. A brochure site of a few pages, a web application with accounts and permissions, and a multi-tenant SaaS platform with billing and tenant isolation are separate engineering problems with separate costs. Each project is quoted against a written scope after a free consultation, so the figure reflects what you actually need. The scope document lists what is included before any work begins.
Is 48 hours realistic, and what does it actually mean?
It applies to standard website builds, and the clock starts when we have your content, brand assets and any access we need, not when you first make contact. Within that window we build and deploy the site. It does not apply to web applications, SaaS platforms, migrations or custom software, which are scoped individually with their own timeline in the project document. If your content is not ready, the clock has not started, and we will say so.
What happens if the project runs late?
We tell you, with the reason and a revised date, rather than letting a deadline pass in silence. Slippage usually traces to something specific: content that has not arrived, a third-party integration behaving differently from its documentation, or a scope change agreed mid-build. Our terms set the remedy where we fail to deliver and the failure is ours: a refund of fees paid for the undelivered work, less the value of anything already accepted and third-party costs incurred.
Who owns the code and the data?
On full and final payment, ownership of the deliverables built specifically for you transfers to you: the custom code, the design and the content we produce for your project. Until payment is complete we retain them. Reusable components and tooling we bring to every engagement stay ours, and you receive a perpetual licence to keep using them as part of your build, with nothing further to pay. Your content and your business data are yours throughout.
What if I want to leave or take it elsewhere?
You take it with you. Ask and we hand over the repository, the deployment configuration, the database and the accounts we hold for you, and we stay reachable long enough for your next developer to ask questions. There is no exit fee, and nothing is deliberately structured to make leaving difficult. We build on ordinary, widely used technology precisely so another developer can read it. If you are comparing studios, ask each of them this question.
How do you handle client data and AI features?
We ask for access only where the work requires it, and your data stays in the systems we build for you. Where a project includes AI features, the scope names which provider processes what, so you can decide before anything is built rather than discovering it afterwards. We do not feed your customer data into a model to improve it, and we do not reuse one client's material for another. If data would leave Australia, that is stated in the scope.
Can I see examples of your work?
On request, and directly rather than through a public gallery. Much of our work is commissioned by businesses who would rather their build was not discussed publicly, so we do not publish client names, logos, or results we cannot evidence. Ask for examples relevant to what you are building and we will walk you through them on a call. If a studio shows you a portfolio full of percentages, ask what was measured, over what period, and who verified it.
What don't you do?
We do not guarantee rankings, traffic, leads or conversions, and our terms say so, because search engines decide those and no provider controls them. We do not buy links or use paid link schemes, which breach search engine guidelines and put a site at risk. We do not publish case studies or client results we cannot evidence. And we do not quote a brochure site as though it were a platform, or take on work we cannot staff properly.
How do payments work?
Payment terms are set in your project document rather than applied from a standard schedule. Our terms describe the common shape: a deposit before we start, typically half the project fee, with the balance due on completion before handover or go-live. Some projects are milestone-based instead, and some are paid in advance. Deposits and amounts covering work already performed are non-refundable. You will know the exact structure for your project before you commit to it.