In this article
A strong portfolio can show that an agency makes attractive websites. It cannot tell you who will own the finished site, whether online orders reach the right person or how an ordinary update will be handled after launch.
When choosing a website design company in Canada, compare the complete operating arrangement as carefully as the visual work. Ask Graby the same practical questions you would ask another provider.
Define the business task before requesting a quote
List what customers must be able to do: understand services, request a quote, book, buy or get support. Identify integrations and the people who maintain the information. Explain what is failing on the current site.
A hypothetical restaurant needs to verify ordering, notifications, pickup times and stock behaviour. A beautiful homepage does not compensate for an order that never reaches the kitchen.
Compare scopes on the same basis
| Area | Question to ask |
|---|---|
| Content | Who writes, supplies and approves it? |
| Design | Which page types and responsive states are included? |
| Development | Which integrations and functional journeys are tested? |
| Migration | How are URLs, content and existing data protected? |
| Support | What happens after launch, and what costs extra? |
Ask about revision rounds, change requests, licences, hosting and ongoing charges. Verify current prices on the provider’s site or proposal rather than relying on a generic article’s cost range.
Want a clearer plan for your website? Get my free website plan.
Keep ownership and maintenance explicit
Clarify domain ownership, hosting access, website administration, source assets and licences. Ask which parts can be edited by staff and what training is provided. Define how the site can be moved or supported by someone else.
Choose a platform the business can maintain. AI website builders may accelerate a simple first version, but the result still needs accurate content, working integrations, accessibility and a support plan. A generated interface is not a completed operating system for the business.
Ask how quality is verified
Google’s mobile-first guidance and Core Web Vitals documentation provide useful technical context. Ask for tests of the actual mobile journey, loading, responsiveness and stability.
Use WCAG 2.2 as an accessibility reference. A provider should explain what is checked and the limits of automated tools. A screenshot or a single performance score cannot verify every requirement.
Make migration and launch reversible
Require backups, a review environment where available and a launch checklist. Preserve existing addresses unless there is a reason to change them, and map redirects where necessary. Test forms, notifications, payments and important links after launch.
Agree on who handles unexpected issues and how urgent problems are reported. Keep launch responsibilities in writing so they do not depend on assumptions.
Evaluate Graby against the same criteria
Graby lists website design and development, e-commerce development and web application work. Confirm the scope appropriate to your project and request relevant, verifiable examples.
Our mobile checklist helps prepare acceptance criteria, and the design-trends guide helps choose visual priorities. A good proposal should make the outcome and responsibilities understandable before the build begins.