Questions we get first
What we do
What do you actually do?
Two things. We automate the multi-step processes in professional services offices, and we build custom software, data platforms and AI systems for organizations and public-sector buyers.
We already have Copilot or ChatGPT. Why this?
Keep them. They help one person do one task. We build the layer that runs the whole process across your people and systems.
Which service is right for us?
If you are a professional services office and a process eats hours, start with AI automation. If you need a specific system built, start with a scoping conversation on any of the other five.
Do you work with public-sector buyers?
Yes. We build custom software, data platforms and AI systems for organizations and public-sector buyers, with accessibility and Canadian data residency designed in.
Do you only work in Ottawa?
We are in Ottawa and we work across Canada. The engagement day is on site or online, and the rest of the work runs on scheduled calls.
What counts as a multi-step process?
Anything that runs through more than one person, tool or system before it is finished. Intake to delivery on a file, a report, a claim, a filing.
Do you meet public-sector accessibility requirements?
We design to WCAG 2.1 AA from the start and it is part of acceptance. Accessibility is built in rather than added at the end.
Pricing
What does it cost?
For automation: the assessment is $2,499 credited against the first build, builds are $5,000 to $12,000 fixed per workflow, ongoing from $1,500 a month. For custom software: a fixed price against a defined scope, quoted after a scoping conversation.
What is included in the monthly plan?
Hosting in Canada, single sign-on, monitoring and alerts, upgrades and fixes, and priority response. New work beyond that is scoped and quoted on its own.
Why is the assessment paid?
It is three to four weeks of measured work and a written report you keep, and it is credited in full against the first build.
What if nothing is worth building?
The report says that on page one and you keep the report.
What is a larger system?
Anything past a single workflow, such as a platform several teams use or a build that spans many processes. Those are quoted separately after a scoping conversation.
Data and security
Where does our data live?
In Canada, or on hardware in your own office. Your choice, in writing, and it never trains any model.
What if the AI makes something up?
Every output has to point back to its source, and if it cannot it does not say it. A person reviews and signs before anything leaves your office.
Is our data going to the United States?
No. It runs in Canada or on hardware in your own office, your choice, in the agreement in writing. It never trains anyone’s model.
Do we need a data warehouse?
Only if the work needs one. We size the store to your data and your reporting, and the cost is in the fixed quote before you agree to it.
How do you handle data quality?
Data quality checks are part of the build, so bad and duplicate records are caught as they arrive. Every number can be traced back to the record it came from.
Where does the data live?
In Canada, or on hardware in your own office. Your choice, in writing, and it never trains any model.
What if it makes something up?
Every output has to point back to its source, and if it cannot it does not say it. A person reviews and signs before anything leaves your office.
Which models do you use?
We choose per project and put it in writing. Your data never trains anyone’s model.
Can it run without an internet connection?
Yes, where the work needs it. We can run the system on hardware in your own office so your documents never leave the building.
How it runs
How fast can we see something working?
By week two of a build you have a working version running on your own files.
How much of our time does it take?
About three hours from the principal, six from the operations lead, and ninety minutes each from two or three staff, across the whole program. Fifteen minutes a week from one reviewer during a build.
Are you going to tell us to cut staff?
No. The assessment tells you where the hours go. What you do with them is your decision. Most firms want the volume.
What happens if something breaks at 2 a.m.?
Monitoring alerts us, and priority response is part of the plan. We fix the fault and tell you what caused it.
Do we have to switch everything at once?
No. We migrate piece by piece with the service running the whole time, and you decide at each step.
Can we stop after the assessment?
Yes. The report is yours to keep and nothing rolls over on its own.
Is the assessment fee credited?
Yes, in full, against the first build.
Who is on the calls?
The person who builds the work is on every call. On your side it is the owner or principal, the operations lead, and the people who do the work.
Working with us
Can you take over a system you did not build?
Yes. We stabilize first, then improve piece by piece, with the service running the whole time.
What happens at the end?
You keep everything: source code, documentation and infrastructure configuration. If you want us to keep running it we will, and the handover is not conditional on that.
What happens to the code at the end?
You keep the source code, the documentation and the infrastructure configuration. The handover is not conditional on us continuing to run it.
Can you work inside our cloud tenancy?
Yes. We can build and host in your tenancy, in Canada, or on hardware in your own office, and the choice is written into the agreement.
Can we leave?
Yes. The plan is month to month with 30 days’ notice, and you can take the handover at any time.
What do you need from us to start?
Access to the system and the people who know it, plus whatever documentation exists. We start with a scoping conversation and put the plan in writing.