Custom Agents
For the work that is particular to your business, where no product fits and the process still runs on people.
Implementation. Built for one process, on your systems, rules and documents.
Operations and functional leaders with a process nobody sells software for, and the IT teams who support it.
The work is repetitive and high volume, but particular enough to your business that nothing off the shelf does it.
What it gives you
Your process, not a product's
Built around how the work is actually done here, including the judgment calls people make without noticing they are making them.
Work that no vendor serves
In an energy company that is often joint venture billing, AFE review, land and lease administration, or Petrinex and OneStop submissions. Every industry has its own version.
Knowledge out of one person's head
The rules and exceptions recovered from the people who hold them, written down, and enforced consistently from then on.
Connected to your systems
Reading from and writing to what the process already touches, with permissions scoped to the task.
Boundaries you set
What it handles, what it escalates and what it is never allowed to do, enforced rather than implied.
An audit trail
What it did and why, in a form someone who was not there can follow.
A build-or-buy answer first
Where a product already covers the ground, we say so early. Custom is worth it when the process is genuinely yours and the volume justifies it.
Measured against the baseline
The numbers taken before the build, reported after, so the result is a fact rather than an impression.
Custom earns its place in one quadrant.
We would rather reach this conclusion in week one than halfway through a build.
Particular to you, but it happens eleven times a month. The build cost will not come back.
JV billing, AFE review, land and lease administration, Petrinex and OneStop submissions.
Standard work at low volume. A person doing it occasionally is the cheapest answer available.
Standard work at high volume is what the software industry already serves well.
- How particular the process is
- Standard → Yours alone
- Volume
- Occasional → Constant
We check first whether a product already covers it, then recover the rules from the people who hold them, set the boundaries, build against your systems and documents, and measure the result against the baseline.
The first question is whether to build at all
Custom is worth it when the process is genuinely particular to your business and the volume justifies it. Where a product already covers the ground, buying is faster and cheaper to own. We would rather say that in week one than discover it halfway through.
Recovering the rules is most of the work
The process lives in people. What they do when the document is missing, when the numbers disagree, when the deadline is tomorrow. Getting that out of them and written down is the part that takes the time, and it is worth having on its own.
Boundaries are what keep it alive
An agent built without an explicit account of what it must escalate will eventually make a decision nobody authorized, and the first you hear of it is when something goes wrong downstream. Writing that down before the build is most of the difference between an agent that stays in production and one that gets quietly switched off.
What you keep
The code and the data·Your existing relationships·Approval and control·The ability to stop·The off switchWhat that means
Start with a 45-minute briefing.
No pitch. We’ll map your situation against what actually works and tell you honestly where to start.