Web Development Company Canada: Websites and Web Apps That Win Enquiries.
How we decide between WordPress and custom code, run a project, and plan speed, accessibility and privacy, with Quebec's French-language rules where they apply.
Your website looks fine on your own laptop, yet enquiries are thin, the pages crawl on a phone, and nobody is sure whether the contact form breaks a privacy or anti-spam rule. Those problems usually start in the brief, long before any code is written. A sound web project settles what the site must do for customers, who edits it, where the data goes and who owns the accounts.
Devvista is a software development company that builds business websites and web applications for Canadian companies. Calls, design reviews and demos are held on video. Below: build options, how a project runs, speed, accessibility, privacy and tax points, a price guide and when a simpler route will do. When you are ready, describe the site you need.
Website, Web Application or Store: Which One Are You Buying?
Most quotes disagree because the buyers described different things under one word. Pin down which of these you mean first, since the work, the price and the upkeep differ for each.
| What you need | What it usually involves | Where it fits |
|---|---|---|
| Business website | Service pages, a contact form, a blog, pages you can edit yourself | Firms that win work from search and referrals |
| Web application | Logins, user roles, a database, dashboards, links to other systems | Customer portals, booking systems, internal tools, quoting |
| Online store | Catalogue, checkout, tax and shipping rules | Selling products. See our Shopify development for Canadian merchants first |
| Redesign of an existing site | Keeping the pages that earn enquiries, fixing speed and structure | Sites that rank but convert poorly, or load slowly |
| Integration or automation | Connecting forms, accounting, a CRM or a stock system | Teams retyping the same data between tools |
If the web application row describes you, our custom software development page covers the wider method. For a site that mainly needs good design and clear pages, the UI/UX design service sits alongside the build.
WordPress or Custom Code: How We Decide
"Should this be WordPress or custom code?" has a straight answer: it depends on what the site must do after launch. A content site that staff update weekly suits a content management system. A product with accounts, rules and data of its own suits custom code. We aim to say so even when it means a smaller job for us.
| Question | WordPress or similar CMS tends to fit when | Custom build tends to fit when |
|---|---|---|
| Who changes the content? | Marketing or office staff, often and without a developer | Content is mostly data created by users inside the app |
| How much logic? | Pages, forms, a booking plug-in, a simple member area | Pricing rules, approvals, roles, calculations, workflows |
| Upkeep | Core, theme and plug-in updates need a routine | You maintain your own code, so plan fixes and dependency updates |
| Speed to launch | Usually quicker, since themes and plug-ins exist | Slower at the start, tailored to the job |
| Growth | Plug-ins can pile up and slow the site | Easier to keep lean, costly if requirements keep changing |
Our longer comparison is in the post WordPress vs custom website, and the WordPress development page explains what we build on it. If you already know you want a team member for months, see hiring WordPress developers.
How a Web Project Runs, Step by Step
A project moves through the stages below, and we aim for every stage to produce something you can look at and approve before the next one starts.
- Discovery. We usually ask who visits, what they should do, which pages already earn enquiries, what must connect to the site and whether personal data is collected.
- Written scope and quote. We aim to name pages, features, integrations, what is left for a later release, and what we need from you, each named.
- Design. We aim to show layouts for phone and desktop, reviewed on a video call, with a clickable prototype for anything interactive.
- Build. We usually propose a staging copy so you can review progress without touching the live site, and a short demo every week or two.
- Testing. We aim to test on real phones, slower connections, keyboard-only navigation, forms, emails, payments and tax lines.
- Launch. We usually set up redirects from old addresses, analytics and Search Console set up, backups confirmed.
- Handover. We aim to hand over logins, documentation and a short walkthrough for your staff.
We give no standard duration, because feedback speed and the size of the scope decide it. We aim to put a dated plan in the quote instead. An NDA before any business data changes hands is something we usually propose; ask if you want it written into the contract.
Why Your Site Is Slow and How to Measure the Fix
Slow pages lose visitors, and they are fixable. Google's web.dev describes three Core Web Vitals and the level it calls good, measured at the 75th percentile of page loads and split by mobile and desktop (web.dev Core Web Vitals).
| Metric | What it measures | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | How soon the main content appears | 2.5 seconds or less after the page starts loading |
| Interaction to Next Paint (INP) | How quickly the page responds to taps and clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the layout jumps as it loads | 0.1 or less |
To find the cause, split LCP into parts. web.dev lists four: time to first byte (about 40 percent of the total in its guideline), resource load delay (under 10 percent), resource load duration (about 40 percent) and element render delay (under 10 percent), and calls the shares guidelines, not strict rules (Optimize LCP). A server that answers slowly and a huge hero image are the two culprits we look for first.
We aim to measure real-world field data where it exists, fix the largest delay, then measure again. A passing score is not a ranking promise, and we do not make one. It is simply a cheaper site to keep visitors on.
Accessibility for Canadian Websites: WCAG, AODA and the Accessible Canada Act
Accessibility is both a legal question in some cases and a plain usability one for every site. The standard most rules point to is the Web Content Accessibility Guidelines. WCAG 2.2 became a W3C Recommendation on 12 December 2024, has levels A, AA and AAA, and adds nine success criteria to 2.1 (W3C WCAG 2.2). We are developers, not lawyers, so confirm which rule binds you with your own adviser.
| Rule | What the official page says | What it means for a build |
|---|---|---|
| Ontario, AODA | Since 1 January 2021 public websites must be accessible if the organization is a designated public sector body or a business or non-profit with 50 or more employees. Web content posted after 1 January 2012 must meet WCAG 2.0 Level AA, apart from success criteria 1.2.4 and 1.2.5 (Ontario.ca) | If you are in scope, we aim to build and test to at least WCAG 2.0 AA. We usually aim for WCAG 2.2 AA, which goes further |
| Federal, Accessible Canada Act | The Act aims at a Canada without barriers on or before 1 January 2040, including information and communication technologies. It applies to federal bodies and to works or undertakings within Parliament's authority (Justice Laws, ss. 5 and 7) | Mostly relevant to federally regulated organizations. Whether you are one is for your adviser to say |
| Everyone else | Neither page above sets a duty for an ordinary provincially regulated small business | Accessible design still widens your audience, so we aim to test it |
In practice we aim to check headings and landmarks, colour contrast, keyboard access, visible focus, form labels and error messages, and alternative text. Some checks need a person, not a scanner, so we aim to test with a keyboard and a screen reader before launch.
Privacy and Email Rules That Shape Your Forms: PIPEDA, Law 25 and CASL
A contact form, a newsletter box or an analytics tag all touch personal information. Three Canadian regimes come up most often. Summaries below come from the official pages we opened; the laws themselves prevail, and your adviser decides what applies to you.
| Law | What the official page says | What we usually build in |
|---|---|---|
| PIPEDA (federal) | Applies to private-sector organizations that collect, use or disclose personal information in commercial activity. Alberta, British Columbia and Quebec have provincial laws deemed substantially similar, and organizations under them are generally exempt for activity within the province (OPC PIPEDA brief) | Collect only what each form needs, state the purpose beside the field, list every third-party tool the site calls |
| PIPEDA breach duties | Report to the OPC any breach of security safeguards with a real risk of significant harm, notify the individuals as soon as feasible, and keep a record of every breach for two years (OPC guidance) | We usually propose logging, alerts, and a short written response plan agreed before launch |
| Quebec Law 25 | Quebec's Law 25 may apply to you: check whether it does. Businesses that collect personal information by technological means must publish a privacy policy, and the person in charge and their contact details go on the website. Consent must be informed and given for specific purposes, as the CAI describes. An assessment is needed before communicating information outside Quebec and before projects involving information systems or electronic service delivery that involve personal information. A confidentiality incident register must be kept (CAI Law 25 summary) | Cookie and consent banners with separate choices, a published policy page, an incident log, and a written impact-assessment input list when your site serves Quebec |
| CASL | Asks businesses to obtain consent before sending commercial electronic messages, and also addresses false or misleading representations including websites (CASL overview) | An unticked, separate consent checkbox on newsletter and marketing sign-ups, and a record of when it was given |
The point for design is the order of work: decide what data you collect, then draw the forms. Doing it the other way round is how a site ends up with fields nobody can justify.
Serving Quebec: Plan the French Version From Day One
If part of your audience is in Quebec, language is a build decision, not a translation job at the end. Quebec has its own French-language rules. We have not summarized them here; check the Office quΓ©bΓ©cois de la langue franΓ§aise (oqlf.gouv.qc.ca) or a Quebec adviser before you finalize scope.
What we can say as builders is what changes in the project. A bilingual site needs separate pages for each language with matching addresses, a language switch on every page, translated forms and error messages, French metadata, and a content process so both versions are updated together. We ask on the first call whether Quebec visitors matter, because adding the structure later costs more than planning it from the start. For an online shop the same question is covered on our Shopify page.
Payments and GST/HST: Questions to Settle Before Checkout
Pages that take money or quote prices touch tax, and the order of decisions matters. The Canada Revenue Agency says a business is a small supplier when its worldwide taxable revenue was C$30,000 or less in a single calendar quarter and over the last four consecutive calendar quarters. Once you stop being a small supplier, the CRA expects you to register within 29 days of that day, so check the dates on the page below with your accountant (CRA RC4022).
| Question for your accountant | Why it shapes the site |
|---|---|
| Are you registered, and where? | Decides whether tax lines appear at checkout or on quotes |
| Which provinces do you sell into? | Decides which rates the site must handle |
| Do invoices come from the site or from accounting software? | Decides whether we integrate with your accounting tool |
| Do you take deposits or subscriptions? | Decides which payment provider flow we build and test |
We build the site to whatever your accountant decides. We do not give tax advice, and we aim to test one transaction per case you sell into before launch.
What Drives the Price of a Web Project in Canada
Prices depend on what the site does, so we quote after a scoping call. A short call comes first, then a proposal in Canadian dollars. We ask for the budget range you have in mind, so we can propose what fits it.
What moves a quote is rarely the page count. The items below are the usual drivers, and we usually put each in the written scope so you can see where the money goes.
| Cost driver | Why it matters | How we handle it |
|---|---|---|
| Logins and data | Accounts, roles and a database are more work than static pages | We aim to scope it as its own line |
| Integrations | Links to accounting, a CRM or payments need testing on both sides | We aim to name and price each integration |
| Content volume and migration | Moving hundreds of pages and keeping their search addresses takes care | We usually propose a page inventory and redirect plan before build |
| Languages | A second language doubles pages, forms and testing | We aim to decide it before design |
| Release size | A smaller first release costs less and teaches you what matters | We usually propose a small first release, then more |
Rankings and enquiry volume are not part of any quote. The SEO service covers search work separately, and we do not promise results.
Domains, Hosting and Code: Who Holds the Keys
The question that bites later is who holds the keys. A domain, hosting account, analytics property and code repository registered to a developer are hard to move if you part ways. We usually propose opening each in your business name so that the logins are yours from day one, and we work inside them.
We aim to list in the handover document every account, what it is for and who can access it, so a future developer or your own staff can pick it up without us.
Web Developers for Toronto, Vancouver, Montreal and Beyond
Buyers often search by city, but the method does not change with the postal code. The same stages apply to a clinic group in Vancouver, a contractor in Calgary, a distributor near Toronto or a retailer in Halifax. What changes is the audience: a Toronto firm may need accessibility evidence for a public-sector client, and a Montreal firm may want French pages. We hold calls, design reviews and demos on video, and aim to fit them to your time zone.
We run one Canadian page rather than a page per city, because the offer is the same. The Canada home page lists the other services, and the mobile app development page covers apps for the same buyers. Delivered work across the company is on our case studies page.
When Devvista Is a Good Fit, and When It Is Not
We suit Canadian businesses that can name who the site is for and what a visitor should do, want one team across design, build and launch, and intend to own what is built.
| We are a good fit if | We are probably not if |
|---|---|
| You want a business site or web application built to your needs, with accounts in your name | You need only a template with your logo, which a site builder already does |
| You welcome being told a store platform or template would do | The lowest quote alone will decide for you |
| You handle personal data and want privacy planned from the start | You need a price before any discovery |
| You want French-language needs raised and scoped early | You need legal sign-off from us, which developers cannot give |
If the real problem is retyping data between tools, an integration project may pay back faster than a new site. Say so on the first call.
Straight Answers.
Tell us about the site you need
Name who the site is for and what a visitor should do. Book a call and we will say whether a website, a web app or a simpler route fits, and what the first release should contain.
- 30-minute online call
- Honest feedback on fit
- No obligation
- Book a call30 minutes online. Tell us what you want to build.
- Get a straight answerHonest feedback on fit and scope.
- DecideYou choose the next step once the scope is clear.