Start with the job the site needs to do
A one-page introduction and a five-page service website are different products. Write down the main action you want visitors to take: call, enquire, view a menu or open an existing booking system. Then identify the information they need before taking that action. A low price is useful only when it covers the work you actually need.
Make content work explicit
Agree who supplies text, photos, prices and business details. Basic editing is different from writing all the copy, photographing a location or entering a large menu. Specify image quantities and who confirms accuracy and permission. A bilingual website needs both versions checked; automatic translation is not finished content.
Ask what a revision means
A consolidated revision round collects feedback into one agreed list. It is not unlimited new pages or a complete change of direction. Ask how extra work is quoted and what happens when materials arrive late. Agree payment milestones and acceptance before development begins.
Separate ownership from ongoing care
A proposal should explain domain ownership, hosting access, source or export handover, licenses and portability. A care plan pays for defined work, not ownership of your domain. Ask what happens when you cancel and whether migration or training costs extra. List optional care and third-party fees separately.
Use prices as scoped starting points
Our pricing page lists independent introductory packages in CAD and USD. The written proposal confirms scope, taxes, content volume and subscriptions. A CMS edits content; it is not automatically a booking system, CRM or store. Bring your existing tools to the discussion so useful systems are not rebuilt unnecessarily.