Approach
Understand the business first. Build the right technology second.
Every engagement is anchored to a piece of work that shouldn’t exist or a decision that needs better information, not to a technology shopping list. Here is how we think, and exactly how an engagement runs.
How we think
Six steps, in this order.
The order matters. Automating a broken process just breaks it faster, and AI on top of bad data gives confident wrong answers.
- 01
Understand
How the work really runs today, who touches it, and what it costs.
- 02
Map
Every hand-off, copy and wait, drawn out and timed.
- 03
Simplify
Remove the steps that shouldn’t exist before automating anything.
- 04
Build
The right tool for each step: a rule, a flow, an application, AI or nothing at all.
- 05
Measure
The same measure before and after, so the result is a number, not an opinion.
- 06
Improve
Hand it over documented, then tune it as the business changes.
How an engagement runs
Small first step. Fixed prices. You own the result.
-
00
30-minute call
Free
We look at one process or decision: how it works today, roughly what it costs, and whether AI, automation, a system or a simpler process would fix it.
You leave with One concrete next step, even if it isn’t with us.
-
01
Diagnostic
Fixed price, from $1,500
We map the workflow, the people and the data trail, and time the current effort. Then we rank the opportunities by effort, risk and payback.
You leave with A current-state map, a measured baseline, a ranked plan and a fixed-price proposal for the first build. The diagnostic fee is credited to the build if you go ahead within 60 days.
-
02
Build
Fixed price, agreed first
We build in your environment, test with your real data, and demonstrate at agreed milestones. Scope changes are priced and agreed before they happen.
You leave with A working system, failure alerts, a manual fallback for anything payroll- or billing-critical, and measured before-and-after results.
-
03
Handover
Included
We train the people who will run it and document what runs, when, who owns it and what to do if it stops.
You leave with Ownership of all code, flows and documentation, plus 30 days of fixes after launch. Ongoing support is available if you want it.
For IT and procurement
Built to pass your IT team’s questions.
Automation touches payroll, cost and equipment records. These are the rules we work to, in writing. Your IT team or managed service provider is welcome from the first call, and can review everything we build.
Access and data
- Your tenant, your systems
- We build inside your Microsoft 365 tenant and existing platforms, not in an account we control.
- Least access, revocable
- We ask for the minimum permissions a build needs, work within your security policies, and you can revoke access at any time.
- Our access is temporary
- We use a separate MFA-protected account, removed at handover. Secrets live in your vault.
- Your data
- We work in your accounts wherever possible. Anything copied for testing is kept encrypted and deleted at handover.
- AI and your data
- Which data may be processed, where and by which service is agreed in writing first.
- Hosting
- Where something must be hosted outside your systems, a Canadian hosting option is available, with backups and data export.
Contracts and continuity
- Written scope
- A written agreement and statement of work: scope, fixed price, timeline, acceptance criteria and ownership.
- Confidentiality
- We sign your NDA and complete your security questionnaire before we see data.
- Licences named first
- Every proposal lists the licences or services a system needs, and what they cost each month, before you approve.
- Service accounts
- Automations run under service accounts, not a person’s login, so they survive staff changes.
- Failure handling
- Every system has failure alerts, and payroll- or billing-critical work keeps a manual fallback.
- Documentation
- What runs, where, under which account, how to change it and how to switch it off.
How we think
Five habits from engineering that make automation last.
Measure first
A baseline before we build, and the same measure after. If it can’t be measured, we say so.
Fix it at the root
Automating a broken process just breaks it faster. We remove the steps that shouldn’t exist before we automate the rest.
Use what you have
Microsoft 365, your existing applications, Excel. New tools only when the case is clear and priced, and AI only where rules run out.
Design for the next person
Someone in your organization will inherit this. Plain documentation, sensible names, no clever tricks.
Show the formula
Every number we give you comes with how it was worked out, so you can check it and defend it.
From your side
What a project needs from you
- One person who owns the problem and can make decisions
- About an hour a week from the people who do the work today
- Access to sample data, exports or documents early on
- An IT contact for accounts, permissions and security questions
Next step
Start with the free call.
No preparation needed. An example of the report, form or export helps, but isn’t required.
With the engineer who would do the work. Reply within one business day.