First Workflow

Your first automation, scoped tight. Usually built in about a week once the scope is locked.

Pick the one repetitive job that eats hours every week. We build it, write it down, and hand it back finished.

We pick the workflow with you during the AI Readiness Audit and agree the trigger and the outcome together. Then we send the written scope and the quote for your review. Once the scope is locked, the build usually takes about a week.

What you get: the operating packet

Every First Workflow build ships with seven artifacts. Each one is yours, in your tools, in plain English.

Workflow map

A one-page diagram of how information moves through the workflow: what goes in, what happens to it, and what comes out.

Named owner

One person on your team who owns the workflow. We document who, why, and what they're responsible for.

Trigger

The single event that starts the workflow, such as a form submission, an email arriving, a calendar event, or a message from another system. Written down so nobody has to guess.

Approval boundary

The list of actions the automation can't take without a person checking first. Customer-facing emails, moving money and anything that can't be undone all stop for review.

Failure path

What happens when something goes wrong. Where the input goes, who gets alerted, what the fallback is. So a broken workflow doesn't quietly lose data.

Runbook

Written instructions a teammate could follow to operate, pause, or hand off the workflow. Specific enough that you don't need us.

Evidence log

A record of what the automation did, when, and what its inputs and outputs were. Operational, not compliance.

A typical sprint

Illustrative. The day-by-day shape varies with the workflow.

1

Day 1

Rewrite the SOP so each step is explicit. No "use your judgment" gaps.
2

Day 2

Build the trigger and the first action.
3

Day 3

Connect the remaining steps to reach the outcome.
4

Day 4

Run it on real input, with a person watching every result.
5

Day 5

Fix what broke, then let it run live with the checkpoint in place.

If the workflow can't fit a sprint, we cut it down before we start. Ship one thing, see the result, and decide what comes next from evidence.

What we don't do

We don't build five workflows in a sprint. One.
We don't automate an undocumented process without documenting it first.
We don't ship without a human checkpoint on the first runs.
We don't put your data anywhere it doesn't belong. We can run on Canadian infrastructure or on your own.
We don't hand you something you can't run yourself.

How we scope and quote

There's no price on this page. During the audit we confirm fit, pick your first workflow and outline the likely scope together. Then we send the written scope and the quote for your review.

We quote after we've seen the work, so the price fits your job and not a template.

FAQ

What if my workflow doesn't fit in one sprint?

We cut it down with you during the audit. If it can't be cut down, we say so and recommend a different starting workflow. Better to ship something smaller and prove it works than to overrun.

What tools do you build it on?

We build on n8n by default (how we run n8n for Canadian businesses). It's open-source, can run on your own servers, and is yours to keep. We can also work in Zapier or Make if that's where your tools already live. We settle the choice during the audit.

What happens after the workflow goes live?

The build hands you the operating packet. If you want us to keep maintaining it through the months and years that follow, that's a Kept Running plan. You can also take it from there yourself. The packet is yours either way.

Can I see what you've built for other clients?

We can show you the shape of a workflow we've built (with the client's permission, anonymized) during the audit. We don't put case studies on the public site yet.

Find your first workflow.

Book the AI Readiness Audit

Free for now. Not forever.

What the audit covers

Or see how Kept Running works → /kept-running