The Systems Engine
The system runs.
Or it doesn’t.
Most AI systems are demos. This one hands your team a running workflow, the agents behind it, a human gate on every loop that matters, and the orchestration layer underneath. Two weeks. One process. Handed back running. Then the next one.
—01 The workFour surfaces
The Systems Engine ships in four shapes, all installed to run without me and against a process your team owns. The Workflow Sprint is the bounded first-step, a two-week engagement that installs one automated process. The other three shapes are what a bounded engagement compounds into over time as your team keeps commissioning them.
Workflow sprint
Two weeks. One process. Handed back running, documented, and owned by your team. The unit of work is a sprint, not a retainer. See the sprint page.
Agent stack
Custom LLM Gems in ChatGPT and Gemini, plus the prompts, guardrails and evaluation harnesses that keep them on-task. Tools your team owns, not tools you rent.
Orchestration layer
Make and n8n on top of the data your team already has. Google Sheets, Airtable, Slack, email, webhooks. The infra that makes the agents useful outside of a chat window.
Docs and handoff
SOP, architecture diagram, credential ownership, and a training session. Your team runs the system from the doc, not from a running Slack thread with me.
Custom LLM Gems · ChatGPT · Gemini · Claude · Make · n8n · Google Sheets · Airtable · Slack · Webhooks
—02 What holds itFour rules
Every automation project that fails, fails on one of these four. The rules are non-negotiable because bending them is how a system stops running the moment I hand it back.
Human gate on every loop that matters
Agents run. Judgment stays with the person. Anywhere a wrong output would ship to a customer, a human approves the send. No exceptions.
Diagram before code
Every automation has a hand-drawn map before a single API call. If the map has a hole, the code will too. If the map is clear, the code is mostly typing.
One process at a time
A two-week sprint installs one process. Not seven. The next sprint installs the next. Trying to automate everything at once is how nothing ends up automated.
Clean handoff
Your team owns the system, the docs, the accounts, the credentials, and the bill. I own the design and the training. That is the whole contract.
—03 How one gets builtThe two-week sprint
Four steps, in this order, inside a fixed two-week window. Nothing outside the map ships in this sprint, and that constraint is why the sprint actually ends.
Audit
The process on paper. Where it starts, where it stalls, what one thing gets automated first and what stays with humans on purpose.
Map
The diagram. Every step, every gate, every fallback path. Approved before build. Nothing gets built against a map with a hole in it.
Build
The stack goes together against the map. Agents, prompts, orchestration, comms. Nothing outside the map ships in this sprint. That is the whole scope discipline.
Handoff
Docs, credentials, ownership transfer, and a two-hour training session with the team that will run it. Then the next process starts a sprint.
Two weeks to a running system.
Then the next one.
Delivered through Donarus Creative Studios