See a project in action
One project. Two people. Different tools. Same page.
A freelance web designer and her client manage scope, timeline, and deliverables in a shared Virgil project. Each brings their own AI engine. Both see the same work.
Step 1 · Set up the project and invite the client
Create a project. Add the client. Bring your own engine.
Megan creates a "Bloom Botanicals Website" project in Virgil and invites her client David. Each person plugs in their own AI key. Megan uses Claude. David uses GPT-4o. Different engines, same project.
Two people, two AI engines, one shared workspace.
Megan Torres
internalWeb Designer · Torres Creative
14 entries in dossier
Engine: Claude (Anthropic key)
David Nakamura
externalOwner · Bloom Botanicals
6 entries in dossier
Engine: GPT-4o (OpenAI key)
Each person brings their own AI engine. Megan plugged in her Anthropic key. David plugged in his OpenAI key. Both work in the same project. The AI reads the same files regardless of which engine powers it.
Step 2 · Scope the project with a checklist
Write down everything the project includes.
Megan builds the scope checklist with Virgil. David can see it, check items off when he has reviewed them, and ask his AI to explain any line item. The checklist is a file in the project, so both engines can read it.
Step 3 · Track deliverables on the board
Move cards, not emails.
The board shows what is done, what is in progress, and what is next. Both Megan and David can move cards. Both engines can read the board when answering questions about project status.
Homepage mockup
Brand assets collected
Product photography
About page draft
Blog setup
Contact form
Launch checklist
Step 4 · Connect Stripe and Figma
Invoicing and design files, inside the project.
Megan connects her Stripe account for invoicing and her Figma workspace for design files. Everything is scoped to this project. Other projects cannot see these connections.
Stripe
Connected · Invoicing
2
Invoices sent
1
Paid
$3,200
Received
Figma
Connected · Design files
4
Design files synced
12
Comments imported
Scoped to this project only. Other projects cannot see these connections.
Step 5 · Budget and timeline in the table
The money is in the project too.
Megan builds a budget table inside the project. David can see the numbers. Both engines can reference the table when answering questions about cost, hours, or progress.
| Deliverable | Hours | Rate | Total | Status |
| Design (homepage + about) | 16 | $125 | $2,000 | Complete |
| Product catalog | 8 | $125 | $1,000 | In progress |
| Blog + content | 6 | $125 | $750 | Not started |
| Dev + launch | 10 | $125 | $1,250 | Not started |
| Total | 40 | - | $5,000 | - |
Step 6 · The payoff
The client asks a hard question. His AI already has the answer.
David opens the project and asks Virgil a question about the budget. He is using his GPT-4o key, but the AI reads the same checklist, the same board, and the same budget table that Megan's Claude reads. Different engines, same truth.
David's GPT-4o and Megan's Claude are reading the same checklist, the same board, the same budget table. Different engines, same truth. The project files are the single source, not the model.
The project is the handshake.
The scope lives in the checklist. The progress lives on the board. The money lives in the table. Both people see the same files. Both AI engines read the same context.
When the project is done, the workspace is the portfolio piece and the receipt.
This is not a project management tool. It is where the work happens and two people stay aligned without a single status meeting.
This is one client. Imagine a roster of them.
Every client, every project, every deliverable. One workspace. Virgil is available now.