Change the proposal without losing the last one
Create a new version whenever things change, keep each one's link, and let your client sign the version you agreed.
v3 final FINAL.pdf
Proposals change. The client wants a phase moved, a price trimmed, a deliverable dropped. Before long there are four PDFs and nobody’s sure which one was agreed.
Rofinery keeps every version of a proposal together, numbered in order, and makes the approved one the one that counts.
Versions without the confusion
Every change kept, one version agreed.
A new version in one step
Create a revision and Rofinery copies the proposal as the next version - v2, v3 and so on - with its own link. The new version starts as not approved.
Only one approved version
When a revision is approved, the others are marked as superseded, so there's never any doubt which version the work is based on.
Show clients the history, or don't
Choose whether clients can switch between the versions they've been sent. If they open an older one, they're pointed to the latest.
The details
How versions behave.
Its own link
Each version gets a new link, so an old link never shows new prices
PDF of each version
Clients can download the PDF of any version they can see
Clone a proposal
Copy a proposal within the same project as a starting point
Recorded in activity
Each new revision is recorded in the project's activity
Revise after approval
An approved proposal can still be revised, and the new version needs approving again
Checklists copied
Line item checklists carry into the new version
Questions about revisions
Only if you switch that on for your team. They then see the versions that were shared with them.
The signed version stays approved until another version is approved. The new revision starts as not approved.
Cloning works within the same project. To reuse work across projects, use deliverable and proposal templates.
Keep every version in one place
Or see how this fits with the rest of your proposal.