01
Client portals
Your customers submit a request, follow their file and download their documents, without calling.
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.
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.
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.
Customers, partners or branches work in the same system. A shared folder cannot show each of them their share, and nothing more.
A sign-up, a booking, a payment or a subscription product. Your idea calls for accounts and rules, not just pages.
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.
01
Your customers submit a request, follow their file and download their documents, without calling.
02
Sellers, buyers and the rules between them: applications, catalogue, calculated shipping, moderated messaging.
03
Software that several organizations use. In Sofia, each one can open its own public reporting line.
04
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.
05
Screens that update themselves, for many people at once. In Boursify, teams trade live.
06
Complex data made readable. The Pathways Explorer compares 151 net-zero scenarios.
01 Discovery
Follow my request without calling
Must-haveDownload my invoices
ImportantGet notified when my file changes
ImportantEvery request in a single queue
Must-haveSee overdue requests
Must-haveExport the month’s requests
LaterWho sees which customer’s data?
Must-haveInvite partners without opening everything
ImportantUsable on a phone
Must-have02 Analysis
03 Data model
04 Mockups
05 Specification
As an administrator at a customer, I want to invite a partner to a single request, so they can upload their documents without seeing the rest of our file.
06 Development
Email notice when a status changes
Requests ODExport of the month’s requests
Reports NKDocument upload from a phone
Documents LMInviting a partner
Accounts SRFilter requests by status
Requests NKLogin and forgotten password
Accounts LMRequest list, phone format
Requests ODInvoice download
Invoices SR07 Quality
Devices
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
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.
Laravel and Vue are our everyday tools, not a limit: the project and your team decide the rest. See our technologies
Installed on the phone and connected to the same data as your web application, when the camera or notifications are part of the task.
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.
Our research and development hub for digital products, for ideas that first need a prototype.
01
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
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
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
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.
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.
It's a turnkey solution, exactly as we wanted it, when we needed it, and within the timeframe that suited us.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Free. No commitment. Reply within 24 hours.
Names and figures shown in the interfaces are examples.