Skip to content

For procurement, IT and legal

Working with AutomatQ.

The things a buyer's checklist asks for after the business has said yes: security, continuity, contracts, support, compliance and hosting, written down once so nobody has to ask twice.

What you can count on

While we are inside your systems

Security and data handling.

How your systems and data are treated while we are inside them.

  • Access is granted in your name, scoped to what the work needs, and revoked the day the engagement ends.
  • Multi-factor authentication on every account we touch, yours and ours.
  • No production data on personal machines. Development runs on anonymised or synthetic copies unless you agree otherwise in writing.
  • Secrets live in your hosting provider's secret store, never in the repository or a chat thread.
  • Dependencies kept current, and every change reviewed by a person before it ships, including the lines an AI drafted.
  • Security questionnaires answered in writing, before contract.
  • The developer on your project holds CompTIA Security+.

Subprocessors by default: Vercel and AWS for hosting, in your accounts. Infrastructure you already run, in your cloud or on premises, is fine too.

The paper, and who stands behind it.

What happens if the builder is unavailable, what cover is in place, and what the contract says.

Continuity

What happens if the person who built it is unavailable.

  • You own the source, the data, the hosting and every account from the first day. Nothing depends on us staying.
  • Everything is documented for the next developer as it is built, not afterwards.
  • A named second developer, under NDA and familiar with the documentation, can be written into the contract.
  • The stack is mainstream, so your IT team or any local shop could pick it up tomorrow.
  • Planned absences are scheduled around your release dates and told to you in advance.
  • A named second developer, under NDA and familiar with the documentation, can be written into the contract when you need one.

Insurance

Cover, confirmed before signing.

  • Insurance requirements go in the statement of work.
  • Tell us what your agreement requires and cover is confirmed in writing before anything is signed.

Contracts and payment

The paper, and what it says.

  • A master services agreement, then a statement of work per engagement. Your paper is fine, subject to review.
  • Everything built is yours from the first day, in writing: source, data, accounts and the discovery deliverables. Nothing is licensed back.
  • Product delivery: a deposit on signing, the balance across milestones, each tied to something you can open.
  • The managed run and dedicated teams: invoiced monthly, net 30.
  • Purchase orders accepted; invoices carry your PO number.
  • Thirty days of fixes after launch, included in every fixed-scope project.
  • Changes priced in writing before they happen. The managed run follows its twelve-month term; dedicated teams end with a month's notice.

Support terms, in numbers.

What the care plan commits to once the system is live.

  • Support hours

    Monday to Friday, 9 to 5 Eastern.

  • Production down

    Acknowledged within four business hours and worked until resolved, with a written note afterwards on what happened and what changed.

  • Everything else

    A reply by the next business day.

  • Uptime

    Hosted on Vercel or AWS in your accounts, under their published uptime commitments, and monitored so we usually know before you do.

  • Backups

    Daily, with a restore path that has actually been exercised, not just configured.

  • Changes

    Small changes handled within the plan. Anything larger is quoted before it starts.

Built to the standard, hosted in your name.

The compliance the work is built to, where it runs, and the details your accounts payable team will ask for.

Accessibility and compliance

The standards the work is built to.

  • Everything built targets WCAG 2.1 AA, the standard Ontario's AODA requires of organisations with fifty or more employees.
  • Tested with automated tooling and by hand, keyboard and screen reader included.
  • Personal information is designed in with PIPEDA in mind, and PHIPA where health information is involved: collect the minimum, log access, make deletion possible.
  • Single sign-on with Microsoft 365 or Google Workspace, roles and an audit trail come as standard on internal platforms.

Hosting and data residency

Where it runs, and whose name is on the account.

  • Hosted in your accounts, so the data never sits in ours and leaving needs no migration.
  • Canadian data residency when required: data and compute stay in AWS's Canadian region, and the hosting choice follows from that.
  • Infrastructure you already run, in your cloud or on premises, is fine.

Onboarding

Vendor details

For onboarding and invoices.

Legal name, address, business number and banking details are supplied with the proposal, so they reach your accounts payable team before the first invoice does.

Vendor security questionnaires and due-diligence forms are answered in writing before contract. Mention them in your inquiry and they come back completed with the proposal.

What happens next.

  1. 01

    A call

    30 minutes

    You talk, we ask questions. No slides.

  2. 02

    A written summary

    Within one business day

    What we heard, and whether a discovery sprint, a quote or nothing is the right next step.

  3. 03

    Discovery or a quote

    Two to four weeks

    A discovery sprint when the goal is clear and the solution is not. A fixed quote when the scope already is.

  4. 04

    The build

    Fixed price, fixed date

    A live preview from the first week, and everything in your name at the end. Then we run it, if you want us to.

Send the questionnaire with the enquiry.

It comes back answered, with the proposal, before anything is signed.