These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Technology CRM
- Features
- Proposal and outcome review
Proposal and outcome review
Tie proposal release and Won or Lost outcomes to independent decisions on the exact opportunity revision.
OverviewProposal Review Context×
Technology CRM · Proposal and outcome review
New
Proposal Review Context
Proposal waits for the sales manager
| Record number | Subject | Counterparty | Expected value USD | Probability percent | Expected close date | |
|---|---|---|---|---|---|---|
| OPP-41231 | Qualified opp-109 | ACC-110 | 20 | 97 | 20 Oct | |
| OPP-65534 | Qualified opp-151 | ACC-110 | 330 | 93 | 08 Oct | |
| OPP-23232 | Qualified opp-675 | ACC-110 | 330 | 87 | 06 Oct | |
| OPP-84015 | Qualified opp-323 | ACC-110 | 410 | 98 | 14 Oct | |
| OPP-82815 | Qualified opp-792 | ACC-110 | 910 | 90 | 12 Oct |
6 of 6 records
Qualified opp-109Opportunities · OPP-41231
QualifiedCounterpartyACC-110
Expected value USD20
Probability percent97
Expected close date20 Oct
Revision610
What you can do
Review the commercial decision before advancing
Relationship Owner prepares the proposal scope and next activity for an opportunity. Sales Manager independently reviews the locked revision before the opportunity advances to Proposal. The review decision retains its reason and source revision, so the team can explain what was considered acceptable at the time.
Negotiation reflects a discussion that has actually begun. Proposal submission alone does not establish that stage. Later, Relationship Owner submits verified acceptance or loss evidence for an independent closing review. Won records the winning date; Lost records a loss reason. Both outcomes preserve the prior expected value and activity evidence.
How the work is organized
- Proposal scope. Relationship Owner presents the intended commercial scope with the next action. Sales Manager examines the current revision and records an independent decision. Returned or rejected work needs resolution before the proposal is released.
- Actual negotiation. The owner records the customer’s negotiation activity and keeps the relevant revision clear. A changed scope cannot silently reuse a decision made on different content. The next activity should explain what remains open with the customer.
- Verified closure. Sales Manager reviews the acceptance or loss evidence against the exact revision. A technical trial result or optimistic probability estimate is not sufficient by itself to establish Won. Preserve the earlier expected value so the outcome can be understood in context.
What to agree during setup
Agree how proposal scope is recorded in the supporting evidence and what the reviewer needs to make the release decision. Define an eligible independent Sales Manager when the usual manager helped prepare the opportunity. Specify what a Return should explain so Relationship Owner can prepare a useful correction.
Decide what establishes customer acceptance and what makes a loss reason useful. Keep the closing decision separate from any connected onboarding, project delivery or billing action. If the business uses an external document or signature service, agree the connection and evidence path during implementation rather than treating the stage change as proof that the service completed.
Check the handoff on an actual case
Use an opportunity for a technology platform whose evaluation has completed. Relationship Owner prepares the proposal scope and a follow-up meeting. Sales Manager returns the proposal because the customer’s requested deployment scope needs clarification. Correct the evidence and obtain a decision on the new revision.
Record the customer’s negotiation discussion before moving to Negotiation. Then submit the final acceptance evidence for independent closing review. Try a close request using the older revision and confirm that it is refused. Run a second rehearsal ending in Lost, with a specific reason. Auditor should be able to see the original expected value and supporting activities in either case.
What your team sees
- Proposal Review Context — Qualified opportunities that provide context for proposal review actions.
- Decision History — Review reasons, reviewers and the source revisions they decided.
- Closed Outcomes — Reviewed Won and Lost opportunities with retained expected value and closing evidence fields.
Follow the work through
Follow proposal and negotiation, then reviewed win or loss.
What it keeps track of
Data model- Opportunities
- Sales opportunities with lifecycle, expected value and expected close date.
- Relationship activities
- Calls, meetings, emails and tasks logged against an opportunity.
- Review decisions
- Independent review decisions recorded against an opportunity revision.
- Record attachments
- Evidence files attached to an opportunity with visibility scope.
- Operation receipts
- Durable receipts for guarded operations with stable operation keys.
- Team members
- Named team members with their organization, platform identity and role scope.
Who uses it
Permissions- Relationship Owner
- , Sales Manager, Auditor.
- Relationship Owner
- Presents the evidence; Sales Manager decides independently; Auditor inspects the resulting history.
Set up Technology CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.