Do we have to start with a discovery sprint?
No. If you already have a specification, or the problem is small and clear, it is quoted directly as a fixed-scope project. Discovery is for when the problem is known and the solution is not.
What does it cost?
Discovery is a fixed fee from $6,000 CAD; most land between $6,000 and $18,000, depending on how many sites, teams and systems are involved. You know the number before it starts, it is the only thing you commit to, and it comes off the build if you go ahead. Builds start at $50,000 for one workflow end to end, integrated with your ERP, land around $100,000 for two or three workflows with a portal, and start at $150,000 for a platform that runs a whole department. Running it afterwards is optional, from $2,500 CAD a month on a twelve-month term, sized to the system and the support it needs.
Why not just use AI, or a no-code tool?
Sometimes you should, and discovery will say so. The rule: use off-the-shelf or no-code when the workflow fits the tool and the data can live there; build custom when the problem is integration, ownership, or a process the tools cannot bend to. We use AI for first drafts too, with a person reviewing every line, because in Veracode's 2025 study AI models picked the insecure option in 45% of coding tasks.
What happens if the person who built it is unavailable?
You own the source, the repository, the hosting and every account from day one, so nothing depends on us staying. Everything is documented for the next developer as it is built, a named second developer can be written into the contract, and the stack is mainstream enough that your IT team or any local shop can maintain it.
How long until something is live?
Discovery takes two to four weeks. Builds are released in stages, so the first piece is usually in use within weeks of starting, while the rest is still being finished.
Who runs it once it is live?
You can, or we can. Hosting, monitoring, updates, the small changes a live system needs and a weekly report are from $2,500 CAD a month on a twelve-month term, sized to the system and the support it needs. The build is yours either way, so stopping is a notice period, not a migration.
What if the answer is not to build anything?
Then that is the recommendation, in writing. Sometimes the fix is a process change or an off-the-shelf tool. Discovery is designed so that answer costs a few weeks to reach rather than a quarter.
Can you work with the software we already have?
Usually that is the point. Most operations work is integration — getting the ERP, CRM, scheduling and the quote queue to tell the same story — rather than replacing any of them.
Who owns what gets built?
You do. Source code, data, hosting and every account are in your name from the first day, including the discovery deliverables.
Will this disrupt the team while it is being built?
Discovery takes a few hours of each person’s time in conversation. The build runs beside the current process, and the switch happens when you are ready, not when the calendar says so.
Do you sign NDAs?
Yes, and an NDA before discovery is normal. Most of this work sits behind a login, which is why little of it can be shown publicly.
Whose contract do we sign?
Either. We work under a master services agreement with a statement of work per engagement, and your paper is fine subject to review. Purchase orders are accepted. The full terms are on the Working with AutomatQ page.
Can you pass our vendor security review?
Yes. A completed security questionnaire, data-handling policy and incident response plan go out with the proposal, and your own questionnaire is answered in writing before contract. Access is granted in your name and scoped to the work, every account has multi-factor authentication, production data stays off personal machines, and everything is hosted in your accounts rather than ours.
Do you carry insurance?
Insurance requirements go in the statement of work. Tell us what your agreement requires and cover is confirmed in writing, with certificates, before anything is signed.
Can our team sign in with Microsoft 365 or Google Workspace?
Yes. Single sign-on, roles and an audit trail are standard on internal platforms, so there is no second password to manage and access ends when someone leaves the directory.
Does the data have to stay in Canada?
It can. When residency is a requirement, data and compute stay in AWS's Canadian region and the hosting choice follows from that. Infrastructure you already run is fine too.
Will it meet AODA?
Everything built targets WCAG 2.1 AA, which is the standard Ontario's AODA requires of organisations with fifty or more employees. It is tested with automated tooling and by hand, keyboard and screen reader included.
Can we speak to a reference?
Yes. References are arranged at the proposal stage, so a client's time is only asked for when a decision is close.