Ask about ownership before work begins
Confirm who will own the domain, hosting account, website content and custom code covered by the agreement. Businesses should retain access to core accounts. If a provider registers a domain on the client's behalf, the arrangement should not make future transfer unnecessarily difficult.
Ask which third-party services require separate subscriptions and whose account will hold them. This avoids surprises when a relationship ends or a renewal is due.
Compare process and evidence, not only sales claims
Review current live work and look for projects relevant to the required complexity. A company experienced with informational sites may not automatically be the right choice for a custom booking system, and the reverse is also true. Ask how requirements, content, testing and approvals are handled.
For projects that extend beyond presentation into software behaviour, a development-focused Canadian website illustrates the distinction between general website work and application engineering.
Be cautious with guarantees that depend on third parties, especially guaranteed search positions. A provider can control implementation and effort, but not promise how an external search engine will rank a page.
Understand maintenance and exit options
Ask what support is available after launch, how urgent issues are handled and whether updates are included or billed separately. For CMS sites, clarify responsibility for software updates and backups.
A professional arrangement should also make it possible to change providers. Documentation, account ownership and access to website files or repositories reduce unnecessary dependence on one supplier.
Ask how the provider handles content and approvals. Some companies expect finished copy before work starts; others include research and writing. Neither model is automatically better, but the responsibility should be explicit. The same applies to photography, accessibility review, analytics and search setup. A proposal becomes easier to compare when each party knows which deliverables are included instead of assuming that the phrase website project covers every related task.