Web application development
Browser-based applications such as portals, dashboards, SaaS products and workflow tools, engineered for security, scale and integration.
An organization's web presence is rarely just a website. It is a public site, client or partner portals, an intranet, and the forms and integrations that connect them to your CRM and ERP. We plan and build these as one platform: accessible, bilingual where you need it, secure, and owned by you.
Web development is the planning, design, build, testing and launch of web platforms: public websites, client and partner portals, intranets and program microsites. It helps an organization establish a clear presence online and reach its audiences effectively, but for most organizations the website is also a service channel. Visitors apply, register, book, download documents and ask for help, and each of those actions has to reach the right system and the right person.
We treat web development as a business platform, not a design exercise. That means sign-in through your identity provider where portals are involved, forms that store every submission before notifying anyone, integrations with your CRM or Prometheus ERP, and security and accessibility that are tested rather than assumed.
When the requirement is mostly business logic rather than content, such as transactions, workflows or dashboards, see web application development.
Accessibility is designed in from the first template. We test against WCAG 2.2 AA with keyboard-only use, screen readers, colour contrast checks and zoom, and we write the results down. Ontario's AODA sets website requirements for many organizations; see the questions below for a summary.
For bilingual organizations we build English and French as equal versions, with separate URLs, correct language tags, layouts that allow for longer French text, and a translation workflow in the CMS.
Privacy is handled in the build: analytics and tracking respect consent choices, forms collect only what you will use, and sign-up forms for newsletters are set up with CASL consent in mind. Quebec's Law 25 has specific rules for tracking technologies, and we implement what your advisers confirm. This is not legal advice.
Every form stores its submission first, then notifies the right mailbox or system, and failures are retried and reported instead of silently lost. Portals connect to Microsoft Entra ID, Google or other OpenID Connect or SAML providers. We follow OWASP guidance, keep plugins and modules to a justified minimum, and can host in Canadian cloud regions to support data residency preferences.
We commonly work with WordPress, Drupal, headless CMS platforms such as Strapi, Contentful and Sanity, and front-end frameworks such as Next.js. Naming a platform does not imply a partnership or reseller status with its vendor.
A web platform needs security updates, content changes and monitoring. Managed-service clients can include their web platforms in 24/7 monitoring and support, with response targets set in the service agreement. Good design matters as much as good code, and our UI and UX design service covers research, prototypes and usability testing. For planning advice, read website and app development strategies for businesses.
The exact list is agreed in writing for each project. These are the usual deliverables and the usual boundaries.
Most delays in this kind of work come from access and decisions, not from the technical build. Knowing these early keeps the project predictable.
Larger platforms follow five stages. Smaller projects combine some of them.
Goals, audiences and top tasks, plus an inventory of existing URLs, content and integrations so nothing valuable is lost by accident.
Output: Discovery summary and URL and content inventory.
Information architecture, templates and a design system, with accessibility notes on each component. We agree these before building so changes are cheap.
Output: Approved sitemap, templates and design system.
The platform is built on a private staging copy. Forms, sign-in and CRM or ERP connections are wired up, content is migrated and redirects are prepared.
Output: Working staging platform.
Accessibility, browsers and devices, performance, security, forms, redirects and both language versions are tested and recorded.
Output: Test report with pass and fail results.
Launch at an agreed time with a rollback plan, then editor training and a written handover.
Output: Live platform, handover guide and credentials.
We do not publish package prices. Each estimate is based on an agreed scope, in Canadian dollars, with taxes shown separately. These are the things that move the number most:
It depends on who edits the content, what the site must connect to and how much control you need. WordPress suits many organizations because editors know it and many providers support it. Drupal and headless CMS platforms suit complex permissions, multiple sites or content shared with apps. We explain the trade-offs in discovery.
Under Ontario's AODA, designated public sector organizations, and businesses and non-profits with 50 or more employees in Ontario, must make their websites meet WCAG 2.0 Level AA, with some exceptions. We design and test to WCAG 2.2 AA, which builds on 2.0. This is general information, not legal advice.
Each language gets its own URLs, correct language tags and a visible language switch, and the CMS tracks which pages still need translating. Organizations serving consumers in Quebec should review French-language requirements with their advisers.
Any change carries some risk. We reduce it by inventorying current URLs, keeping valuable pages, redirecting changed ones to their closest equivalent and checking redirects after launch. We cannot promise rankings, but we make sure nothing breaks through carelessness.
You do. The domain, hosting, CMS administration, analytics and licences should all be in your organization's name. We work with delegated access and hand everything over at the end.
Browser-based applications such as portals, dashboards, SaaS products and workflow tools, engineered for security, scale and integration.
User research, UX audits, prototypes, design systems and accessible interfaces for business software, portals, ERP screens and mobile apps.
What successful websites and apps have in common, the six-stage development process, common challenges and how to choose a development partner.
Tell us which sites and portals you run today, who uses them and what they need to connect to. We will reply to arrange a conversation about scope before anything is priced.