AI workflow build
When training is not enough, we build the workflow with you.
Some work needs more than better prompts: it moves between a CRM, spreadsheets, forms and email, or follows rules too strict to leave to a chatbot. Jack scopes it, builds it around the systems you already use, tests it on your real cases, and trains the people who will run it.
Who a build is for
- A team with one recurring task that takes hours every week and follows clear rules
- Work that moves between systems: CRM, spreadsheets, forms, email, Microsoft 365, Google Workspace or Lark
- A business that wants its rules in a sheet it can edit, not buried in code
- Teams that already tried a chatbot on the task and got results they could not trust
Not the right fit
- Replacing an ERP or migrating a whole CRM
- Projects that need the builder to hold a compliance certification such as HIPAA or SOC 2
- A product you plan to sell to your own customers
- Workflows where nobody will review the output
From one task to a workflow your team runs
- 1
A 20-minute call
What the task is, who does it now, which systems it touches and what “done” looks like.
- 2
Written scope and quote
What the workflow will do, what it will not do, which data and accounts it uses, and how we will check it works. Nothing is built before you agree to it.
- 3
Build and test on real cases
Built against sample or approved data first, then compared with a real week of the work. Problems are fixed before anyone relies on it.
- 4
Run it next to the old way
A person reviews every output while the workflow runs alongside your current process.
- 5
Hand over and follow up
Written instructions, a training session for the people who run it, and a check two weeks later on whether it should continue, change or stop.
Delivered with every build
- A working workflow that runs in accounts your team controls
- Business rules kept where your team can change them, such as a spreadsheet
- A plain-language page explaining what the workflow does and why
- Automated tests where the build includes code
- Training for the people who run and review it
- A two-week follow-up check
Not included
- AI tool, software or hosting subscriptions
- Ongoing maintenance or new features, unless scoped separately
- Changes inside systems your team cannot give us access to
A build in production: weekly scheduling for a livestream agency
About 30 part-time hosts and operators, 8 brand rooms, seven days a week. The first draft of the schedule used to take about six hours by hand each week; it is now generated from rules the client keeps in its own spreadsheet. A person still reviews, edits and publishes it.
- Engine
- Deterministic code, not a language model
- Rules
- Live in the client’s spreadsheet
- Status
- In production since September 2026
- Review
- A person reviews, edits and publishes
By written quote
Every build is scoped before work starts, so the quote matches the task, the systems involved and how much testing it needs. There is no public price list.
Questions about builds
Training or a build: which do we need?
If your team can do the task with an AI tool once they know how, training is enough; start with the training program. If the task needs to run on its own, across systems, or with rules enforced exactly, it is a build. The 20-minute call sorts this out.
Do you work inside our CRM or other systems?
Yes, through access your admin approves. We start with the smallest access that does the job, usually read-only, and agree in writing which data and accounts the workflow touches.
Do you use AI or regular code?
Whichever the task needs. A language model is useful where the input is messy, like free-text notes. Where business rules must hold exactly, the decision is made by deterministic code, as in the scheduling case study.
Who owns what you build?
Where possible it runs in accounts your company owns, and you keep the code, the rules and the documentation.
How long does a build take?
It depends on the task and the systems involved. The written scope gives a timeline before you commit.
Can our team learn to maintain it?
Yes. The handover includes training for the people who run it, and the rules sit where they can change them without a code change.
Bring one task to a 20-minute call
Describe the work and the systems it touches. Jack replies within one business day with a recommended next step: training, a build, or neither.