Software built around how your organization works.
We plan, build and run custom systems, such as learning platforms, operations and inventory tools, and client portals, connected to the software you already use. You own what we build.
What we build
Systems for the work that off-the-shelf software handles badly, or the work your team does differently.
Learning and training
Courses, onboarding and certifications, with reminders before anything expires.
- Learning management
- Staff onboarding
- Certification tracking
- Continuing education credits
Operations and supply chain
Orders, stock and suppliers in one place instead of three.
- Inventory
- Purchasing
- Supplier portals
- Dispatch and scheduling
Client and member portals
A place for clients or members to sign in, see their files and get things done.
- Accounts and documents
- Bookings
- Payments
- E-signing
CRM and sales
Pipelines, quotes and contracts shaped to how you sell.
- Lead pipeline
- Quotes
- Contracts
- Client history
Internal tools
The forms, approvals and case files your staff use every day.
- Intake forms
- Approvals
- Case management
- Field reports
Dashboards and reporting
The numbers from every system in one place, without the Friday copy and paste.
- Key numbers
- Board reports
- A data warehouse
- Scheduled exports
Sound familiar?
Most of the systems we build start as one of these.
- The same details typed into three different systems.
- A spreadsheet that runs the business, and one person who understands it.
- Paying per seat for software you use a fraction of.
- A process the software can’t handle, so it lives in email.
- Reports that take a day to put together.
- Old software nobody can change, and nobody wants to touch.
| AName | BCourse | CDone | DExpires |
|---|---|---|---|
| J. Patel | First aid | 03/02/24 | ?? |
| Maria Gomez | WHMIS | 2024-11-18 | Nov 2026 |
| sam o’neil | first-aid | ||
| Chen, L. | Forklift | 12 Jan | renew? |
| Patel, Jaya | WHMIS (dup?) | 2023 | expired?? |
Certifications tracked in a spreadsheet nobody trusts
An illustration of the kind of change we work on, not a client result.
Today
- Staff certifications live in a spreadsheet, and reminders go out when someone remembers.
- New hires get a folder of PDFs and a week of shadowing.
- When an auditor asks for training records, it takes days to pull them together.
With the change
- Staff take courses in one place, and certificates are issued when they finish.
- Reminders go out on their own before anything expires.
- Training records ready for an audit, exported in one click.
Every step included
A software project runs through the same four steps as our AI work, from mapping the workflow to keeping the system running.
- ConsultWe map how the work moves today and decide what to build, buy or leave alone.Workflow mapping · A build or buy check · A written scope, priced per phase · A clickable prototype before any codeIncluded
- EngineerDesigned and built in short cycles, with something working to review every two weeks.Interface design · Web apps and portals · Roles, permissions and an audit trail · Accessible, in English and FrenchIncluded
- IntegrateConnected to the software you already run, with your data moved across.Accounting, payroll and email · Payments, e-signing and sign-in · Data moved out of spreadsheets · An API for whatever comes nextIncluded
- ImplementPiloted with one team, then launched with training and documentation.A pilot with one team · Training and guides · Hosting in Canada, if you need it · Monitoring and backupsIncluded
We keep it running
A monthly plan looks after hosting, security and fixes, and leaves room to keep improving the system as your work changes.
- Hosting, monitoring and backups
- Security updates, tested before release
- Fixes, and improvement hours every month
- A quarterly review of what to build next
Custom or off-the-shelf?
Off-the-shelf software is the right answer more often than you’d think, and we’ll tell you when it is. Custom pays off when the way you work is what sets you apart.
| Custom software | Off-the-shelf | |
|---|---|---|
| Fit | Built around how your team already works. | Your team changes how it works to fit the software. |
| Cost over time | Built once, then a fixed monthly plan. No per-seat fees. | Per seat, every month, and the bill grows with your team. |
| Your data | In a database you control. | In the vendor’s system, under their terms. |
| Connections | Connected to exactly the systems you run. | Limited to the connectors the vendor offers. |
| Vendor risk | Nobody can retire it or change its terms. | The vendor can raise prices, drop features or shut it down. |
| Time to start | Built in phases, over weeks or months. | Often the same day. |
| Upfront cost | A project budget, agreed in a written scope. | Low, often a free trial. |
Build or buy? Five questions
Answer all 5 to see where you land.
You own it
What we build for you is yours: the code, the data and the documentation. No per-seat fees, and nothing that locks you in to us.
- Your code, in your own repository
- Your data, in a database you control
- Documentation another team could pick up
- No per-seat licences
Built here first
The CRM this company runs on is one we built: a lead pipeline, a client portal, e-signing, required two-factor sign-in, and an assistant that reads the CRM. It’s the same kind of work we do for clients.
Ready for AI when you are
Every system we build keeps its data clean, its permissions clear and an API open, so adding an assistant later is a step, not a rebuild. Run it on your own hardware or with a cloud provider.
Questions
Something else? Ask in the form below.
Who owns the code?
You do. Our default agreement assigns the code, the data and the documentation to you, and it lives in accounts you control. If we ever part ways, another team can pick it up.
How is a project priced?
Each phase has its own price, agreed in a written scope before work starts. Discovery comes first, so the estimate for the build is based on what we learned rather than a guess.
How long does it take?
It depends on the size of the system. We build in phases, each one usable on its own, and agree the timeline in the scope before work starts.
Can you take over a system someone else built?
Often, yes. We start by reviewing the code and the hosting, tell you what we found, and then fix, extend or replace it. Sometimes the honest answer is to keep what you have.
Will it work on phones?
Everything we build works on phones and tablets in the browser. If you need an app in the app stores, we’ll say so during discovery and plan for it.
Where is our data hosted?
With a hosting provider we agree on together. If your data needs to stay in Canada, we use Canadian regions and document it.
Can it work in English and French?
Yes. When you need both, we plan for them from the start, which is much easier than adding French later.
Plan your system
Tell us a little about the system you need. We reply by email, usually with a few questions or a time to talk.