Skip to content

Web application development in Montreal

Client portals, platforms, online products, internal tools: applications that open in the browser, with nothing to install, for your customers, your partners and your teams. Witify designs them, builds them and keeps them moving forward.

Talk to an expert

For
SMBs, nonprofits and founders of online products
Technologies
Laravel, Vue, TypeScript, Nuxt, React
Team
Montreal, all across Quebec

01 When

When a web application makes more sense than a website

A website is read. A web application is used: each person has their own account, rights and data in it. It comes into its own in the situations below.
A team at work in front of several screens, in a bright office
  1. Your customers call to ask where their file stands

    An order, a request, a claim: the information is in your systems, but only your staff can reach it. Every question turns into a call or an email.

  2. Forms that come back by email

    An Excel file or a PDF goes out to a customer or a partner, comes back filled in as an attachment, and then someone types it in again. Read why Excel ends up getting in the way.

  3. Everyone must see their own data, and nothing else

    Customers, partners or branches work in the same system. A shared folder cannot show each of them their share, and nothing more.

  4. A service to offer online

    A sign-up, a booking, a payment or a subscription product. Your idea calls for accounts and rules, not just pages.

  5. An internal tool at the end of its rope

    An Access database, a shared workbook or a no-code tool that slows down, crashes or can no longer keep up with its users. Read the risks of Access in 2026.

Before we build, we look for the lightest option that does the job. It may be a good website, an online form or software already on the market. When it is, that is what we recommend.

When the need reaches past the portal into sales, production or inventory, it is custom software instead. Our analysis shows it early.

02 What we build

What your users open in their browser

A portal, a platform or an internal tool all have accounts, roles and data that stay current for everyone. The rest depends on who logs in.

02

Marketplaces

Sellers, buyers and the rules between them: applications, catalogue, calculated shipping, moderated messaging.

See Arto Galleria : Marketplaces

03

Online products

Software that several organizations use. In Sofia, each one can open its own public reporting line.

See Sofia : Online products

04

Internal tools

A team’s tool, open anywhere. The Centre de jour de Saint-Jérôme prepares the day’s baskets in it and tracks each beneficiary’s balance.

See the Centre de jour : Internal tools

03 Method

A method where every step shows

Our usual method, with one question asked from the start: who logs in, on which device, and to see what? Every step leaves a deliverable you can look at.

01 Discovery

We meet every type of user.

Your customers, your staff, your partners and management do not expect the same thing from the application. We meet them separately, then list what each must be able to do, in order of priority.
Fig. 01 The discovery meetings board

02 Analysis

We decide what to connect, import or replace.

Accounting software, online payment, a shared mailbox, an older tool: we take stock of what exists and of the part each will play once the application is live.
Fig. 02 The map of systems to connect

03 Data model

We structure the data and the access.

Organizations, accounts, roles, requests, documents: the model sets who each piece of data belongs to and who may see it. Every user’s rights follow from it.
Fig. 03 The model of accounts and access

04 Mockups

Every screen is drawn for the computer and the phone.

The main journeys become mockups in both formats. Your users comment on them at this stage, while a change does not yet touch a line of code.
Fig. 04 The portal mockup

05 Specification

Every feature is described, then approved.

For each one: the role that uses it, what it must do and the criteria that will say it is done. You approve the document before the first sprint.
Fig. 05 A page of the specification

06 Development

Every week, something new to try.

Each sprint lasts a week and ends with a follow-up meeting with you. What is ready reaches staging, a copy of the application your team opens in its browser, at the office or on a phone.
Fig. 06 The week’s board

07 Quality

Every release goes through the same checks.

No change moves forward without a senior developer’s review. Automated tests check the features and each role’s access rights, then you approve in staging. The release to production is automated.
Fig. 07 The path of a change to production

04 Quality

What we take care of in a web application

A web application opens on devices nobody picks, for users who do not all have the same rights. So access, screens and speed come before everything else. The examples below use made-up data.

Devices

One application, every screen.

The same requests on an office computer and on a customer’s phone. On the small screen, what matters comes first: the list, the status, the action button.

Access

Everyone sees their share.

Each role opens only the screens that concern it. A partner uploads documents without ever seeing an invoice. Your administrators invite and remove accounts themselves.

  1. Every access checked by the server

    The risk
    A hidden button protects nothing. Someone who guesses an address could open another customer’s file.
    Our choice
    Every request checks the user’s role and organization. Automated tests confirm it for each role. Sensitive actions go to the audit log.
    The gain
    A customer never sees another customer’s data.
  2. Fast, even as usage grows

    The risk
    An application that is quick with a hundred files can slow down at a hundred thousand, just as usage takes off.
    Our choice
    Volumes are planned in the data model. Each screen loads only what it shows, and long tasks (exports, imports, email sends) go through a queue. On the systems we maintain, Sentry flags slowdowns.
    The gain
    Screens stay fast as users and data pile up.
  3. Open to the internet, protected accordingly

    The risk
    A web application can be reached from anywhere, including by people looking for a flaw. A leak of personal information brings obligations under Quebec’s Law 25.
    Our choice
    Sensitive data encrypted, servers closed behind a firewall, automatic alerts when a library has a known flaw, ISO 27001 and SOC 2 certified hosting.
    The gain
    Your users can trust you with their information.

What we build with

Laravel and Vue are our everyday tools, not a limit: the project and your team decide the rest. See our technologies

Application
Laravel, PHP, REST APIs for your other systems
Interfaces
Vue, TypeScript, Tailwind CSS, Nuxt or React when the project calls for it
Real time
WebSockets, screens and notices that update themselves
Data
MySQL, PostgreSQL, D3.js for custom visualizations
Hosting
AWS, DigitalOcean, serverless for highly variable loads
Monitoring
Sentry, errors and slowdowns flagged on maintained systems
Tooling
Sprintify, our in-house kit of components and modules

05 Sprintify

The foundations are ready, the time goes to your rules

Accounts, roles, tables, forms, email notices: every web application needs them. With Sprintify, our in-house tool, these building blocks already exist and are tested. AI-assisted code generation then produces the base of each module. The hours saved go to your screens and your special cases.

What Sprintify brings

  • Ready-made interface components (Sprintify UI): tables, forms, filters, uploads.
  • Proven modules for accounts, roles and permissions.
  • AI-assisted code generation, starting from the approved data model.
  • A review by our developers, who steer and complete what is produced.

What it gives you

  • Screens to try from the first sprints.
  • Consistent screens from one module to the next, because they share the same components.
  • A budget that goes to your business rules rather than the login page.
  • A base our whole team knows, so it is simpler to evolve.

What it does not replace

  • Meeting your users: they decide what we build.
  • The design of your journeys, made for your customers and your teams.
  • Your business rules: they are written with you, case by case.
  • Code review, tests and staging, as for everything else.

06 Witify Lab

Web, mobile and AI, with the same team

A web application is often the heart of something larger. The same team can add a mobile app or AI to it, on the same server and with the same data.

Mobile app

Installed on the phone and connected to the same data as your web application, when the camera or notifications are part of the task.

See the service : Mobile app

Artificial intelligence

An assistant that answers your customers from your documents, an attachment read the moment it arrives. We suggest it where it pays off better than a simple rule.

See the service : Artificial intelligence

07 Go-live

A launch prepared with your users

A web application often opens to a lot of people on the same day. We put it in a few hands first, then open it wider. Our deployment checklist covers the preparation.
  1. Staging You try every journey with realistic data.
  2. Pilot group A few real users, customers or staff, before everyone else.
  3. Accounts and data Existing data imported, accounts created, invitations ready.
  4. Training Your teams trained before the opening, clear documentation for your customers and partners.
  5. Go-live An automated deployment, with redirects if the application replaces an older site.
  6. First weeks Usage and errors watched closely, quick adjustments.

08 After

After launch, an expert view of what comes next

Once live, the application shows what no meeting could predict: what your users actually do. As your technology partner, we use it with you to decide what comes next: what is worth building, what can be automated, what can wait. Monitoring, fixes and updates are part of our support and maintenance offer.

01

What still goes through the phone

Requests that still arrive by call or email show what the application does not cover yet. For each one, we estimate with you the time it takes your team and what it would take to bring it in.

02

Who else could log in

Your suppliers, another branch, your subcontractors: we assess with you who would benefit from entering the application, with which rights and to what end.

03

Automation and AI, tried on your cases

Sorting incoming requests, drafting a first reply, spotting an overdue file: we test these tools on your own requests before recommending that you adopt them.

04

Every change measured

Time to answer a request, calls avoided, share of customers who use the application: measured before and after each change, to know what it really brought.

09 Work

Portals, platforms and products already live

A real-time simulator, an online product, a nonprofit’s tool, a marketplace, a public data tool: applications built by our team in Montreal, each told in its own case study.

View all projects

  • Boursify

    Financial education

    A market that doesn’t exist. Whole classes trading live.

    Web application, Mobile application

  • Sofia

    Harassment prevention

    Two complaint regimes. One single software.

    Custom software, Web application

  • A list in Excel. Today’s list, in one click.

    Custom software, Web application

  • Arto Galleria

    Art, online marketplace

    Unique, fragile artworks. Sold and shipped online.

    Web application

  • Net-zero Canada by 2050. 151 ways to get there.

    Web application

It's a turnkey solution, exactly as we wanted it, when we needed it, and within the timeframe that suited us.

Sylvain Castonguay Founder and CEO, Nordresa

10 Questions

Questions and answers

Cost, technologies, devices, security: answers to the questions asked before a project.

Another question? Email us at info@witify.io or call 1 800 334 9031.

What factors influence the cost and duration of a web application project?

Three factors weigh the most: the number of features and types of users, the depth of the journey design (UI/UX) and the rigour of testing. Integrations with your other systems add to them.

Depending on the timeline and the product, it is sometimes wise to launch a first version to a smaller group of users. Elsewhere, you only make one first impression, especially when sensitive data is involved. When an algorithm or a technical goal is uncertain, a research and development (R&D) phase comes first and moves forward in iterations.

For orders of magnitude, read our article on what custom software costs.

What technologies do you use for your web applications?

On the server, we mostly work with Laravel (PHP), whose ecosystem covers most of what a web application needs: accounts, queues, APIs, notifications. For interfaces, we use Vue and TypeScript, with Nuxt or React when the project suits them. D3.js handles custom data visualizations. Data lives in MySQL or PostgreSQL.

Hosting is on DigitalOcean or AWS, with a serverless architecture for highly variable loads. Sprintify, our in-house tool, brings ready-made components and modules along with AI-assisted code generation.

These tools are a habit, not a limit: we also work with other languages and frameworks, depending on your project and on what your team already uses.

How do you handle responsive compatibility for different device types (desktop, tablet, mobile)?

All our web applications adapt to the screen: computer, tablet and phone. Mockups are drawn in both formats from the start. We then try the application on the devices your audience actually uses, including less common sizes when needed.

A web application can also be installed on a phone’s home screen, like an app (PWA). If your users need deep access to the phone’s features or a presence in the app stores, a mobile app is a better fit.

How do you maintain web application security?

On the servers first: ISO 27001 and SOC 2 certified hosting, restricted access, sensitive data encrypted and backed up every day.

Inside the application next: every access is checked against the user’s role and organization, and automated tests confirm it with every change. Sensitive actions can be recorded in an audit log.

Our technical leadership approves every technology before it is used on a project. Automatic alerts flag the libraries affected by a known flaw, which are then updated.

Do you help with compliance with GDPR standards and Law 25?

Yes, in how the application is designed. From the start, we plan for what these laws ask for in practice: clear consent, plus a person’s right to access, correct or delete their information. Add to that access limited to what each person must see and a record of who consulted what.

We do not give legal advice: your privacy policies and your precise obligations are validated with your legal counsel. Our role is to build an application that makes your compliance easier.

What is the difference between a website and a web application?

A website presents your services, your products and your team. It is made to be found and read. A web application is for getting things done: people log in to submit a request, follow a file, order or approve. It manages accounts, data and rules.

A simple test: if your users must log in and what they do changes data, it is an application. Many organizations have both. The website stays the storefront. The application lives behind the login.

Web application or mobile app: which one to choose?

A web application is often the right starting point: nothing to install, a single version for every device, updates everyone gets at the same time. It suits users at a desk, occasional customers and outside partners.

A mobile app makes sense when the camera, notifications, offline work or a presence on the App Store and Google Play matter. Both can share the same server and the same data: Effet Tandem runs on the web, iOS and Android. Our article on native and hybrid apps helps you choose.

Why a custom application rather than a no-code tool (Airtable, Bubble)?

For a small internal tool, with few users and simple rules, a no-code tool is often a very good start. If it is enough, we will recommend it.

Custom work takes over when the tool becomes critical: customers or partners log in, access rights get finer, volume grows, integrations multiply. We can then take over what exists and rebuild it while keeping your data.

Can you take over an existing web application?

Yes. We start with a code audit: technologies and their versions, quality, security, database. You then know what is worth keeping.

Depending on the result, we update the application to keep it evolving, or we rebuild it in stages while limiting the impact on your users. Our page on application modernization describes both paths.

Who owns the code of our application?

You do. Ownership of the code built for your project is transferred to you once it is paid in full, as our contract sets out.

That ownership holds up in practice: the code is versioned, covered by automated tests and documented, on widely used technologies (Laravel, Vue, MySQL). Another team could take it over if you ever chose to.

A portal or a platform in mind? Let’s talk.

In 30 minutes, an expert listens to who needs to log in and what for. They tell you whether a web application is the right path and what it would take.

  • A 30-minute call with an expert, not a salesperson
  • A realistic budget estimate, backed by numbers
  • A concrete action plan, whether you work with us or not
Or write to us

Free. No commitment. Reply within 24 hours.

Names and figures shown in the interfaces are examples.