See a project in action
One client. Three internal contacts. Six months of history. Zero dropped balls.
A construction company manages its most important client relationship inside a single Virgil project. Every email, every note, every decision, accessible to everyone who needs it, with an AI agent that has read all of it.
Step 1 · Set up the project
Create a project. Add the people.
The project manager creates an "Apex Development" project in Virgil. Then adds every person who touches this relationship: the client's point of contact and the internal team.
A folder per person: notes, emails, context, files, and a Virgil agent read into all of it.
Mark Reeves
externalVP of Development · Apex Development
24 entries in dossier
Robert Chen
internalAccount Manager · Turner Construction
18 entries in dossier
Jason Torres
internalProject Lead · Turner Construction
11 entries in dossier
Step 2 · Fill the dossiers
Paste emails. Add notes. Drop context. Connect Procore.
Every interaction gets logged. Robert pastes an email thread with Mark. Jason adds a note after a site visit. The project manager drops context about Mark's priorities. And because the project is connected to Procore, RFIs, change orders, and daily logs flow in automatically. Internal, external, and construction data live side by side.
Mark: 'We need Phase 2 wrapped by end of Q3. The board is watching this one closely. No extensions.'
Added by Robert Chen
Mark walked the site with me and the GC. He was happy with Phase 1 quality but flagged drainage on the east lot. Said if we handle it proactively he will fast-track the Phase 3 approval.
Added by Jason Torres
Mark reports directly to the Apex CEO. His reputation is tied to this project. He values responsiveness over formality. Prefers phone calls for bad news, email for good news. Has been burned by a previous contractor who over-promised.
Added by Project Manager
Change order #7: East lot drainage rework. $42,000. Status: Approved by Mark Reeves. Procore ref: CO-2026-007.
Mark: 'Approved, but this is the last one. We cannot keep moving the budget. I told the board Phase 2 is on track and on budget.'
Added by Robert Chen
Submitted by Jason Torres. Assigned to Mark Reeves. Response received in 2 days. Procore ref: RFI-2026-031.
Mark mentioned he is up for promotion to SVP. If Apex Development goes well, it is his ticket. He is more cautious than usual. Do not bring surprises.
Added by Robert Chen
Concrete pour complete, east wing. Weather hold lifted. Mark visited site, signed off on inspection. 14 workers on site. Procore daily log #84.
Step 3 · Connect Procore
Construction data flows in. No copy and paste.
The project connects to Procore in one click. RFIs, change orders, daily logs, submittals, and inspection records sync into the project automatically. Virgil does not replace Procore. It reads Procore the same way it reads your emails and notes, so the agent has the full picture: what was said, what was built, and what was approved.
Procore
Connected · Apex Development (Project #4821)
31
RFIs
7
Change orders
84
Daily logs
19
Submittals
Scoped to this project only. Other projects cannot see this connection.
Step 4 · Create a custom agent
Virgil reads everything in the project.
The team creates a custom Virgil agent scoped to this project. It has read every stakeholder dossier, every email, every note, every uploaded document, and every Procore record. When anyone on the team asks a question, the agent answers with the full context of the relationship and the build.
Apex Relationship Agent
Scoped to: Apex Development project · 3 stakeholders · 53 dossier entries · 12 documents · Procore (31 RFIs, 7 COs, 84 daily logs)
Agent instructions
You are the relationship manager for the Apex Development account. You have read every email, note, document, and Procore record in this project. When asked about any stakeholder, reference specific dates, quotes, RFIs, change orders, and context. Flag contradictions. Cross-reference what was said in emails with what was approved in Procore. Draft responses in Robert's voice unless told otherwise.
Step 5 · The payoff
Six months later, Mark contradicts himself. Jason catches it in seconds.
Mark emails Jason asking to expand the Phase 2 scope and push the budget. But six months ago, Mark told Robert the opposite. Jason does not remember that email. He does not need to. He asks Virgil.
The project is the source of truth.
Robert gets promoted. The history does not leave with him. Jason goes on paternity leave. His replacement opens the project and has six months of context on day one. Mark's contact at Turner Construction changes, but the relationship does not reset.
The board, the documents, the emails, the notes, the Procore data, and the agent are all in one project. Your emails talking to your change orders talking to your daily logs. Every tool sees every other tool. Nothing is siloed. Nothing is lost.
This is not a CRM. It is not a project management tool. It is a workspace where the work happens and the context lives, and an AI agent that has read all of it.
What the project holds over time
January
Project created. Mark, Robert, and Jason added as stakeholders.
January
Procore connected. 31 RFIs, 7 change orders, and 84 daily logs sync into the project automatically.
January - March
14 email threads pasted. 6 site visit notes logged. Mark's communication preferences documented.
March
Mark approves change order #7 but draws a line: no more budget changes.
April
Robert logs that Mark is up for SVP. Risk flag: he is being cautious.
June
Robert promoted to Director. His replacement reads the full project on day one.
July
Mark contradicts his March position. Jason catches it in 10 seconds with Virgil.
Year 2+
Phase 3 begins. The project carries forward. Every decision, every quote, every context note is still there.
This is one project. Imagine a wall of them.
Every client, every relationship, every project. One workspace. Virgil is available now.