0140 engineers
- On staff in Montreal.
- We are not renting a bench from somewhere else and reselling it to you.
Montreal, Quebec
Webisoft
Custom software, team extension, ERP and AI
Montreal, Quebec. 40 engineers, entirely onshore in Canada.
02 / 23Introduction
Who we are
A Montreal software and AI consulting firm, working with manufacturers, distributors, logistics operators and software teams.
02Entirely onshore
- All work performed in Canada.
- That matters for data residency, for procurement, and for being in your timezone when something breaks.
03Two ways to buy
- A scoped project with a fixed outcome, or capacity added to your own team.
- Most clients end up using both.
03 / 23Introduction
What we do
Four practices. Clients usually arrive through one of them and stay for two.
Custom software
- Platforms, portals, client-facing applications and internal tools.
- Python and Django, React, .NET and Node.
- Delivered as scoped projects with the source code handed to you.
Team extension
- Developers, QA and support embedded in your team and your tools.
- You keep product ownership and strategy.
- We supply the execution capacity.
ERP and Odoo
Implementation, migration and customisation for teams consolidating off spreadsheets and partial systems onto one system of record.
AI and automation
Document and email automation, agentic workflows, forecasting and reporting, built on top of the systems you already run.
04 / 23Introduction
Typical engagements
Six recent examples, described by sector. Client names available where we have permission to share them.
01
Apparel manufacturer
Customer order emails with Excel and PDF attachments read, checked against their in-house PLM style master, and made ready to import into Microsoft Dynamics.
Freight carrier and brokerage
Developer-as-a-service alongside their own three-person team. Product ownership, evaluation and strategy stay in-house; we supply capacity.
Exmar Offshore
A standing development, support and QA team working inside the client's own Jira projects, billed by the day.
Paper and film manufacturer
A fixed-fee prune-and-model stage on a legacy database. The next stage was priced only once the shape of the data was known.
Optical laboratory
Agentic customer support on inbound email, plus accounts payable automation on supplier invoices.
Construction distribution
An Odoo implementation for a team consolidating off spreadsheets and partial systems onto a single system of record.
05 / 23Practices
Custom software development
The core practice. Software built for a business that has outgrown what it can buy off the shelf.
What we build
- Client and partner portals.
- Internal tools that replace a spreadsheet nobody trusts.
- Platforms with a real user base.
- Integrations between systems that were never meant to talk.
How we work
- Scoped in phases with a written definition of done for each one.
- A working checkpoint before the end, not a reveal at the finish.
- Your people in the room from week one.
What you keep
- The source code, deployed in an environment you control, with a written runbook.
- No dependency on us to keep it running, and no licence you have to renew.
06 / 23Practices
Team extension
For teams that have the roadmap and the product judgement, and need execution capacity rather than a project.
Embedded in your tools
- Your Jira, your repositories, your standups and your review process.
- We do not run a parallel process and hand you a report.
You keep ownership
- Product direction, prioritisation and evaluation stay with you.
- We are capacity, not a second opinion you have to manage.
Roles, not just developers
Development, QA and support, staffed to what the work actually needs and adjusted as it changes.
Two contract shapes
Ongoing monthly capacity for day-to-day work, plus separately scoped projects when something larger comes up.
07 / 23Practices
The Webisoft Operating Suite
Our automation and ERP work, in separate areas. Take one, or several, in any order. None of them requires the others.
Intelligence
Demand and inventory projection, scenario modelling, recommendations
Automation
SalesQuotes, proposals, estimates, win and loss review
ServiceEmail triage, drafted replies, escalation routing
OperationsData cleanup, centralisation, system integrations
FinancePayables and receivables, invoice capture, reconciliation
Odoo ERP
System of record for finance, inventory, projects and HR
Cloud
AWS and Azure. Hosting, security and Canadian data residency
Custom applications
Client portals
Dashboards
Internal tools
Connects to what you already run: QuickBooks, Sage, Xero, Salesforce, HubSpot, Shopify, EDI and logistics platforms, legacy databases.
08 / 23Operating suite
Intelligence
Forecasting and recommendations built on your own history, not on an industry average.
Demand forecasting
Projected demand by product, customer and season, learned from your own order history rather than a generic model.
Inventory projection
What runs short and when, based on open orders, lead times and what is already on the water.
Scenario modelling
What happens to margin if a supplier price moves, a lead time slips, or a large order lands.
Recommendations
Reorder points and quantities suggested with the reasoning shown, so a planner can agree or overrule.
Plain-language reporting
Ask a question of your own sales history and get an answer, without waiting on a report to be built.
Sequence
- Your order and stock history
- A model trained on your data
- Forecast with the reasoning shown
- A planner agrees or overrules
09 / 23Operating suite
Automation
The manual steps between systems, handled end to end, with a person still approving the result.
Document intake
Email, PDF, Excel and scans read on arrival, including the attachments customers send in whatever format they like.
Extraction
Line items, quantities, dates and references pulled out and structured, ready for whatever system consumes them.
Reconciliation
Every line checked against your product master, price list or open orders, with near-misses surfaced rather than guessed.
Exception handling
Anything uncertain flagged with a stated reason, and a clarification message drafted where the sender needs to resend.
Approval and output
A person reviews and approves, then the result lands in your system in the format it expects.
Sequence
- Document arrives
- Read and extracted
- Checked against your records
- Flagged if uncertain
- Approved by a person
10 / 23Operating suite
ERP and Odoo
For teams consolidating off spreadsheets and partial systems, or getting more out of an Odoo instance they already run.
Implementation
Standing up the modules the business actually needs, configured to how it works rather than to a demo script.
Migration
Moving data off spreadsheets and legacy systems, with the cleanup done before the import rather than after.
Custom modules
The parts of your operation no standard module covers, built inside Odoo rather than bolted alongside it.
Integration
Odoo connected to the systems staying in place, so the ERP is not another island to keep in sync by hand.
Training and handover
Your people running it, with written documentation, not a dependency on us for day-to-day changes.
Modules
- Finance
- Inventory
- Manufacturing
- Purchasing
- Projects
- Sales
- HR
- Maintenance
11 / 23Operating suite
Cloud
AWS and Azure. The infrastructure under the rest of it, run properly, in your own tenancy.
Hosting and environments
Production, staging and development set up properly, with deployments that are repeatable rather than remembered.
Security and access
Least-privilege access, secrets handled correctly, and an audit trail that stands up when procurement asks.
Canadian data residency
Workloads kept in Canadian regions where your policy or your clients require it.
Monitoring and backup
Alerting on the things that actually matter, with tested restores rather than assumed ones.
Model infrastructure
The hosting and controls for AI workloads, including keeping sensitive data out of third-party training.
Platform
- AWS
- Azure
- Your own tenancy
- Canadian regions
- CI and CD
- Monitoring
- Backup and restore
- Access control
12 / 23Operating suite
Custom applications
The screens and tools that sit on top, when no product on the market does the specific thing you need.
Client and partner portals
A place for customers or suppliers to see status, submit what they owe you, and stop emailing to ask.
Dashboards
The operating picture your team checks in the morning, pulled from the systems that actually hold the data.
Internal tools
Replacements for the spreadsheet everyone relies on and nobody trusts, with the rules written down.
Mobile
For the people doing the work away from a desk, on the floor, in a truck or on a site.
Integration layer
The connective tissue underneath, so the app reads from your systems rather than holding its own copy.
Layers
- Your existing systems
- An integration layer
- The application your people use
13 / 23Delivery
Build your first project
A short exercise we use on calls. Fill in the three blanks and you have the shape of a scope.
A dashboard that connects to ERP data and automates receivables collection.
What you want
Where the data lives
What it should do
14 / 23Delivery
How a project runs
Five weeks on a typical first project. The process mapping happens inside the project, not as a phase you buy first.
We sit with the people doing the work, walk the process end to end, review real documents, and agree the output format.
The build itself, with a checkpoint at the end of week 3 showing working output on your own data rather than a demo set.
Rules and thresholds for what the system handles and what it escalates, set with your team rather than by us.
Testing with your team, tuning against what it finds, deployment, a written runbook and a handover session.
15 / 23Delivery
How we work
Four commitments that hold across every practice.
- We build around the ERP you already run.
- Dynamics, Sage, NetSuite, SAP or something custom.
- Odoo is an option for teams without a system of record, never a prerequisite.
- Automation removes the manual matching, not the judgement.
- Nothing releases on its own, and confidence thresholds are set with your team.
Source code delivered to you, deployed into an environment you control, with a runbook so your people can run it without us.
- Each engagement is scoped, delivered and accepted on its own terms.
- We would rather earn the next project than pre-sell it.
16 / 23Slides 17 to 22
Case studies
Six engagements, across team extension, custom software, R&D and automation.
17 / 23Case studies
Case study 01
Theta Lake
Communication compliance and security software, serving highly regulated industries.
- They needed developers who could work inside a compliance-heavy environment without slowing down, and capacity that could flex with the workload rather than sitting idle between peaks.
- We started with a single embedded AngularJS developer who integrated into their systems and their compliance constraints.
- As trust built, we grew that into a tailored team of five spanning developers and specialist roles.
- A team that scales up during peak workloads and back down in quieter periods, with no loss of continuity and no compromise on the compliance safeguards their industry demands.
One developer, then a team of five, sized to the work rather than to a contract.
18 / 23Case studies
Case study 02
Exmar Offshore
Offshore engineering and maritime solutions, operating globally.
- Lightship and deadweight calculations for offshore drilling platforms ran on slow, error-prone spreadsheets.
- Their internal ERP platform, P-EX, needed modernising at the same time.
- We stood up a dedicated business unit for P-EX and built custom software to replace the spreadsheet calculations.
- When partners and clients started asking about the tool, we rebuilt it as a market-ready SaaS product with scalable architecture, and supported pricing and onboarding.
- Engineering time and error rates both came down.
- More significantly, an internal utility became a commercial product generating recurring revenue for Exmar.
10 active SaaS clients on a product that began life as an internal spreadsheet replacement.
19 / 23Case studies
Case study 03
Share Mobility
Transportation technology for businesses, schools and communities.
- A sudden leadership and staffing shift left them with no CTO and no engineering team, two designers, and live systems in production carrying real security exposure.
- We placed an interim CTO who ran a full technical audit across their 55-repository codebase, covering architecture, security, licensing and operational readiness.
- Alongside that we deployed a senior DevOps engineer, a senior fullstack developer, and a mobile developer retained on call.
- Live systems were secured and stabilised, a technical roadmap and accountability structure were put in place, and delivery capacity returned so the product kept moving.
55 repositories audited, and an engineering function rebuilt from zero.
20 / 23Case studies
Case study 04
eCycle Solutions
One of Canada's leaders in electronics recycling.
- They wanted to move recycling from a cost-heavy necessity to a technology-led business, which meant proving that traceability and automated sorting could pay for themselves.
- A Phase 1 R&D programme: a Hyperledger blockchain ledger for verifiable recycling records, an AI image recognition proof of concept for sorting, and a client-facing application prototype.
- Every feature was mapped back to a real business problem with ERP, sales and operations in the room.
- Operational efficiency gains from automation, buy-in across three departments, and a validated new revenue line packaging traceability and reporting as a sellable data product.
A compliance obligation turned into a product they can sell.
21 / 23Case studies
Case study 05
dVIN Labs
Blockchain, AI and tokenised investment in fine wine.
- They needed to move off an external contractor to an in-house engineering team, relaunch their token securely, and build multi-chain infrastructure, all without losing momentum on a live roadmap.
- A Solana-focused consulting team managed the transition and the token relaunch and onboarded their new in-house developers.
- Alongside it, CTO-led discovery, a high-level security audit and an IT budget plan, plus blockchain, backend, frontend, QA, UI/UX and project management capacity.
- The migration completed without disruption, the infrastructure was hardened for scale, and DeFi feature work accelerated across staking, governance and liquidity pools.
A contractor-to-in-house transition delivered without pausing the roadmap.
22 / 23Case studies
Manufacturing and industrial
Recent work with manufacturers, converters and distributors. Outcomes to be added as each engagement completes.
Sales order intake
- Customer orders arriving as email with Excel and PDF attachments, read and checked against the in-house PLM style master, then made ready to import into Microsoft Dynamics.
Legacy data cleanup
- A fixed-fee prune-and-model stage on a legacy database, with the following stage priced only once the true shape of the data was known.
Manufacturing automation
- AI and automation applied to manufacturing operations, targeting the manual steps between systems that nobody has time to fix.
Invoicing automation
- Invoice generation and processing automated to remove manual re-entry and shorten the cycle from job complete to invoice sent.
Document automation
- Document handling automated on top of an existing Epicor P21 installation, without changing the ERP itself.
Production systems
- Systems work for a thermal paper converter, integrating with their existing production platform.
23 / 23Webisoft
Tell us where the work is
piling up right now.
- If it is a workflow, we will scope one project against it.
- If it is capacity, we will put people on your team.
- Either way you get a fixed shape before you commit.
Phil TherienPartner and Chief Revenue OfficerWebisoft460 Sainte-Catherine St. West, Suite 305, Montreal, QC H3B 1A7
webisoft.com ↗