Every client document current by the next meeting.
The kickoff pack, the scope, the status report, the QBR: client work is a folder of documents that all have to reflect the latest conversation. Abstract keeps the folder true.
Every client project starts from the same template and drifts in its own direction.
After each call somebody owes updates to the scope, the timeline and the status doc, and by week six the documents describe three different projects. The client gets whichever version was attached last.
Template in, living deliverables out.
Start from your template.
A project template is a folder: proposal, scope, timeline, status, meeting notes. Duplicate it, feed it the pre-sales transcripts and the onboarding survey, and the first drafts write themselves around your structure.
Feed it the meetings.
Transcripts land in the project's meetings folder. After each call, one command updates every affected document, shown as diffs before anything lands.
Share the living version.
Publish deliverables as live web pages the client can always trust In beta, or export DOCX and PDF when the moment calls for an artefact.
Wednesday's call moved the launch date and added a deliverable. The transcript hits the project folder before you're back at your desk. Abstract proposes updates to the timeline, the scope and next week's status note, and flags that the pricing summary might be affected but isn't sure: that one's marked for your judgement. You approve, tweak the status wording, and the client portal already shows the new dates.
Nothing client-facing changes without you.
Client-facing documents change only through proposals you approve.
The diff view means you can let the agent do the sweep without letting it near your commercial language unsupervised.
Transcripts in, deliverables out.
Transcripts from Granola, Fathom or Fireflies as files today; direct connectors Coming.
Tickets and tasks from Jira, Linear, Asana or Monday Coming: pull work items in as context, push agreed actions back out.
Questions
Can clients see the machinery?
No. They see a clean published page or an exported document. The workbench is yours.
Does every project need setting up from scratch?
No. Templates are folders; your delivery method becomes the starting state of every new project.
What about confidentiality across clients?
Projects are separate folders with separate context. The agent working in one client's project sees that project.