Send the final. Never the draft.
Proposals, working papers and deliverables on one record, so the version the client receives is the version the partner signed off, and the hours behind it are already counted.
One live engagement, five seats, three days
- PRO-004Proposal and scopeRev BAccepted
- REP-021Findings reportRev CIn review
- MOD-009Operating modelRev BApproved
- WRK-114Working papersRev ADraft
- PRS-030Steering packRev AIssued
The draft went to the client, and nobody can say who sent it.
Deliverables get rewritten by three people across a weekend, emailed round for comment, and the final that arrives at the client is whichever attachment was most recent in somebody's thread. Meanwhile the hours behind it are reconstructed from memory on the last day of the month.
Three things consulting teams notice first
One version goes out
Drafts are revisions of the same deliverable. The approved one is marked, so what reaches the client is what the partner signed.
Review that leaves a record
Comments and approvals sit on the document, not in a mail thread, so you can see who cleared what before it was issued.
Hours counted as you work
Log time against the engagement you are already in, so the fee position is current rather than rebuilt at month end.
Three steps, start to finish.
Open the engagement
Scope, proposal and the client all in one place, with the team who need access on it from the start.
Build the deliverable
Work through revisions, collect comments on the document, and record the approval that lets it go out.
Issue and account
Send from inside the engagement so replies file themselves, and close with the hours and the trail already in order.
Everything an engagement needs, in one place
From the proposal to the final invoice, on one record.
Clients and associates can be invited to a single engagement, and that is all they ever reach.
More of the platform.
Document control
Register, version, issue and mark up every document on one accountable record, so the whole team works from the version that is actually current.
ExploreProject delivery
Projects, milestones, statuses and the people on them, with the documents filed against the work rather than beside it.
ExploreContacts
Companies, the people at them, and the work you have in flight together, kept next to the documents rather than in a separate address book.
ExploreWhat people ask first
Yes. Invite them to the engagement and put the working papers behind a confidentiality setting they are not on.
Log hours against the engagement or the individual piece of work. It sits next to the deliverable rather than in a separate tool.
Yes. Start a new engagement from a structure you have already used, so the folders and the standard documents are there on day one.
Put one live engagement on it this week.
Three days free, five seats, every module. Take the deliverable with the most versions and see it resolve to one.
3 days · 5 seats · every module · no card