Drafting and sending
Draft, share an unguessable link, and record a decision that writes its own audit row.
Updated September 19, 2026 3 min read
When the scope and price are ready for a customer to review, create a proposal attached to the relevant client and opportunity. Open Proposals, check the draft’s title, scope and totals, then mark the reviewed version sent and share its public link.
Sharing and recording a decision
A draft link never exposes the proposal's content, so sharing one early does not leak your pricing. Once a proposal is marked sent, its unguessable public link lets the recipient view it, accept it, or decline it, and declining can include an optional short reason. If no explanation is supplied, the customer reason stays empty and the pipeline records that the proposal was declined. An expired or superseded proposal can no longer receive a new decision, on purpose, since a stale decision on old terms would be worse than no decision at all.
Every lifecycle change records its event and audit evidence in the same transaction, so the two can never drift apart. Repeating the same operation returns its existing receipt rather than creating a duplicate, and if a save fails, refresh the record and retry the same intended change instead of starting a fresh proposal.
Revising after you've shared it
Editing the material content of a proposal that has already been sent or viewed creates a new draft version rather than silently changing what the customer already saw. The earlier version becomes superseded and keeps its original content and history intact, so you always have a record of exactly what they were looking at when they read it. Review the new version and share its link when you're ready. Accepted, declined, and expired proposals are terminal: their terms cannot be edited in place, because a proposal someone already agreed to is not a draft anymore.
Following up
A recorded decision creates a follow-up task automatically and uses the same pipeline transition rules as everything else. Acceptance can move an open opportunity to negotiation, but it does not on its own establish a won deal or confirm collected payment, those are separate facts you still need to verify. If follow-up processing fails after the decision itself was recorded, retry that same response; its existing receipt lets the follow-up work resume without duplicating the original decision.
Use Today to review the resulting task and the pipeline to confirm the next stage matches what happened, not just what you hope happened.