How it works
An engagement, from signature to handover.
Seven moments in a Vantalect engagement, and what Pavilion does at each. The Assessment runs two weeks and the Embed runs six; the room is the same.
The walkthrough
Seven moments.
- 01
Signature
The consultant creates the workspace from the Assessment or Embed template. The calendar, the deliverables checklist, the obligations, and the document slots appear, dated from the access date in the statement of work.
- 02
Invitations
The sponsor and the named engineers are invited by email and sign in by magic link. The sponsor can add observers. Every person sees their own obligations and the pairing schedule.
- 03
Week one
The kickoff and the logging class are recorded on Zoom; their transcripts and reviewed summaries appear on the session pages within the hour. Fulcrum is installed in your environment and connected to the measurement panel.
- 04
Every week
Sessions are recorded; the agent drafts summaries, decisions, and action items; the consultant reviews and publishes; engineers pick up their tasks; the sponsor's weekly check-in has its own page with the number so far and the decisions of the week.
- 05
Documents
The audit, the installation plan, the readouts, and the playbook are published as versions. Your sponsor comments on paragraphs and accepts the version. The deliverables checklist ticks itself as artifacts arrive.
- 06
Measurement
The panel shows the baseline, the current factor, coverage, and, for the Embed, the distance to the 3x gate. Snapshots are taken at both readouts so the gate is auditable later; the week-six report attaches to the closing readout.
- 07
Handover
The closing readout is accepted; the export is generated; the workspace goes read-only and stays yours, with the archive.
Who does what
Seven roles, one room.
| Role | Who | Can |
|---|---|---|
| Owner | The consultant's organization | Everything: workspaces, templates, members, API keys, exports |
| Consultant | Charles, or any consultant on the engagement | Publish documents, schedule sessions, attach recordings, record decisions, assign tasks, mark deliverables |
| Sponsor | The client executive who signed | Accept deliverables and readouts, see the measurement panel, comment, invite their own people |
| Engineer | A client engineer on the named team | Read, comment, complete their tasks and obligations, open Fulcrum from the panel |
| Observer | Anyone else the sponsor invites | Read and comment |
| Agent | A Claude Code session or fleet service acting for the consultant | Publish, attach, summarize, record, and read through the API and MCP, as its own identity in the audit log |
| Guest | The holder of a share link | Read one document or recording, with expiry, no account |
What we need from you
Three things, and the clock starts.
Access within three business days
Repository, CI, and a container host for Fulcrum. The engagement calendar is dated from the day it exists.
Your engineers, four hours a week
Each paired engineer, for pairing and the weekly session. The obligation is tracked in the workspace, and a missed week slides the schedule honestly.
Your sponsor, thirty minutes a week
The weekly check-in, and both readouts. Acceptances are the sponsor's alone.
Meetings are held on Zoom and recorded with your permission. Your code never leaves your repositories; the measurement panel copies figures, never records.
Included with every engagement
Built for one occasion.
Handed over when it ends.
Every Vantalect engagement runs in a Pavilion workspace, set up in week one and exported to you in full at the close. It is not sold separately.
Remote engagements nationwide.
Pavilion, a Vantalect app.