approach · workflow first, tool second

Map. Automate. Hand over. Care.

Same four moves on every job, so your team still trusts it a year later.

01 Map 02 Automate 03 Hand over 04 Care

01 · Map

Map the work as it really happens.

The real clicks and copy-pastes, with the person who does the work. Then a baseline.

you get

A process map of the work as it runs
A baseline in hours, response time or error rate
A clear line between what gets automated and what stays human
A fixed quote for the first build

The stated request is rarely the real need.

02 · Automate

Automate what’s safe to automate.

Rules for consequences. AI behind validation. Every step fails loudly.

built into every workflow

Deterministic logic for decisions with consequences
Validation before AI writes or sends anything
Error handling and alerts to a named person
Logging for any step that writes a record or sends a message

03 · Hand over

Hand it over, documented.

Your accounts, your credentials, your docs. Live is not done. Owned is done.

you get

A runbook for when it breaks
A handover session and a named owner on your side
A one-page guide for small businesses
Reusable methods and templates stay with you

04 · Care

Keep it healthy.

30 days of stabilisation, then Care or a clean handoff. No lock-in.

after launch

30 days of stabilisation fixes on every build
Care plans from $50 a month, business-day response
A monthly health note: runs, errors, hours saved
Or a clean handoff to your team, fully documented

house rules

Seven principles I stand by.

01 Map before building. The stated request is rarely the real need.
02 The person who does the work is in the design session. Without them, it fails in production.
03 Deterministic logic for decisions with consequences. AI handles judgement tasks, behind validation and a human path.
04 Native before middleware. Don’t add a tool you don’t need.
05 You own the accounts, workflows and docs. Built in your accounts, with your credentials, from day one.
06 Live is not done; owned is done. It runs whether or not I’m around.
07 No hours-saved claim without a baseline. I measure before, so the after actually means something.

guardrails

Compliance isn't a phase. It's in the build.

Built in from the start, not bolted on after launch.

CASL Consent checked before any follow-up sends. PIPEDA · BC PIPA You decide which data goes to which vendor, in writing. no scraping Licensed data only. No scraping. Meta messaging rules DMs only to people who reached out first. No cold DMs. sensitive data Sensitive details stay out. Names, times and contacts only. AI output No AI writes or sends without validation.

fit at a glance

I'll tell you if it's not worth automating.

strong fit

The same manual work happens daily or weekly
Someone will own the system after I leave
The process is stable enough to write down
The tools have APIs or native automation
There’s a baseline to measure against

probably not

The process changes every week
You want AI for its own sake, with no problem attached
Nobody will own it
The goal is to replace a team, not remove repetitive work
Critical systems have no API access
Mass cold DMs, fake engagement, or getting around a platform’s rules
AI replying to customers alone where a wrong answer causes real harm

step 01 starts here

The map is free. Let's draw one.

A free 30-minute call to map one workflow.

Map a workflow with me

next: The tools I use

Craft Concepts Digital Automate _ Services All services Build Grow Automate Free apps Automate home Services Anatomy Tools Cookie settings Privacy Terms LinkedIn © Craft Concepts Digital · Vancouver, BC

Skip to content

Home Services Anatomy Approach Tools FAQ ← all services Map a workflow

approach · workflow first, tool second

Map. Automate. Hand over. Care.

Same four moves on every job, so your team still trusts it a year later.

{{ s.num }} {{ s.short }}

{{ s.num }} · {{ s.short }}

{{ s.title }}

{{ s.body }}

{{ s.listLabel }}

{{ it }}

{{ s.note }}

house rules

Seven principles I stand by.

{{ r.num }} {{ r.rule }}{{ r.why }}

guardrails

Compliance isn't a phase. It's in the build.

Built in from the start, not bolted on after launch.

{{ g.tag }} {{ g.body }}

fit at a glance

I'll tell you if it's not worth automating.

strong fit

{{ f }}

probably not

{{ f }}

step 01 starts here

The map is free. Let's draw one.

A free 30-minute call to map one workflow.

Map a workflow with me

next: The tools I use