Skip to content

AI operating system for businesses in London, Ontario

In short. Aiwah Labs in London, Ontario builds AI operating systems that run one workflow, such as purchase approval or dispatch, across the tools you already use, with named approvers and an audit trail. The first use case is live within a week, and we build on it. Typical setup is from about USD 3,500, with no monthly maintenance fee.

AI operating system implementation overviewAll services in London, Ontario

People working across a manufacturing floor
Starting price
USD 3,500
Typical one-time setup, in US dollars. No monthly maintenance fee.
Timeline
First use case in 1 week
We build on top of it, one use case at a time.
Languages
English, French
Staff screens and drafts run in English. French inputs are tested in the audit.
Office
London, Ontario
Also serves St. Thomas, Kitchener, Waterloo and Southwestern Ontario.
You own
Code and data
Plus the prompts and the accounts set up for you.

What is an AI operating system for a business?

An AI operating system carries one workflow, such as an order, an invoice, a site visit or a renewal, from the signal that started it to a next step a named person can defend. Software does the carrying. People keep the judgment.

It replaces neither your ERP nor your CRM, which stay the record. The operating layer connects the message, the document and the approval those systems keep apart. A company brain answers questions. An operating system moves the work. For the broader change to the workflow itself, see operations redesign.

  1. Trigger

    A message, a document or a date starts the case.

  2. Agent steps within limits

    Read, file and draft. The design lists what it may do alone.

  3. Your existing systems

    ERP, CRM, drive and inbox stay the record.

  4. Approval and audit trail

    A named person approves. Each run keeps what was read and changed.

How one workflow moves through an AI operating layer, with a trail at the end.

Where it helps in London, Ontario.

Scenarios the setup is built around. Each one ends in a record or a person, not a dead end.

Purchase and invoice approval for a manufacturer

A purchase request arrives. The system checks the budget line and the supplier record, drafts the purchase order, and routes it to the person whose limit covers it.

Dispatch and job closing for a trades firm

A request becomes a job, a technician is assigned, and the job closes only when the proof and paperwork are on the record. Exceptions land with a named owner.

Renewals for a professional-services firm

A client renewal approaches. The system gathers the history, drafts the message, and waits for a partner before it sends anything.

What we build.

We integrate with the systems you already run: your ERP, CRM, accounting, email and the in-house tools nobody else supports.

The system of record

SAP, Oracle, Odoo, Zoho, Tally, QuickBooks, Xero, Salesforce, HubSpot, or an older in-house system that has an API, a database or an export. If a system has none, the first release is a record beside it, with no forced migration.

The layer between them

Our code moves each step between your systems and holds the state the old system cannot. The AI drafts and checks. It does not approve.

What it may do alone

Read, file, draft and update a status the design marks as safe. A payment, a price, a coverage decision or a clinical decision waits for a person.

The trail

Each run stores what it read, what it changed and who approved the rest. The people who own the workflow can open it.

One case, end to endInvoice approval in the team channel
Recorded
  1. Trigger

    Invoice 1042 arrived by email from a supplier.

  2. Operating layer

    Invoice 1042 matches purchase order 311, but the total is 8% above the last order. I have sent it to Priya for approval, with both documents attached.

  3. Approver

    Approved.

  4. Written to your accounting system

    Status set to approved. Who approved it, and what the system read, saved in the audit trail.

Illustrative example. Not a real conversation.

From one real case to a live path.

First use case in 1 week. We build on top of it, one use case at a time.

  1. Days 1–2Audit

    Audit one workflow

    One invoice path, one dispatch board or one renewal cycle. The people who run it are in the room, and we trace where the work stalls.

  2. Days 2–3Design, before build

    Name the decision a person keeps

    Everything else can be drafted or moved. That one decision stays human, and the screen shows the evidence behind it.

  3. Days 3–5Build

    Connect the tools that hold the work

    The message channel, the document and the system of record share one case, with no second copy that drifts.

  4. Days 4–6Test, before launch

    Rehearse the exception

    A missing approval, a failed write and a changed bank detail all have to land with an owner. The happy path is the easy test.

  5. End of week 1First use case

    Run it on live work

    The first use case takes real cases, with a person approving. It is live within a week.

  6. Then, use case by use caseAfter the first use case

    Build on top of it

    The next workflow goes on top of the first, one at a time, with the same named approvers and audit trail.

Talk to sales.

Prices are in US dollars and exclude taxes. They are one-time setup, not a subscription.

Typically from aboutUSD 3,500One-time setup

No monthly maintenance fee. No vendor lock-in. The client owns the code and the data.

Talk to sales
  • One operating workflow first, not a replacement for your ERP or CRM
  • The systems you already run, where an interface exists
  • Actions only inside the limits set in the design
  • An audit trail of what ran and who approved it
  • You own the code and the data. There is no requirement to stay on our hosting.

Usage, such as LLM tokens, is passed through at provider cost. We add no markup.

Bring one call, thread or workflow. We scope from there.

Book a call

What you own at the end.

You own

  • The code and the workflow logic
  • The data the system holds and its audit trail
  • The prompts and the rules that set what it may do alone
  • The cloud and model accounts, which can sit in your name
  • The build itself, with no vendor lock-in

Controls that stay in place

  • Consequential actions wait for a person. The design lists them.
  • Every run has an audit trail: what was read, what changed and who approved.
  • Your ERP or CRM stays unless the engagement names a piece to replace.
  • No monthly maintenance fee and no vendor lock-in. You own the code and the data, subject to third-party licences.

Integrations

One operating layer across every system you run.

The layer sits between the tools that already hold the work. It reads, checks and moves each step, and writes the result back to the system of record.

Inner ring: where the record lives

ERP and accounting

  • SAP
  • Oracle
  • Dynamics 365
  • Odoo
  • ERPNext
  • Zoho
  • QuickBooks
  • Xero
  • Sage

CRM and service

  • Salesforce
  • HubSpot
  • Zendesk

Outer ring: where the work moves

Mail, sheets and approvals

  • Gmail
  • Outlook
  • Excel
  • Google Sheets
  • Slack
  • Microsoft Teams
  • WhatsApp

Payments, data and reporting

  • Stripe
  • Razorpay
  • PostgreSQL
  • MySQL
  • Airtable
  • Power BI
  • AWS
  • Azure
Examples, not the full list. Logos do not imply a partnership with their makers.

Not on the list? We still connect it.

If your system lets data in or out, we connect to it. If it does not, we find a workaround, and we tell you how dependable that route is before we build. We also connect Tally, Zoho Books, NetSuite, bank and tax portals, warehouse and dispatch software and the in-house system nobody else supports.

  1. API or webhook

    The clean route. Most modern tools have one, and many older ones do too.

  2. Database or export

    No API? We read the database, or a scheduled CSV or SFTP export.

  3. Email and shared folders

    We pick up the reports, invoices and attachments your system already sends.

  4. Screen automation

    For a portal with no other way in, a bot works the screen the way your team does, with every step logged.

How we approach integrations →

What changes in London, Ontario.

Also serves St. Thomas, Kitchener, Waterloo and Southwestern Ontario.

London’s manufacturers, agri-food firms and health suppliers run on approvals: a purchase over a limit, an invoice with a price that moved, a production change, a job closed without its paperwork. The City of London names five key sectors, agri-food, manufacturing, digital media and technology, health, and professional services. Its economic overview page was last modified in October 2020, so read the list as context and not as a count. An AI operating system takes one of those flows and runs it across your ERP, your inbox and your shared drive.

The approvals are the product. A purchase request arrives. The system checks the budget line and the supplier record, drafts the purchase order, and routes it to the person whose limit covers it. A payment, a price change or a changed bank detail waits for that person. The ERP stays the record, and every run logs what it read and who signed off.

Trades and field-service firms get a different version of the same layer. Our essay on field service automation in London, Ontario describes what a winter job needs on the record before it can be billed: the address, the technician’s qualification for the work, what was done, and the customer’s signature or recorded refusal.

For firms that sell to municipalities, hospitals or schools, Ontario’s Bill 194 applies to those public bodies, not to private businesses. It matters to vendors selling AI to them, and an audit trail gives you a record to show those buyers.

We scope the first workflow with the people who run it, in your office.

Sources behind the local points

  1. The City of London names five key sectors: agri-food, manufacturing, digital media and technology, health, and professional services. The page was last modified on 8 October 2020.

    City of London, Economic Overview of London, Ontario
  2. Ontario’s Bill 194 (S.O. 2024, c. 24) applies to public-sector entities, including FIPPA and MFIPPA institutions, children’s aid societies and school boards. It does not regulate private businesses, but it matters to vendors selling AI to municipalities, hospitals and schools.

    Legislative Assembly of Ontario, Bill 194 (43rd Parliament, 1st Session)

Straight answers.

Does an AI operating system replace our ERP?Local

No. Your ERP or accounting system stays the record. The operating layer connects the email, the document and the approval around it, and writes the status back.

Which workflow should a London manufacturer or trades firm start with?Local

The one where work stalls waiting for someone: a purchase approval, an invoice with a changed price, or a job that cannot be billed without its paperwork. We pick one in the audit and leave the rest until it runs on live cases.

Does Ontario’s Bill 194 apply to our business?Local

Only if you are a public-sector entity. Bill 194 applies to FIPPA and MFIPPA institutions, children’s aid societies and school boards, not to private businesses. It matters if you sell AI-enabled services to those bodies, and the audit trail records what each run read and who approved it.

How much does it cost in London, Ontario?

Setup is typically from about USD 3,500, one-time, with no monthly maintenance fee. Model usage is billed at provider cost, with no markup from us.

How long does it take?

The first use case is live within a week, and we build on top of it, one use case at a time. We do not quote a total timeline.

Bring one workflow.

Tell us the call, the thread or the record. Every setup on this page starts with a call.

Book a call