How we work
How an AI engagement runs, from free consultation to support.
Your team can name where AI could help. Getting it running on your real systems is the hard part. We start from how the work gets done today, then take the automation all the way into production and keep it running.
Who works on it
- Talk through your process with the Zerg team. We’ll identify who would build and support it.
- One team from process design to production support.
- From you: the process owner and any technical specialists we agree on, with access to the systems the process touches.
Four steps
One process first. What you get at each step.
Start with the queue that slows your team down most. Then, if you choose, the next process, the same way.
01 / Free consultation
We learn how the work gets done today, find where AI automation will pay off, and recommend a first build.
You get a recommended first build and how we would test it, or a plain answer that it isn’t a fit.
02 / Acceptance criteria
We agree on acceptance criteria with you before we build, then test every build against them. They set which tests, on which systems, and what counts as passing.
You get the tests the first build must pass, agreed before work starts.
03 / Build and secure
Our engineers work inside your team to build workflows, integrations and custom apps, then test them against your real systems.
You set the tools, execution limits and human review points for Zerg agents.
You get the build and its tests, and each Zerg agent run leaves a history your team can inspect.
04 / Deploy and support
Connected to your ERP, repositories, APIs and documents.
We monitor results, fix failures and adapt the workflows as your rules and requirements change.
You get the build connected to those systems, and support on the terms agreed in the scope.
At the end of a build
What you have at the end.
- The acceptance criteria and the tests used to accept the work.
- The build, connected to the systems agreed in its scope.
- A history of the Zerg agent runs, for your team to inspect.
After the first build
Support, then the next process.
We keep the first build running. Then we decide with you whether to take on another process. Each one starts the same way: acceptance criteria first, then the build.
Questions teams ask first
Before the first build.
What does a first build cover?
One process, agreed in the consultation, and tested against acceptance criteria we agree with you before we build.
What if our process isn’t a fit?
We tell you in the consultation. We say no when we can’t agree on the scope and the tests up front.
Free consultation
Start with one process.
Step 01 is free. Bring one process and the systems it touches, and leave with a recommended first build or a plain answer that it isn’t a fit.