0117

Montreal, Quebec

Webisoft

Custom software, team extension, ERP and AI

Montreal, Quebec. 40 engineers, entirely onshore in Canada.

02 / 17Introduction

Who we are

A Montreal software and AI consulting firm, working with manufacturers, distributors, logistics operators and software teams.

0140 engineers
  • On staff in Montreal.
  • We are not renting a bench from somewhere else and reselling it to you.
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 / 17Introduction

What we do

Four practices. Clients usually arrive through one of them and stay for two.

01

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.
02

Team extension

  • Developers, QA and support embedded in your team and your tools.
  • You keep product ownership and strategy.
  • We supply the execution capacity.
03

ERP and Odoo

Implementation, migration and customisation for teams consolidating off spreadsheets and partial systems onto one system of record.

04

AI and automation

Document and email automation, agentic workflows, forecasting and reporting, built on top of the systems you already run.

04 / 17Introduction

Typical engagements

Six recent examples, described by sector. Client names available where we have permission to share them.

05 / 17Practices

Custom software development

The core practice. Software built for a business that has outgrown what it can buy off the shelf.

01

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.
02

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.
03

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 / 17Practices

Team extension

For teams that have the roadmap and the product judgement, and need execution capacity rather than a project.

01

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.
02

You keep ownership

  • Product direction, prioritisation and evaluation stay with you.
  • We are capacity, not a second opinion you have to manage.
03

Roles, not just developers

Development, QA and support, staffed to what the work actually needs and adjusted as it changes.

04

Two contract shapes

Ongoing monthly capacity for day-to-day work, plus separately scoped projects when something larger comes up.

07 / 17Practices

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

Attaches to any of these, or to none at all.

Connects to what you already run: QuickBooks, Sage, Xero, Salesforce, HubSpot, Shopify, EDI and logistics platforms, legacy databases.

08 / 17Delivery

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.

01

We sit with the people doing the work, walk the process end to end, review real documents, and agree the output format.

02

The build itself, with a checkpoint at the end of week 3 showing working output on your own data rather than a demo set.

03

Rules and thresholds for what the system handles and what it escalates, set with your team rather than by us.

04

Testing with your team, tuning against what it finds, deployment, a written runbook and a handover session.

09 / 17Delivery

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.
10 / 17Slides 11 to 16

Case studies

Six engagements, across team extension, custom software, R&D and automation.

11 / 17Case studies

Case study 01

Theta Lake

Communication compliance and security software, serving highly regulated industries.

THE CHALLENGE
  • 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.
WHAT WE DID
  • 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.
THE OUTCOME
  • 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.

12 / 17Case studies

Case study 02

Exmar Offshore

Offshore engineering and maritime solutions, operating globally.

THE CHALLENGE
  • 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.
WHAT WE DID
  • 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.
THE OUTCOME
  • 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.

13 / 17Case studies

Case study 03

Share Mobility

Transportation technology for businesses, schools and communities.

THE CHALLENGE
  • 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.
WHAT WE DID
  • 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.
THE OUTCOME
  • 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.

14 / 17Case studies

Case study 04

eCycle Solutions

One of Canada's leaders in electronics recycling.

THE CHALLENGE
  • 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.
WHAT WE DID
  • 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.
THE OUTCOME
  • 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.

15 / 17Case studies

Case study 05

dVIN Labs

Blockchain, AI and tokenised investment in fine wine.

THE CHALLENGE
  • 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.
WHAT WE DID
  • 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 OUTCOME
  • 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.

16 / 17Case studies

Manufacturing and industrial

Recent work with manufacturers, converters and distributors. Outcomes to be added as each engagement completes.

APPAREL MANUFACTURING

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.
PAPER AND FILM

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.
FLUID CONTROL SYSTEMS

Manufacturing automation

  • AI and automation applied to manufacturing operations, targeting the manual steps between systems that nobody has time to fix.
TANK MANUFACTURING

Invoicing automation

  • Invoice generation and processing automated to remove manual re-entry and shorten the cycle from job complete to invoice sent.
CRANE SALES AND SERVICE

Document automation

  • Document handling automated on top of an existing Epicor P21 installation, without changing the ERP itself.
PAPER CONVERTING

Production systems

  • Systems work for a thermal paper converter, integrating with their existing production platform.
17 / 17Webisoft

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