LupinusBuildContact
← All guides
Guide 4 · Leads

Track opportunities before they become customers or projects

The LupinusBuild Leads Pipeline provides a structured place to capture and manage sales opportunities before they move into later customer and project workflows.

Leads Pipeline

The Leads Pipeline tracks active sales opportunities before they become established customer or project records.

Open Leads

Leads that are not Won or Lost.

Open Lead Value

Combined estimated value of open opportunities.

Total Leads

Active pipeline records currently loaded.

Archived leads are excluded from the normal pipeline view.

Create or edit a lead

Authorized users can choose Add from the Leads screen to create a new opportunity. Existing leads can be opened for editing.

Lead title
Required name for the sales opportunity.
Status
Tracks the lead through the current sales pipeline.
Lead source
Records how the opportunity originated.
Estimated value
Optional estimated opportunity value.
Contact name
Optional contact name.
Contact email
Optional contact email.
Contact phone
Optional contact phone number.
Location
Address, city, state, postal code, and country fields.
Notes
Optional notes about the opportunity.
Required field

Lead title is required before a lead can be saved.

New leads currently default to New status, Other source, and US country.

Lead status

The current lead workflow supports these status values:

NewContactedScheduledProposal NeededProposal SentWonLost

Open lead counts and open estimated value exclude leads whose status is Won or Lost.

Lead sources

A lead can record the source of the opportunity using one of the current source options:

WebsitePhoneEmailReferralRepeat CustomerSocial MediaWalk-inOther

Estimated-value labels

Lead cards display a value-based label derived from the current estimated opportunity value.

High Value
$50,000 or more
Strong Lead
$15,000 through $49,999.99
Standard
Greater than $0 and less than $15,000
Unpriced
$0

These labels describe the estimated lead value used by the current application. They are not separate user-entered priority fields.

Lead cards

A lead card can show:

Status
Lead source
Value label
Lead title
Contact
Location
Estimated value
Notes

If no contact name is available, the display falls back to email, then phone, and finally No contact added.

Location display first uses city, state, and postal code. If those are unavailable, LupinusBuild falls back to the first address line and then No location added.

Convert a lead

In the current implementation, the Convert action appears for a lead whose status is already Won.

Authorized users are presented with two conversion choices:

Customer Only

Creates a customer from the lead information.

Customer + Project

Creates the customer and also creates a related project record.

Available contact and location information is carried into the customer record. When a project is also created, applicable lead information is carried into that project.

Conversion notes preserve lead-origin information such as the lead title, source, estimated value when present, and existing notes.

Company-specific project behavior

Project numbering, project stages, project status defaults, and other company-specific conversion rules can depend on the workspace configuration. Those implementation details are not presented here as universal LupinusBuild behavior.

Archive a lead

Authorized users can choose Archive from a lead card.

Archiving records the archive time rather than deleting the lead. Archived leads are then excluded from the normal active pipeline.

Lead permissions

The current lead-management interface allows the following roles to create and edit leads:

Primary AdminCFOAdminManager

Other supported roles can view lead information but receive read-only access in the current lead form.

Review Roles & Permissions →
Continue with customer records
Customers →