About FoundryOS

Business software should fit the operation,
not the other way around.

FoundryOS is a Nova Scotia engineering company founded by Dan Merchant. We build custom software when the right system doesn't exist, connect the systems worth keeping, and integrate governed AI where it can do real work, all engineered around how your business actually runs.

We're small and hands-on. The people who understand your operation are the people who design and build the system around it. No account managers, no offshore hand-offs, just real engineering owned end to end.

Start a Project →Take the Assessment →

Why we exist

Custom used to be a luxury.

It isn't anymore, and that changes how your business can run.

For years, custom business software was reserved for companies with large budgets, long timelines, and internal development teams. Most businesses had to adapt their operations around whatever software was available.

That tradeoff has changed. Modern engineering and AI-assisted development make it possible to build serious operational software faster and more economically than before.

But custom does not mean replacing everything. Good engineering starts by understanding the operation: what should be built, what should remain authoritative, what needs to connect, and where automation or AI actually earns its place.

The goal isn't more software. The goal is a better operating system for the business.

How we work

We don't start with software.
We start with the operation.

The questions come before the code.

Where does work begin? Where does the data live? Which system owns it? Where are people manually moving information? Who has authority to make each decision? What has to happen when something goes wrong?

Those questions determine the architecture. Sometimes the answer is a new platform. Sometimes it is integration between systems that already work. Sometimes automation or AI can take over part of the workflow. Usually, the right answer is some combination of those things.

Build what is missing.

When existing software fundamentally does not fit the operation, we build around the business instead of forcing the business around the software.

Keep what works.

A CRM, ERP, accounting system, database, or internal application does not need replacing simply because FoundryOS is involved. Systems that already do their jobs can stay authoritative.

Integrate deliberately.

Connections, automation, and AI should exist because they improve the operation, not because the technology is fashionable. When AI acts inside the business, its authority should be explicit and governed.

What we build around

How we engineer.

The discipline behind every system we ship.

Operational Fit

The system should reflect how the business actually works instead of forcing the operation into generic software.

Build & Connect

Build what's missing. Preserve what works. Connect the gaps between them.

Controlled Automation

Automation and AI earn authority deliberately. Consequential work stays governed by permissions, approvals, policy, and escalation.

Engineering Discipline

Moving quickly does not mean treating production software like a prototype. Infrastructure, data, integrations, security, and operational controls are part of the build.

Ownership

You own what we build. FoundryOS can continue hosting, maintaining, and improving the system without turning it into a black-box dependency.

Operational AI

AI belongs inside a system of authority.

The model is not the system. It is intelligence working inside one.

That means knowing what information it can access, what actions it can take, which decisions require approval, when it must escalate, and what evidence gets recorded afterward.

That is how FoundryOS approaches operational AI: useful enough to do real work, constrained enough to remain accountable.

What we mean by operational AI →

Proof

We ship real systems.

Not concepts. Operational software running in the businesses we built it for.

Our portfolio starts with what we can prove: operational software running in real organizations. Our own product, CrewOS, runs crew and contractor operations end to end and is live at crewos.ca. Alongside it: an operations hub for a commercial cleaning company, a community food network, and the practice-management platform we run FoundryOS on.

The same engineering discipline carries into system integration and operational AI: understand the business first, then build or connect only what the work requires.

See Our Work →

Let's look at how your
operation works today.

Whether the answer is a new platform, better connections between existing systems, operational AI, or some combination of the three, the first step is understanding what the business actually needs.