Skip to main content
Skip to main content

Track one real opportunity from lead to project

Do not begin CRM implementation with a massive contact import. Begin with one real opportunity and prove that the team can move it forward without losing the next action or re-entering the customer when the work becomes a project.

At a glance​

Best forContractors managing leads, bid opportunities, customer relationships, projects, service calls, estimates, invoices, or payments
Initial setupApproximately 60–90 minutes for the first pipeline and test record
Pilot sizeOne salesperson/owner, one estimator or PM, one real opportunity
RolesCRM administrator, opportunity owner, estimator/PM, billing reviewer
Success looks likeOne opportunity has a next action, converts cleanly to a project, and reaches the next commercial document without duplicate customer entry

Use this solution when​

  • leads live in email, notebooks, spreadsheets, or individual phones;
  • no one knows the next action or owner;
  • bids are submitted but follow-up is inconsistent;
  • customer and project information is entered repeatedly;
  • won work does not hand off cleanly to operations;
  • service calls, project work, estimates, and invoices are disconnected;
  • management cannot explain pipeline value or conversion.

The first outcome​

One real company and contact become an owned opportunity with a next action, move through the agreed pipeline, convert to a project if won, and produce the next required estimate, invoice, or service action.

Before you begin​

Prepare:

  • one target company and contact;
  • one active opportunity;
  • opportunity owner;
  • estimated value and expected close date;
  • the company's real sales stages;
  • definition of won and lost;
  • required fields before a project can begin;
  • project numbering convention;
  • estimate/invoice numbering and approval policy;
  • payment terms, taxes, retainage, and other financial rules requiring review;
  • roles permitted to view, edit, approve, invoice, or receive payments.

Step 1: Define a small, honest pipeline​

Use stages that represent meaningful decisions. A practical starting point is:

New Lead → Qualified → Estimating → Proposal Sent → Negotiation → Won/Lost

For every stage, define:

  • entry condition;
  • required information;
  • responsible role;
  • expected next action;
  • maximum acceptable time without activity;
  • exit condition.

Avoid stages that merely describe feelings, such as Hot or Maybe, without an observable exit condition.

Step 2: Configure the minimum required information​

Require only information needed to act or report. Suggested opportunity fields:

  • company;
  • primary contact;
  • opportunity name;
  • owner;
  • stage;
  • expected value;
  • expected close date;
  • project type/trade;
  • location;
  • source;
  • next action;
  • next-action date;
  • loss reason when lost.

Too many required fields will drive users back to spreadsheets and notes.

Step 3: Create one company and contact​

  1. Search for duplicates before creating a record.
  2. Create or import the company.
  3. Add the primary contact.
  4. Confirm phone, email, role, and communication preference.
  5. Add only useful tags or classifications.
  6. Log one real interaction.
  7. Assign an owner.

Acceptance test: another authorized user can find the company, understand the relationship, and identify the next step without asking the record creator.

Step 4: Create the pilot opportunity​

  1. Link the company and contact.
  2. Assign one accountable owner.
  3. Enter realistic value and close date.
  4. Select the correct pipeline stage.
  5. Record scope and qualification notes.
  6. Add the next action and date.
  7. Attach or link relevant documents.
  8. Schedule the follow-up.

Every open opportunity should answer:

  • What are we trying to win?
  • What is it worth?
  • Who owns it?
  • What happens next?
  • When will that happen?
  • What could prevent the win?

Step 5: Test the full state path​

Move a clearly marked internal test opportunity through:

  1. New lead
  2. Qualification
  3. Estimating
  4. Proposal sent
  5. Follow-up
  6. Won conversion
  7. Project creation

Then test a separate lost opportunity and require a reason.

Verify that conversion does not create duplicate companies, contacts, or projects. Confirm which values transfer and what still needs review.

Step 6: Complete the won-work handoff​

The project handoff should contain:

  • customer and billing contact;
  • project name/number;
  • address and site contact;
  • contracted scope;
  • contract value;
  • exclusions and assumptions;
  • start/finish expectations;
  • project manager/foreman;
  • estimate/proposal version;
  • approval status;
  • billing terms;
  • required documents;
  • special safety, payroll, reporting, or customer requirements.

Use a conversion checklist. Do not rely on a salesperson's memory or a handoff meeting with no record.

Step 7: Test the commercial path​

Based on the customer's use case, test at least one:

  • estimate creation and PDF/email delivery;
  • approved estimate to invoice conversion;
  • change-order creation and approval;
  • service call to completed work and invoice;
  • recurring invoice;
  • client portal access;
  • payment recording or online payment flow.

Use internal/test recipients for the first attempt. Verify numbering, company information, taxes, discounts, retainage, payment terms, approval, PDF layout, email content, and status changes.

First-week rollout​

Day 1​

  • Enter five active opportunities manually.
  • Assign owners and next actions.
  • Do not import historical clutter.

Days 2–3​

  • Hold a 15-minute pipeline review using CRM records only.
  • Correct stages, values, dates, owners, and duplicates.
  • Observe which fields people avoid.

Days 4–5​

  • Convert one won opportunity or complete one service-call path.
  • Produce one controlled estimate/invoice test.
  • Decide which historical companies/contacts are worth importing.

Operating rhythm​

Opportunity owner — after every interaction​

  • Log meaningful activity
  • Update stage when the exit condition is met
  • Set the next action and date
  • Update value/date when circumstances change

Sales/estimating manager — weekly​

  • Review opportunities with no next action
  • Review stale stages
  • Review closing dates and probability assumptions
  • Review losses and reasons

Project manager — at conversion​

  • Accept or reject the handoff
  • Verify scope, value, contacts, dates, and documents
  • Confirm project ownership and field requirements

Billing — before sending documents​

  • Verify numbering, terms, tax, retainage, recipient, approvals, and amounts
  • Confirm payment status and reconciliation

Definition of done​

  • Pipeline stages have observable entry/exit rules.
  • The pilot company and contact are not duplicated.
  • The opportunity has an owner, value, close date, next action, and next-action date.
  • Won conversion produces the correct project and transfers required information.
  • Lost opportunities require a useful reason.
  • The relevant estimate/invoice/service path has been tested internally.
  • Permissions prevent unauthorized financial or customer actions.
  • The weekly review can be run from CRM without a separate spreadsheet.
  • A data owner exists for companies, contacts, projects, and financial status.

Common mistakes​

Importing every old contact​

Start with active customers and opportunities. Clean, map, deduplicate, and dry-run larger imports.

Building too many stages​

Use the fewest stages needed to drive decisions and accountability.

Tracking stage without next action​

Every open opportunity needs an accountable owner and dated next step.

Declaring the CRM the project system without a handoff​

Define the authoritative project record and how it becomes available to Time, Safety, and Apps.

Sending the first estimate or invoice to a real client without testing​

Verify output, email, approval, numbering, and calculations internally first.

Measure success​

  • open opportunities with owner and next action;
  • stale opportunities;
  • lead response time;
  • proposal follow-up time;
  • win/loss rate with meaningful reasons;
  • conversion without duplicate records;
  • days from won to operational handoff;
  • estimates/invoices sent without correction;
  • customer/project data re-entered in other systems.

What to add next​

When won projects need field labor tracking, activate BLDR Time using the same project. When the project needs daily reports, inspections, T&M tickets, photos, or special approvals, create a focused workflow in BLDR Pro. When project startup requires meetings, JHAs, permits, or training, activate Safety Meetings.

For the paper process behind this guide, see the bid pursuit process and client relationship management.

Important: Confirm contracts, taxes, retainage, payment processing, invoice requirements, record retention, and customer communications with qualified accounting and legal professionals.

Was this page helpful?