Lead-to-Opportunity Workflow Pattern

A reusable pattern for designing Salesforce lead-to-opportunity workflows for companies with complex, relationship-driven sales cycles. Drawn from implementation work with ^[1], where the goal was to replace ad-hoc lead handling with a structured, accountable, and scalable system.

When to Use This Pattern

This pattern fits clients who:

Sell high-value, low-volume engagements (not transactional/volume sales)
Need to match leads to reps by expertise or bandwidth, not round-robin
Want structured sales accountability without over-constraining rep autonomy
Are scaling and need repeatable process before headcount grows

Core Workflow Stages

1. Lead Ingestion

Leads enter the system through multiple channels. Capture the source at ingestion for downstream reporting:

Strategy / outbound leads — sourced by marketing or ABM campaigns; track UTM parameters, campaign source, and channel
Referrals — from past clients or partners; capture referral contact and relationship to existing account
Direct inbound — form fills, calls, or direct email; treat as high-intent and prioritize response time

Key fields to require at lead creation: industry type, lead source, company/firm name, contact name and title. Avoid requiring fields that only become knowable at the opportunity stage (e.g., project address, project budget).

2. Lead Handoff — Manual Assignment via Notification

Do not auto-assign leads to reps. For complex sales, fit matters more than availability alone. Instead:

New lead triggers an email + Teams notification to the sales manager (or designated assignee)
Manager reviews lead and manually assigns to the best-fit rep based on:
- Domain expertise (e.g., fine art, commercial, hospitality)
- Current workload and bandwidth
- Existing relationship with the account or firm
Assignment triggers the automated playbook (see below)

Quarra Stone example: Lincoln (lldurham) wanted all new leads to notify him directly so he could assign based on rep expertise and capacity — e.g., routing fine art inquiries to the rep with that background rather than whoever was next in rotation.

3. Automated Sales Playbook

Once a lead is assigned, automatically create a sequential task list that guides the rep through the early sales process. Tasks should be structured but not prescriptive — define what to do, not exactly how to do it.

Example task sequence:
1. Do research on the firm and contact (link to research template or checklist in task description)
2. Make initial contact (call, email, or LinkedIn message)
3. Schedule discovery conversation
4. Log outcome and advance stage or disqualify

Implementation notes:
- Use a dropdown for task subject (not free text) to enable accurate reporting on task types and completion rates. Free-text subjects break grouping in reports.
- Tasks should have due dates set relative to assignment date (e.g., Task 1 due in 2 days, Task 2 due in 5 days)
- Overdue tasks trigger escalation alerts (see below)

4. Escalation Alerts

Accountability without micromanagement:

Rep alert: Email notification when a task is overdue by N days (configurable threshold, e.g., 3–4 days)
Manager alert: Separate notification to the sales manager when a task is overdue, so they can follow up without waiting for the rep to self-report

Both alerts should link directly to the record in Salesforce.

Two-Tier Scoring System

Scoring serves two different purposes at two different stages. Keep them separate.

Tier 1 — Lead Scoring (Pardot / Marketing Automation)

Purpose: Measure engagement and intent. Is this person paying attention to us?

Automated signals to score:
- Website visits
- Email opens and clicks
- Form fills
- Content downloads

Outcome: A numeric score that helps prioritize which leads to act on first. High scorers are warmer and should be contacted sooner.

This scoring lives in Pardot and syncs to the Lead record in Salesforce. It does not require manual input.

Tier 2 — Opportunity Scoring (Salesforce, Manual)

Purpose: Evaluate project and client fit. Is this the right opportunity for us?

Manual scoring dimensions (customize per client):
- Project timeline / urgency
- Project complexity and type fit
- Client decision-making authority (COG vs. influencer)
- Geographic location
- Budget tier / value alignment

Outcome: A score that helps prioritize which opportunities to pursue aggressively and which to deprioritize or decline — especially important when production capacity is finite.

Quarra Stone context: Lincoln had an existing qualifier matrix (ideal client / ideal project scoring) developed with his executive coach. The intent was to port this into Salesforce as the opportunity-level scoring model. The BD playbook covers the lead stage; the opportunity scoring covers the closing stage.

Integration Considerations

Outlook (Email)

Integrate Salesforce with Outlook so all email correspondence is automatically logged against the relevant Lead, Contact, Account, or Opportunity. This is especially valuable for:
- Multi-person project teams (anyone can see the full thread)
- Long-cycle projects where context may need to be recalled months or years later
- Commission structures tied to project completion, not just close

Users must install the integration themselves. Provide written instructions; offer a group walkthrough session if adoption is slow.

Microsoft Teams (Chat)

Native Salesforce–Teams integration exists and allows users to view, edit, and share Salesforce records directly within Teams. Research the current native connector before recommending third-party plugins. Use cases:
- Lead assignment notifications delivered as Teams messages (with direct link to record)
- Overdue task alerts surfaced in Teams
- Centralizing project communication away from scattered group texts and personal email

A free Salesforce–LinkedIn integration can be installed to display a LinkedIn profile card on Contact and Lead records. Reps can view profiles and send messages without leaving Salesforce. Useful for:
- Researching contacts before outreach
- Sending connection requests or InMail as part of the playbook sequence

Google Maps

A Google Maps component on the Contact or Lead record (showing the firm's location, not the project site) helps with:
- Sales trip planning and territory management
- Understanding which accounts are clustered geographically

Note: Project address belongs on the Opportunity object, not the Lead. A lead with a known project address is likely ready to convert.

ZoomInfo (Optional)

A paid lead enrichment and prospecting tool. Useful for ABM strategies and building targeted account lists. Evaluate cost vs. need; sharing seats is common but technically against ToS. Discuss with client before recommending.

Lead vs. Opportunity — Stage Boundary

A clear conversion trigger prevents ambiguity:

A lead becomes an opportunity when the contact sends something to price or scope — i.e., there is a real project to evaluate.

At conversion:
- Create the Opportunity record
- Generate the prospect folder / project number (not before)
- Begin opportunity-level scoring
- Transition from the BD playbook to the opportunity closing workflow

Fields that only apply post-conversion (project address, project budget, scope details) should live on the Opportunity object, not the Lead.

Project Object Sequencing

If the client also uses a Project object (post-close project management), sequence the implementation:

First: Define and implement the lead-to-opportunity workflow (this pattern)
Second: Build out opportunity closing stages and scoring
Third: Develop the Project object for post-close handoff to PMs

In the interim, PMs can use the Opportunity object to assign tasks to estimating — this is a workable bridge while the Project object is being configured.

^[2]
^[3]
^[4]
^[5]
^[6]
^[7]