Skip to content

Custom Software Engineering

The systems your AI has to live in.

AI is only ever as good as the software around it. We build the platforms, APIs, integrations and data pipelines that the clever part depends on — and modernise the ones quietly holding your business back. Often this is the work that actually needed doing.

  • Web platforms & dashboards
  • APIs & systems integration
  • Data pipelines & warehousing
  • Legacy modernisation
  • Cloud architecture & DevOps
  • Technical due diligence

Where the real cost sits

The spreadsheet is running the company

Somewhere there is a workbook, a shared inbox and one person who understands both. It works until it does not, and it cannot be automated, audited or handed over.

Your systems do not talk to each other

The booking system does not know about the invoicing system, which does not know about the CRM, so a person retypes the same information three times a day and occasionally gets it wrong.

The old platform is now the constraint

Every change takes a month, nobody wants to touch the deployment, and the original developer left in 2019. Rewriting it wholesale is terrifying and usually unnecessary.

In this section

What we build

Web platforms & internal tools

Multi-tenant SaaS, operations dashboards, portals and back-office systems — with the permissions, audit trails and admin tooling that make them safe to actually run a business on.

APIs & integration

Well-documented APIs, and the integration work that connects the systems you already pay for: payments, accounting, scheduling, identity, messaging, government and industry endpoints.

Data pipelines & reporting

Ingestion, transformation, warehousing and reporting that produce numbers your team trusts — with lineage, so when a figure looks wrong you can find out why.

Legacy modernisation

Incremental, not big-bang. We put a seam around the old system, move capability across a piece at a time, and keep you running throughout. Rewrites that stop the business are how modernisation projects die.

Cloud architecture & DevOps

Infrastructure as code, CI/CD, environments, observability, backups and disaster recovery — on Azure, AWS, GCP or Cloudflare, hosted in Canada where residency matters.

Technical due diligence

For investors and acquirers: an independent read on a codebase, its architecture, its team and its real technical debt, written in language a deal team can use.

What you get

Built by senior engineers, documented for a team that has never met us.

  • 01 Production software in your cloud accounts, under your control
  • 02 Source code and full commit history in your repositories
  • 03 Infrastructure as code, so the environment can be rebuilt from scratch
  • 04 CI/CD pipelines with automated tests and safe rollbacks
  • 05 Monitoring, alerting and logging that a human will actually respond to
  • 06 Architecture decision records — what we chose and why
  • 07 Runbooks and a handover session for whoever maintains it next

How it works

  1. 01

    Understand the system

    Before proposing anything we map what exists: the software, the integrations, the manual steps people have quietly built around the gaps. The workarounds are usually the most informative part.

  2. 02

    Sequence for value

    We stage the work so something useful lands early and the riskiest piece is proven first — not so that the invoice is smooth and the payoff arrives at the end.

  3. 03

    Build and integrate

    Two-week increments, deployed continuously, with your team able to use and challenge each one. Integration work happens early, because that is where the surprises live.

  4. 04

    Operate and hand over

    Monitoring, runbooks, documentation and training. We make ourselves unnecessary on purpose, and stay on retainer only if you want us there.

Engagement models

We are deliberately conservative about technology choice. Anything we pick, you have to run for the next three years.

Discovery & technical plan

A fixed-fee engagement that maps the existing system, defines the target architecture and produces a sequenced, costed plan.

Fixed fee · 1–3 weeks · scoped to complexity

Project build

Defined scope delivered in two-week increments, fixed price per phase, with a working system at the end of each.

Phased fixed price · scoped to complexity

Ongoing engineering partnership

A standing monthly commitment for teams that need continuous capacity — new features, maintenance, integrations and platform work.

Monthly retainer · minimum 3 months

Related work

Systems we have built that touch this kind of problem.

A bookkeeping platform for Canadian small business, with AI extraction, a grounded assistant and native mobile apps. Built, shipped and operated by us.

Native apps
iOS + Android
Bilingual
EN / FR
Data residency
Canada
Export format
T2125
  • Native iOS
  • Native Android
  • Azure (Canada)
  • Microsoft Entra
  • Stripe

A bilingual, multi-tenant operations platform for Canadian driving schools: constraint-based scheduling, learner records, automated messaging, billing and certificates.

Tenancy model
Multi-branch
Bilingual
EN / FR
Learner portals
No install
Compliance posture
Law 25
  • Multi-tenant SaaS
  • Azure (Canada)
  • Constraint scheduling
  • Role-based access
  • Tenant isolation

Questions about engineering

What is your stack?

TypeScript and React on the front end, Python and Node on the back, Postgres for data, and Azure, AWS, GCP or Cloudflare for infrastructure. We are conservative on purpose — new tools have to earn their place in something you will run for years.

Will you work alongside our in-house developers?

Yes. We often work best as the senior pair for an existing team — setting architecture, reviewing code, handling the hardest pieces — rather than replacing anyone.

Can you take over a project someone else started?

Usually. We start with a short paid review so we can tell you honestly what is salvageable and what is not, before either of us commits to a plan.

Do we have to do AI to work with you?

No. A good deal of our work is ordinary, well-built software. If AI does not improve your problem, we will not add it so we can put it in a case study.

Start here

Tell us what is actually broken.

Thirty minutes, no deck, no pitch. You describe the problem; we tell you honestly whether AI is the right tool, roughly what it would take, and whether we are the right people. If we are not, we will say so.

We reply within one business day. English or French.