Consulting

Software built right the first time.

Custom .NET/C#, Azure, and VMware engineering for organizations that need software built right the first time — from greenfield systems to modernizing legacy platforms. You talk to the people doing the work.

01 · Greenfield

Custom .NET/C# applications

From a workflow tool replacing a shared spreadsheet to a complex line-of-business system, we work end-to-end: requirements, architecture, build, deploy, support.

Modern .NET — ASP.NET Core MVC and Web API, Entity Framework Core, clean layered architecture

Frontend to fit the job — server-rendered Razor, Blazor or React depending on the use case

API-first — REST APIs with OpenAPI specifications, designed for the systems that will call them

Accessibility built in — WCAG 2.1 AA, aligned with Government of Canada web standards

Bilingual by default — English and French designed into the architecture, not bolted on

02 · Modernization

Legacy modernization

Rehost, replatform, refactor or rebuild — whatever makes sense for the application in front of us. We port the intent of legacy systems faithfully, without carrying their bugs forward, and keep things running while we do it.

Assessment first — discovery, dependency mapping, and an honest effort estimate per application

Framework upgrades — .NET Framework and classic ASP to current .NET

Data-layer untangling — stored-procedure-heavy logic moved into testable application code

Parity you can verify — side-by-side behaviour checks against the system being replaced

Canadian hosting — Azure Canada Central / Canada East, or your own data centre

Engagement model

Discovery first — larger modernizations typically start with a short paid discovery that delivers technical findings, options and draft outcome requirements your organization can use to procure the next phase from any supplier.

03 · Integration

Integration, identity and access

Enterprise applications rarely live alone. They need to talk to Active Directory, Entra ID, departmental APIs and third-party vendor systems — and those connections are where data quietly goes wrong. We design, build and debug them.

Active Directory & Entra ID — Windows/Negotiate auth, group-based authorization, SSO and conditional access

Vendor & data-feed integration — scheduled and event-driven exchanges with third-party systems

API gateways — Azure API Management, OAuth 2.0, throttling and mTLS where required

Integration forensics — tracing stale, missing or mismatched data back to its root cause

Least privilege by default — audit logging and zero-trust patterns built in

04 · Platform

Azure & VMware

We deploy where your authority to operate actually lives — a departmental Azure landing zone, a private cloud, or on-premises VMware — and automate the Windows operations that keep it running.

Azure — App Service, Azure SQL, Key Vault and landing-zone-aligned deployments in Canadian regions

VMware — vSphere-hosted Windows/IIS workloads, and vRO/Aria orchestration

Windows automation — scripted AD and host operations with an audit trail

CI/CD — Azure DevOps and TFS pipelines, with gated builds and repeatable releases

A vendor integration that was quietly sending stale data.

A long-running enterprise records platform fed customer records to a third-party vendor system and to a legal-entity identifier data exchange. Most records synced correctly. Some didn't — and nobody could say why.

01The symptom

Downstream systems were receiving values that were out of date, even though the source records looked correct to the people maintaining them. The integration itself reported no errors.

02The diagnosis

We traced the export field by field and found the culprit: a value captured as a frozen snapshot when each record was created, rather than read live from its source. Every later update was invisible to the integration.

03The fix

A targeted LotusScript agent that recalculated the field from its live source — correcting the backlog of existing records and keeping new ones current — without re-architecting the platform or the integration around it.

04The outcome

Downstream partners received current data again, and the client got a clear explanation of the root cause instead of another round of manual corrections.

The hardest integration bugs don't throw errors. They send the wrong answer, politely, on schedule.

Need HCL Notes/Domino expertise specifically?

That's Domino North's home turf. For .NET, Azure and VMware work, talk to us directly.

Talk to us → dominonorth.com →