AI WORKFLOW SYSTEMS
Start with one workflow that is costing you time, leads, or trust.
I build a custom tool for one painful workflow, wired into the systems
you already use, and hand it back yours to own with a clear runbook.
This isn't a giant AI transformation and it isn't just prompt advice.
It's practical workflow work: map the process, wire the tools, add AI
where it helps, keep a human approval gate where judgment matters.
I'm based in Ontario, Canada, and I work with teams across the
Greater Toronto Area, and remotely with teams anywhere.
OFFERS
Fixed scopes. Real systems. No surprises.
I'm taking on a small number of founding clients right now, so the
first projects run on founding-client terms: a lower entry cost, and
the build is pay-only-if-it-works. You get my full attention while I
prove the work.
Offer · 01
Workflow Audit
Most small operations have one workflow they quietly dread, and
it usually grew by accident rather than by decision. The audit is
a focused read of exactly that workflow: what happens now, where
it leaks, what AI should and should not touch, and what I would
build first. You arrive with a feeling that work is falling
through the cracks. You leave with a map of exactly where, the
risks named, and a fixed-scope build plan, including exactly what
the build would do and how we would both know it works, that you
can act on with me or without me.
In hand at the end:
- Current-state map
- Automation opportunities
- Risk and data notes
- Fixed-scope build plan, with acceptance criteria
Sounds familiar?
- Sunday night spent clearing the backlog the week never let you touch.
- Asking the room "did anyone get back to them?" and nobody knows.
- The process that only works because one person remembers how.
$1,500 CAD Credited toward your build if you go ahead.
Offer · 02
AI Workflow Build
The build is a small working system around one workflow: intake,
AI-assisted drafting or classification, routing, review gates,
and tracking. Every inquiry gets acknowledged the moment it
arrives, the reply is drafted and waiting for a person to
approve, and nothing depends on memory anymore. You leave with a
working piece, built on accounts you own, and a runbook your team
can run without me. The guarantee is simple: you only pay for the
build if it does what we defined in the audit.
In hand at the end:
- Lead follow-up or document/inbox workflow
- Client-owned accounts and API keys
- Testing with sample or approved data
- Runbook and a walkthrough with your team
Sounds familiar?
- The customer who messaged at 9 pm and bought from whoever answered first.
- The quote you meant to follow up on, two weeks ago.
- Three people can see the inbox. Everyone assumed someone else replied.
From $4,000 CAD Most builds land between $4,000 and $9,000, fixed after the audit.
After the build
New versions and changes are paid work when you want them. No monthly
retainer, no lock-in. You own what I build, and it runs without me.
Industry pain, on the record:
unanswered web leads · abandoned AI initiatives · sporadic AI use in small business
WHY THIS IS NOT DIY AI
A prompt can help once. A workflow has to hold every week.
You can ask AI to write one reply, or wire a Zapier hack together over
a weekend. Both work until they don't. The gap is making the work move
reliably every time: inputs captured, outputs routed, state tracked, a
person reviewing the right moments, errors caught and visible, and a
clear way to recover when something breaks. That is a system, not a
script, and it is the part that takes real work.
My job is the middle layer: integration, judgment, QA, and the
walkthrough at the end. Where off-the-shelf tools like Zapier or Make
hit a wall, I build the custom piece in code instead of forcing your
work to fit a template. And if the problem only needs a quick prompt,
I'll say that instead of selling a build.
HOW DELIVERY WORKS
You own what I build. It runs on your systems.
What you are paying for is custom software, not a service you rent
from me. It is delivered as source your team can run and change, and
it lives on your infrastructure from day one. Your team keeps working
in the tools they already use, there is no new app to log into and no
new system to learn.
Runs on your accounts, your keys, your storage. You connect your own keys to the finished code; I never log into your systems.
Your data stays in your systems. I build against sample or redacted data, so your real records never flow through my tools.
You get the source and own your build outright; the reusable engine under it is licensed to you to run and modify forever. No black box, no lock-in, and a clean exit whenever you want one.
Handoff, runbook, and a walkthrough for your team, so it runs without you needing me from day one.
DATA AND SCOPE
Client-owned systems by default.
Production builds run on your own accounts, API keys, storage, and
automations. You connect your own keys to the finished code, and I
never log into your systems or sit between you and your data. The full
detail, where your data lives, training, ownership, and what happens
if I am unavailable, is on the security and
architecture page.
Prototype with dummy or redacted data first when possible.
Keep human approval before customer-facing or high-risk actions.
Avoid sensitive medical, legal, financial, child-related, payroll, or HR workflows unless the privacy scope is clear.
No revenue guarantees, full CRM migrations, or open-ended custom apps inside a small pilot scope.
QUESTIONS
Asked before you ask.
Where do you work?
I'm based in Ontario, Canada. I work with teams across the
Greater Toronto Area, and remotely with teams anywhere.
What does a first project cost?
A focused audit is $1,500 CAD, credited toward your build if you
go ahead. Builds run from $4,000, most landing between $4,000 and
$9,000, fixed after the audit, and you only pay for the build if it
does what we agreed. I'm taking founding clients right now, so the
first projects run on founding-client terms. Prices are published
because fixed scopes keep a first project honest.
Do you need access to our data?
As little as possible, as late as possible. Pilots run on sample
or redacted data, production builds run on accounts you own, and
a person approves anything customer-facing or high-risk. Your
data stays yours.
How do you build this without access to our live systems?
I build against the structure of your systems, not the contents:
your field names and formats, a few sample or scrubbed records,
and the test environments the tools you already use provide. Your
real databases and accounts connect only at the end, in your own
environment, and I verify each connection with a simple test
before anything goes live. Your production data never sits on my
machine.
What if we only need a quick fix, not a system?
Then that's what I'll tell you. The audit exists for exactly
this: a focused, fixed-price read of the workflow that ends in a
recommendation you can act on either way.
START
Send me the workflow that is annoying you.
Tell me what comes in, who touches it, where it slows down, and what
you wish happened automatically. I'll tell you whether it sounds
like an audit, a small build, or something you can handle yourself.
Text me what you're building. Straight to me, not a bot or an assistant, and
I usually reply the same day: 365-675-2420.