eva agents
Agents run the recurring work: the Monday brief, the payment chase, the programme watch. They read your systems on a schedule, prepare the output, and raise decisions to the right person.
Runs on your calendar
Weekly updates, deadline watches and pipeline reviews run on the schedule you set, not when someone remembers.
Acts with approval gates
Reading and drafting happen automatically. Anything that writes to a system or goes to a client waits for a named person.
Every run is logged
Each run records what was read, what was produced and who approved what, so the work stays auditable.
Run agents like the rest of your systems
Set up, govern and improve every agent.
The same discipline you apply to your ERP or document control, applied to automated work.
One agent per routine, working across systems.
An agent can read cost from the ERP, float from P6 and correspondence from Outlook in the same run, then produce one output.
- Multi-system reads in a single run
- Triggers on a schedule or a change
- Output routed to the right owner
Agent: payment-term watch
eva output- Reads ERP receivables daily
- Matches against contract payment terms
- Raises a chase list to finance
See it at work
Schedule a run.
Pick a workflow, set the schedule and see what a run produces. Illustrative sample, fictional data.
Reads
Illustrative run · fictional data
Compared finish dates on 9 projects against last week.
Produced a drift review, 3 slipped milestones charted.
Raised 2 milestones that now put a handover date at risk.
Nothing sent without approval. Every run logged.
Recurring briefs
The Monday brief, without the Sunday evening.
Agents assemble the cost and programme position from live systems before the week starts, so the meeting starts from facts.
- Weekly project updates across cost, programme and issues
- Morning brief on what changed
- Catch-up after time away
Monday brief · Project Harbour
eva output- Cost to complete unchanged week on week
- Facade float down to 4 days
- Two decisions needed from the client
Watches and chases
Nothing slips because nobody looked.
Agents watch what drifts quietly: payment terms, programme movement, expiring certificates, approaching deadlines.
- Receivables checks with a chase list
- Programme drift against baseline
- Notice and deadline watch across contracts
Deadline watch · this week
eva output- Early warning notice due Thursday
- Insurance certificate expires in 9 days
- Two invoices past payment terms
Governed by default
Automation with a human hand on the pen.
Agents prepare and flag. People decide. The boundary between the two is set per workflow, per team.
- Drafts prepared automatically
- Writes and client sends held for approval
- Activity log export for audit (rolling out)
Pending approvals
eva output- Client update · Project Harbour
- Chase email · Groundworks subcontractor
- ERP note · retention release
How an agent run works
- 01
Trigger
The schedule fires, or a change in a connected system starts the run.
- 02
Gather
The agent reads the current state of the relevant systems, through existing permissions.
- 03
Produce
A brief, a chase list or a flagged exception is prepared, each item with its source.
- 04
Report
The result lands with the right person, actions wait for approval, and the run is logged.
Connected systems
Agents work across the systems you already run.
Each agent reads from connected systems in place. Status shown as it stands today.
Available now
- Microsoft 365
- SAP Business ByDesign
- Primavera P6
- Zoho CRM
- On premise file servers
- PDF and Excel generation
- AutoCAD Architecture
- Revit 2024 in-app bridge
Rolling out
- Building takeoffs
Planned
- Bluebeam
- Procore
- Notion for personal accounts
See one workflow run against the systems and project information your team already uses.