An agency’s pipeline should help decide what to do with each project. A column called “interested” adds little if every salesperson interprets it differently. The goal is to create stages describing observable progress and identify stalled opportunities without relying on one person’s memory.
HighLevel distinguishes a contact, representing a person, from an opportunity, representing a potential deal. The pipeline brings together the process and its stages. This distinction is useful when a client first asks about a website and returns months later to discuss an advertising campaign. Official documentation.
Write the rules for every stage#
Start with a small number of stages and define the evidence required to enter or leave each one. An initial agency setup might be: request received, diagnostic completed, proposal presented and decision pending. Manage a won or lost outcome using the opportunity’s corresponding status.
“Diagnostic completed” requires a conversation and a summary of the need. “Proposal presented” requires the proposal to have been shared with the right person. A salesperson’s intention to prepare something is not evidence of progress by the client.
For each stage, assign an expected next action and an internal review timeframe. The timeframe does not need to be identical for a local retailer and a business purchasing through a tender. Document those differences so an opportunity that has remained open for several days can be interpreted correctly.
Collect only information that supports action#
Use contact fields for stable information about the person and opportunity fields for project information, such as service, indicative budget or expected decision date. HighLevel supports custom fields with different types; their availability in other modules depends on the selected object and field type. Official documentation.
Start with requested service, owner, next action, follow-up date and reason for loss. For recurring categories, use a small set of agreed options. Leave a short space for additional context, without turning it into the place where all important information is hidden.
Review a complete case#
Hypothetical example: a company requests SEO and advertising. The team opens one opportunity for a combined project if the budget and decision are shared, or two if they are independent purchases. After the diagnostic, record who decides, the priority problem and when the proposal will be reviewed. This definition prevents the same potential revenue from being counted twice.
Each week, look for opportunities without an owner, without a next action and with incomplete information. Review losses too, distinguishing budget limitations, poor fit and lack of response. Do not turn every new explanation into another category.
Measure time between stages, the proportion of diagnostics reaching a proposal and opportunities lacking follow-up. Before comparing salespeople, confirm they apply the same rules. The CRM is useful when its data represents what happened and leads to a concrete action in the next conversation.