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.
- Property Listing Portal
- Features
- Opportunities
Opportunities
Listing engagements from first qualification to a reviewed customer outcome.
OverviewMy opportunities×
Property Listing Portal · Opportunities
New
My opportunities
Opportunities
| Record number | Subject | Counterparty | Status | Expected close date | Revision | |
|---|---|---|---|---|---|---|
| OPP-96087 | New opp-417 | ACC-150 | New | 07 Oct | 330 | |
| OPP-67173 | Qualified opp-895 | ACC-150 | Qualified | 05 Oct | 650 | |
| OPP-64683 | Proposal opp-941 | ACC-140 | Proposal | 06 Oct | 80 | |
| OPP-98382 | Negotiation opp-703 | ACC-110 | Negotiation | 23 Oct | 370 | |
| OPP-12954 | Won opp-173 | ACC-120 | Won | 26 Oct | 580 |
6 of 6 records
New opp-417Opportunities · OPP-96087
NewCounterpartyACC-150
Expected close date07 Oct
Revision330
What you can do
Keep the engagement and its decision together
Each listing engagement begins as an opportunity. The Relationship Owner records the subject, account, expected close date and expected value in the correct organization. The opportunity stays connected to its owner, relationship activities, listing records, authorization files, review decisions and operation receipts. This lets the Sales Manager see the decision in the context of the actual engagement.
The pipeline moves through New, Qualified, Proposal and Negotiation before Won or Lost. The owner records calls, meetings, emails and tasks along the way. Qualification is guarded by the current revision and an operation key so a repeated request has the same result. Proposal submission is distinct from actual review and negotiation. A customer outcome needs acceptance or loss evidence; an eligible reviewer closes the same revision that was submitted.
How the work is organized
- Owned engagement. Each opportunity has an assigned Relationship Owner and a counterparty account inside an organization.
- Dated expectation. The expected close date and expected value support the manager’s pipeline review while the status identifies the current stage.
- Guarded outcome. Won records the date of the win; Lost records the reason. A reviewer checks the submitted evidence and revision.
What to agree during setup
Agree what qualifies an engagement for the team and what retain reason the owner records. Decide how an account is identified when a seller or counterparty appears in more than one discussion. Set a rhythm for updating expected close dates and logging relationship activity. Agree which evidence demonstrates customer acceptance and which notes support a loss decision. Include the Sales Manager who will review the result, and make sure that person is independent of the submission.
Prepare an example that can reach Won, an example that ends Lost and an example where the opportunity changes after submission. These cases show whether the reviewer sees the revision that was actually offered. Agree who works a returned proposal and how an owner follows up without treating a submission as approval.
Check the handoff on an actual case
A Relationship Owner opens a listing engagement for a seller account, gives it a close date and records an introductory call. After confirming the seller’s intent, the owner qualifies the opportunity and logs the retain reason. A proposal goes to review, then the team records the negotiation in the same opportunity rather than opening a second engagement. The owner attaches the signed acceptance and submits the current revision for close. The Sales Manager checks the attachment, the seller account and the revision before recording Won and its date. If the seller declines instead, the manager records Lost with the reason. A repeated close request with the same operation key must return the first result; a different request under that key is refused.
What your team sees
- Opportunities Overview — The engagement list with owner, account, close date, value and current status.
- Opportunity Pipeline by Status — A board for reviewing engagements by current status and owner.
Follow the work through
Opportunity qualification begins with an assigned engagement. Customer outcome covers the final review. See the data model for the linked records.
What it keeps track of
Data model- Opportunities
- Listing engagements worked by relationship owners from new through won or lost.
- Accounts
- Clients, sellers and counterparties associated with listing opportunities.
- Organizations
- Brokerage organizations that own listings and relationship records.
- Team members
- Brokerage staff and reviewers who own and moderate listing work.
- Relationship activities
- Calls, meetings, emails and tasks logged against an opportunity.
- Record attachments
- Owner authorization and supporting evidence files linked to an opportunity.
- Review decisions
- Independent moderation decisions recorded for a frozen listing revision.
- Operation receipts
- Durable receipts for every guarded action, retry and reconciliation.
Who uses it
Permissions- Relationship Owner
- , Sales Manager, Auditor.
- The owner prepares and records the engagement; the manager reviews the outcome; the auditor follows the evidence.
Set up Property Listing Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.