An opportunity records potential work before it becomes a project. The Opportunities dashboard lists those records and provides pipeline views. This reference covers the main fields and controls; available choices depend on your account’s configuration.
Opportunity details
Field | Meaning |
Company | The prospective client. Select an existing company, or enter a trading name for a new one. A genuinely new company needs Create Companies. Matching an existing trading or legal name (any case) uses that company and does not need Create Companies. Without Create Companies, typing a new name stops the save with You do not have permission to create companies. For a new client who is a homeowner or other individual, tick This company is a person, not a business (for example a homeowner) under the new company message. The box starts ticked when Settings → Account Defaults has New companies are set to A person. See How to set up a client who is a person. |
Name | The name identifying the opportunity. |
Description | An optional summary of the enquiry or potential work. |
Referred By | The person and/or company that referred the opportunity. One picker lists contacts then companies. Choosing a contact sets the contact and their company; choosing a company sets only the company; clearing the field clears both. Typing a name with no pick creates a contact. Key details show the contact with the company underneath when both are set. |
Templates | The opportunity templates that provide its starting structure and available workflow. |
Opportunity Stage | The opportunity’s position in the sales process. The dashboard labels this Status. Stage names and defaults are configured for your workflow. |
Staff roles | The people responsible for the opportunity. Role labels, such as Assigned or Admin, depend on account setup. |
Team | The team associated with the opportunity. No Assigned Team means no team has been selected. |
Tags | Labels for organising and filtering opportunities. |
Contacts and addresses | Client contact and address records associated with the opportunity. |
Dates and forecasting
Field | Meaning |
Enquiry Date | When the enquiry was received. |
Due Date | The opportunity’s due date. |
Target Date | The target date for progressing or closing the opportunity. |
Deal Value | The monetary value recorded for the potential work. |
Lead Score | A configured likelihood category used in pipeline forecasting. For example, Hot (80%) combines a category name with its probability; the choices can differ between accounts. |
Revenue Structure | The expected revenue timing: Payment On Delivery or Monthly. |
Estimated Deposit Amount | The expected deposit included in the revenue forecast. |
Estimated Start Date and Estimated End Date | The expected delivery period used with the revenue settings for forecasting. |
Deal Won Date and Deal Lost Date | Dates recorded against the opportunity’s outcome. |
Pipeline views and filters
Control | Purpose |
List View | Displays opportunities in rows with key details, values and the latest note. |
Kanban | Displays the pipeline as a board. |
Insights View | Shows pipeline reporting. Primary Select and Multiselect custom fields appear as extra filters, and they carry through when you click into a chart or change the dates. |
All, Team Assigned and Self Assigned | Changes which opportunities are included by assignment. |
Monthly Revenue | Shows opportunities in the context of forecast monthly revenue. |
Search | Searches by opportunity name, address or contacts. |
Status, staff, team and additional filters | Narrows the displayed records. Saved Filters stores a filter selection for reuse. |
Stages and proposals
Stage names such as Enquiry, Quote Sent, Won, Lost and BD are examples of a configured workflow. An opportunity stage is distinct from the status of an individual proposal.
Converting an accepted proposal creates a project and marks the parent opportunity as won. Setting a proposal to Accepted alone does not create a project.