■ CONSULTING PRACTICE · INSIDE CYBORG GARDEN

We build agent systems that do real work, then we run them.

NimbleCo is the consulting practice inside Cyborg Garden. The garden is where the research and the open source live. This is where it gets built for someone in particular.


What gets installed

Your own instance, your keys, your infrastructure. We install the same tooling we run our own ventures on, so you can read it before you hire us: Swarm Map is the control plane that decides which agent can do what and where, and ASG is the operator that runs a unit of work from framing to handoff and then stops, because the call at the end is a human's. Both are public. So is the science we run on them.

Then we operate it. Agents handle the requests and surface the decisions, which is the actual product: attention protection at scale. Meetings are a cost, not a service.

How it is priced

Hourly billing has a bug in it. Make the harness twice as good and the work takes half as long, so doing the job well costs us money. We price four things separately instead.

Installation is a fixed project price, because it is a project and it finishes.

Operation is a monthly retainer priced on surface area: how many agents, integrations, scheduled jobs, repositories and hosts we keep alive. Surface area is the honest measure because it cannot be gamed by working faster.

Escalations come out of a monthly decision budget. That is the plainest description of what you are buying: access to a judgment queue that a machine has already filtered.

Tokens and infrastructure pass through at cost. We do not absorb them and we do not bury them inside a rate where you cannot see them.


What we leave with

Every consultant leaves with something. Usually nobody writes down what.

YOU KEEP THE SUBSTANCE. WE LEAVE WITH THE SHAPE.

Patterns we learn get generalised into our own templates. Your data, your names and your particulars never travel. That boundary is a fail-closed sanitisation gate that runs across the whole tree before anything leaves, and it fails closed, so a check that cannot complete blocks the release rather than waving it through. It is a technical control rather than a promise, and you can ask to watch it run.

If you would rather nothing was generalised at all, that is a priced option, not an argument.

Where this does not work

If your bottleneck is a decision only one person can make, a fleet of agents moves that bottleneck around rather than removing it. You will hear that at the scoping call and not three months in.

If we stop working together, you keep the instance and it keeps running. There is nothing here for us to hold hostage, which is deliberate.


[email protected]

Bring the work you gave up on automating. Ask to see the gate run.

The ventures and the open source live at Cyborg Garden. The old NimbleCo site is kept at the archive, and the writing has moved to the almanac.

Copy everything