Agent builder
What a project manager needs chased on a Tuesday is specific to that project. So you build the agent. Describe the job in a sentence and it runs against your live model.
We stopped guessing what you needed.
Vela used to arrive with a procurement agent, a permitting agent and a studies agent already built. They were reasonable guesses, and that was the problem. We had never sat in your weekly delivery meeting, so we were guessing at the work. Now your team writes the agent and we build the thing that builds it.
- Describe the job in plain language
- It runs against your live project model
- Scoped to one project unless you widen it
- Share it with the team or keep it to yourself
New agent
Draft“Watch the supplier thread for GSU-01 and tell me when a date moves.”
Ana Duarte · Procurement Manager
Vela wires the job the sentence describes: when the supplier email lands, read the register, prepare the update, and stop at Ana's sign-off.
How one gets built
You write a sentence. You get the parts back.
Describe the job the way you would to somebody starting Monday. Vela works out which sources the agent reads, which fields it watches and what it raises when one of them moves, then shows you all three before you save it. If one part is wrong you fix that part. You don't rewrite the sentence.
- The sources, the watch list and the trigger are all editable
- It reads the live model as it stands right now
- Every conclusion cites the document it came from
Delivery watch, first pass
Read-onlyYou check its work against the citations before you let it watch anything for real.
What it is allowed to touch
It sees one project, and the rows you name.
An agent starts with the narrowest scope that lets it do its job, and that scope is printed on the agent itself instead of buried three screens into settings. It reads the project it was built for. It never picks up more access as it runs.
- Scope it to a project, a tab or a single thread
- Writing is granted per agent, and only if you grant it
- The scope is printed on the agent itself
What this agent may touch
What happens at the end
It works out the exact edit and hands it over.
An agent finishes by putting the change in front of somebody by name: these fields, these values, this document as the reason. That is faster than the alternative. A summary takes twenty minutes to check. A filled-in edit with the source attached takes one look.
- The real fields and values, filled in
- The document behind each one, and the place inside it
- It goes to somebody by name
Prepared update
Awaiting approvalThe agent works out the exact edit and hands it over. Dana signs it off or she doesn’t.
How it spreads
One person builds it. The team runs it.
An agent that works is worth more than the afternoon it saved the person who wrote it. Share it to the workspace and anyone on the project can run it, with the scope it was built with. Keep it private if the job is only yours.
- Share to the workspace or keep it private
- A shared agent keeps the scope it was built with
- The builder stays named on it, so questions have somewhere to go
Agents in this workspace
3One person builds it. The whole team can run it.
The anatomy of an agent
Four parts, and you can read every one.
Every agent is the same shape: a sentence, the sources it reads, the fields it watches, and the named person it stops at. Here is Ana's delivery watch, laid flat.
The sentence
“Watch the supplier thread for GSU-01 and tell me when a date moves.” Written by Ana Duarte, the way she would brief someone starting Monday.
What it reads
The GSU-01 thread in Gmail and the equipment register's Long-lead tab, row 12. Nothing else on the project is in its scope.
What it watches
Ready to ship, on site, and the float to the 6 Nov 2026 need-by. When one of them moves, it traces what the move touches.
Where it stops
It prepares the exact edits and puts them in front of Dana Whitfield by name. Nothing is written or sent unless she approves it.
The rest of the platform
AI-native execution layer
The systems, documents and teams behind a project, reading into one place where the work moves.
ExploreProject brain
One source of truth for the project, and somewhere a document is still findable years later.
ExploreCustom dashboards and portals
Build the view each discipline works out of, instead of asking four teams to share a screen.
ExploreTell us the job you would hand to a new hire.
Bring the thing your team chases every week. We'll build the agent for it on the call and run it against a project you already know the answer to.