Back office · Workflow Automation · Bookkeeping, dispatch, dashboards

One trigger. Five tools updated. Nobody retyping anything.

The 90-minute process your operations person runs every morning becomes a 90-second background job with an audit trail. Bookkeeping, dispatch, reporting, intake. Built on production orchestration, in code you own.

// Quick answer

Workflow Automation from Compass AI Group replaces the multi-step process someone runs by hand with a workflow that connects your existing tools and runs it end to end, triggered by a form, an email, a webhook, or a schedule, with every step logged. Common examples are bookkeeping (receipts to reconciled books in QuickBooks or Xero), dispatch, intake, reporting dashboards, and client portals. Built for Canadian SMBs. Scope and price are set in Charting after a free Bearings call.

// How it would work

One RFP comes in. A proposal is on its way out.

A preview of an RFP-intake workflow as it would run for a Canadian engineering firm. Same shape, different business logic, your own integrations.

Workflow · Preview01 · Trigger received
fromprocurement@cityhall.example
subjectRFP-2026-117 · Bridge inspection contract
attachmentsrfp-package.pdf · 38 pages
t-0trigger fired in 0.6s
workflowrfp-to-proposal · started

A new RFP email lands. The workflow picks it up before anyone reads it.

// What you get

Four phases. One signed-off process.

Every workflow follows the same four phases. The logic in the middle is what we build for you.

01

Catches the trigger

A form submission, an inbound email, a webhook, a scheduled time. The workflow listens on whatever signal matters.

02

Gathers context across your tools

Pulls related records from your CRM, looks up the customer in QuickBooks, checks calendar availability, fetches order history. It reads the situation before acting.

03

Decides and acts with branching logic

If new customer, do A. If VIP, route to B. If Stripe errors, retry, then page on-call. Custom logic, custom branches, no rigid template.

04

Writes the result back everywhere it needs to go

Updates the CRM, fires the email, posts to Slack, creates the ticket, syncs the spreadsheet. One trigger, every downstream system updated, audit trail complete.

// Best for

Same engine. Your process.

Every workflow is built around how your team already operates.

  • Someone on your team spends their morning moving the same data between three systems
  • Bookkeeping, dispatch, or reporting is late because it depends on one person remembering
  • You have outgrown Zapier and the spreadsheet that runs the business
// Design principles

Production orchestration. Code you own.

The specific tools depend on your existing systems and integration shape. The principles below hold on every build. No vendor lock-in. You see the exact stack before scope is signed.

Orchestration
Durable execution · production-grade
Reasoning
Modern LLM with tool-use · selected per build
Database
Canadian data residency by default
Integrations
Native API + webhook handlers
Observability
Per-run traces · live dashboards
Reliability
Retry queues · dead-letter alerting
// How it starts

Bearings first. Then the fix.

Every service on this site starts the same way, so you never pay for a build before the problem is measured.

01

A free 30-minute Bearings call

Two operators talking about your business. Where the time goes, what it costs, and whether this service is even the right fix.

02

Charting: a fixed scope in writing

Fixed scope, fixed price, fixed timeline before any work starts. If a Bearings Report should come first, we say so.

03

Heading: build with weekly reviews

You see the work every week. True North measures the result against the baseline we recorded at the start.

// Three common examples
Bookkeeping

Receipts to reconciled books

Receipts photographed or forwarded, read, matched to the bank feed, categorized, GST/HST tagged, posted to QuickBooks. Monthly close in two hours instead of two days.

Dispatch

Order to installer without a phone call

An installation booked in the online store creates the job, picks the installer company by territory and capacity, sends the work order, and updates inventory. Six installer companies, one program.

Dashboards

One screen instead of the spreadsheet, the inbox, and the group chat

A dispatch board, a client portal, or a KPI dashboard built on the same data the workflow already moves. Roles, approvals, and exports included.

// Proof

What changed for real businesses.

(01)
In buildgo-live 30 Sept 2026

A GTA heating-and-cooling company with about 3,500 existing customers

Three manual processes replaced; one program instead of six vendors.

At go-live

The problem
Every sale by phone, referral, or builder; three manual back-office processes.

Workflow questions, answered plainly.

How is this different from Zapier or Make.com?

Zapier connects two apps with a fixed if-this-then-that. Workflow Automation builds custom multi-step workflows that branch on context, handle exceptions, retry on failure, and call any API with whatever logic the process actually needs. Zapier is plumbing. We build the logic that decides what flows through.

Which tools can the workflow connect to?

Anything with an API (Application Programming Interface) or a webhook. Common integrations: Slack, Notion, Airtable, Google Workspace, Microsoft 365, Salesforce, HubSpot, QuickBooks, Xero, Stripe, Shopify, Twilio, ClickUp, Linear, Jira, Asana, and any custom internal system. If your tool has docs, we can wire it.

What happens when the workflow hits an error or edge case?

Every workflow has retry logic with exponential backoff, dead-letter queues for unrecoverable failures, and an escalation rule that routes the exception to a human with full context. Nothing fails silently. You get notified before your customer does.

Can I see each run, and change the logic later?

Yes. Every workflow ships with a dashboard showing live runs, success rate, average duration, and a step-by-step trace of any individual execution. The logic is code you own, so you can hand it to any developer to extend. No proprietary lock-in.

How do you keep workflow runs reliable in production?

We build on trigger.dev for orchestration: durable execution, automatic retries, observability, scheduled jobs, and queue management. The workflow engine itself is proven infrastructure. The only custom code is the business logic that makes it yours.

Can you automate our bookkeeping?

Yes. Bank feeds in, categorized transactions out: receipt reading, GST/HST tracking, reconciliation, and a faster monthly close, posting to QuickBooks Online, Xero, FreshBooks, or Wave with an audit trail on every decision. It does not replace your accountant; it removes their cleanup work.

Can you build a dashboard or admin portal?

Yes. When a workflow needs a screen, we build it: a client portal, a dispatch board, a KPI dashboard, an internal admin tool with roles and approvals. It is scoped as part of the workflow, not as a separate product.

// What manual workflows cost you

Your operations manager is not paid to copy-paste between apps.

Add up the hours your operations lead spends each week moving data between tools by hand: forwarding emails, updating two systems that should sync, retyping invoices, chasing hand-offs. The workflow does that in the background while they do the work you hired them for.

30+ years operatingLean Six Sigma Black BeltCertified Project ManagerToronto, CA

Plot Your
Course.

A free 30-minute Bearings call. Two operators talking about your business. No deck. No pitch. An honest read on what to fix first, and whether AI belongs in it.

Book Your Bearings Call