How many questions should I actually ask before signing?

Fewer than a full checklist, if the quote itself already answers most of them in writing. Ask the ones a written quote left silent — that silence is usually where the risk sits.

Should I ask these questions by email rather than on a call?

Ask on a call if you like, but get the answers restated in writing afterwards. A verbal answer is not something you can point to later if the outcome does not match what was said.

Questions to ask a web designer before you sign

A short list of direct questions, asked before a deposit is paid, resolves almost every dispute this site sees described after the fact. None of them requires legal knowledge to ask. What they require is asking them before you are committed, because every one of them is far easier to negotiate before money has moved than after.

The questions to ask a website designer, and why each one matters

Abstract illustration of a list of questions, shown as a numbered column of small question-mark glyphs, evenly spaced.

Question	What a good answer sounds like	What it protects against
What exactly is included in this price?	A written list of pages, features and what’s excluded	Scope disputes — the single largest source of conflict
How many rounds of revisions are included, and what counts as one?	A specific number, with a definition of a “round”	Open-ended revision demands on both sides
Who writes the content, and what happens if it’s late?	A clear owner for copy and photos, and a stated effect on timeline	Stalled projects with no one accountable
What is the payment structure?	Staged payments tied to defined milestones, not one lump sum up front	Losing all leverage if work does not arrive
Who will hold the domain and hosting accounts?	Your business, by name, as registrant	Losing control of your own domain
Do I own the code, design files and copyright once I’ve paid?	A clear yes, in writing, on final payment	Being locked into one supplier for every future change
What happens if either of us wants to end this early?	A stated position on partial payment and handover of work-to-date	An acrimonious, undocumented exit
What is not included that I might assume is?	A specific, named list — hosting, SEO, ongoing support, stock imagery licensing	Surprise costs after signing
Can I see a live site you’ve built, not a screenshot?	A URL you can visit today	Unverifiable claims about past work
What happens after launch — is there a warranty period?	A stated number of days and what it covers	Being charged immediately for bug fixes that should be covered

The three that matter most if you only ask three

Abstract illustration of the three priority questions, shown as three glyphs highlighted in the gold accent among a larger muted set.

If time is short, ask about scope, payment structure and ownership. Scope disputes are the most common source of conflict because “included” means different things to each party until it is written down. Payment structure determines how much leverage you retain if things go wrong — a staged structure keeps you in the conversation; full payment up front does not. And ownership determines whether you can ever leave this supplier without starting from nothing, covered in full on who owns your website.

Ask before the quote, not after it

Some of these questions are best asked before a formal quote is even produced, because the answers change what the quote should contain. “What’s included” and “what’s excluded” in particular should shape the document you receive, not be discovered by reading between its lines. What a complete quote should state on its own, without you having to ask, is set out on what should be in a website quote.

Get the answers in writing

Abstract illustration of getting answers in writing, shown as a document icon with a small pen resting across it.

A verbal answer on a call is a reasonable way to have the conversation, but ask for the substance to be restated in the written quote or contract afterwards. This is not distrust — it is the same discipline a supplier should want from their own side, because a written record protects both parties if memory of the conversation later diverges. Under the Australian Consumer Law, consumer guarantees attach to services regardless of what is or is not in writing, but a written record of scope and price is what a dispute actually gets resolved against in practice.

What a good supplier or web design firm does with these questions

A supplier confident in their process will usually answer most of this list unprompted, because it is exactly the information a competent quote should contain. Hesitation, vagueness, or irritation at being asked is itself useful information — see red flags when hiring a web designer for the specific patterns worth treating as a stop sign rather than a quirk. Whether a designer works in-house or outsources the photography, copywriting or the portfolio pieces they show you is itself worth asking about, since a portfolio built entirely from outsourced or templated work answers a different question than the one you asked.

What to do next

Abstract illustration of a next step, shown as a simple signpost icon with one arm.

Write these ten questions down and take them into your next supplier conversation, whether that is a first call or a formal proposal review. Ask the ones the written material has not already answered, and treat a reluctance to answer any of them plainly as data rather than as rudeness to be excused.

Turning the scope questions into a document a supplier can actually quote against is what the project brief generator is for — it forces the same specificity this list asks of a supplier’s answers.